Search Issue Tracker
Fixed in 1.1.0-pre.3
Votes
0
Found in [Package]
1.0.1
Issue ID
1315475
Regression
Yes
[PolyBrush] Something went wrong saving brush settings Warning is thrown when Saving a Brush after opening the PolyBrush Window
How to reproduce:
1. Create a new project
2. Import PolyBrush
3. Click Tools -> Polybrush -> Polybrush window
4. Press the Save button located next to the Brush drop-down list
5. Observe the Console window
Expected results: No errors are thrown and the brush settings are saved with no issues
Actual results: "Something went wrong saving brush setting" warning is thrown in the console
Reproducible with 1.0.1, 1.0.2, 1.1.0-pre.1(2018.4.32f1, 2019.4.21f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a5)
Not reproducible with: 1.0.0, 1.0.1-preview.2(2018.4.32f1, 2019.4.21f1, 2020.2.5f1)
Workaround: Switching to another Brush fixes the issue. Settings for all brushes can then be saved until the PolyBrush window is closed
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.1.0-pre.3):
Fixed in Polybrush 1.1.0-pre.3 which will be available in Unity 2021.2
Resolution Note:
Fixed in Polybrush 1.1.0-pre.3 which will be available in Unity 2021.2
Resolution Note:
https://ono.unity3d.com/unity/unity/pull-request/123695/_/2021.1/st/polybrush-1.1.1