Search Issue Tracker
Fixed in 1.1.0-pre.1
Votes
0
Found in [Package]
1.0.2
Issue ID
1289851
Regression
No
Additional Vertex Streams field is cleared after opening another Scene and updating the Polybrush package version to 1.0.2
How to reproduce:
1. Open the attached '1289851.zip' project
2. Open the 'Test1' Scene
3. In the Hierarchy window select the 'Cube' object
4. Observe the 'Additional Vertex Streams' field in the Inspector window
5. Open the 'Test2' Scene
6. Open Window > Package Manager
7. Update the Polybrush package to the 1.0.2 version
8. Open the 'Test1' Scene
9. Select the 'Cube' object and observe the 'Additional Vertex Streams' field
Expected result: The Additional Vertex Streams value is not cleared
Actual result: The Additional Vertex Streams value is cleared
Reproducible with: 2019.4.14f1, 2020.1.14f1, 2020.2.0b11, 2021.1.0a5 (when upgrading the Polybrush package from 1.0.0, 1.0.1 to 1.0.2)
Not reproducible with: 2019.4.14f1, 2020.1.14f1, 2020.2.0b11, 2021.1.0a5 (when upgrading the Polybrush package from 1.0.0 to 1.0.1)
Cannot test with 2018.4.29f1 (Multi-object editing is not supported)
Notes:
- Sometimes after updating the package and opening the 'Test1' Scene the Polybrush Mesh (Script) component's 'Apply as' field changes to 'Overwrite Mesh' (1/3 times)
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
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
- [Android] [Windows] The frame buffer is replaced incorrectly when using Framebuffer Fetch
- Crash on Scripting::SetCachedPtrOnScriptingWrapper(ScriptingObjectPtr, Object*) when exiting a project
- WASM Heap size greatly increases when UI elements are present in a WebGL build
- Crash on mdb_node_add when opening a specific project with a corrupted Library
Resolution Note (fix version 1.1.0-pre.1):
https://github.com/Unity-Technologies/polybrush/pull/148