Search Issue Tracker
Won't Fix
Won't Fix in 5.0.X
Votes
0
Found in [Package]
4.5.2
5.0.4
Issue ID
PBLD-24
Regression
No
[ProBuilder] Mesh names can change when modifying Scenes
How to reproduce:
1. Open the user's attached project and load Scene "SampleScene"
2. Select the "Cube" GameObject in the Hierarchy
3. Observe the name of the Mesh in the Inspector under the "ProBuilder MeshFilter" Component
4. Create a new Scene and load it
5. Return to the Scene "SampleScene" and repeat steps 2 and 3
Expected result: The Mesh's name remains the same
Actual result: The Mesh has a new name
Reproducible with: 4.1.0, 4.5.2 (2020.3.37f1), 5.0.6 (2021.3.7f1, 2022.1.11f1, 2022.2.0b3, 2023.1.0a4)
Reproduced with: Windows 10, macOS 12.3 (Intel)
Notes:
- Other arbitrary actions can also make the Mesh change its name (however, these methods appear to have a lower reproduction rate), such as: disable a GameObject -> save Scene (does not have to be the Scene containing the Mesh), close and reopen the Project
- Issue has a negative impact on Version Control software which prompts changes to a Scene when no actual changes exist
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
- [RenderGraph] Outputs from camera stack override each other when using OpenGLES3 with a custom renderer feature
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
- MeshCollider preview gizmo disappears from the Scene view when overriding the mesh asset using any 3D editing tool
- Tutorial project is not created when started from the Get set up tab
- Audio Listener Component expands when selected
Resolution Note:
This is a known issue that is related to the underlying serialization architecture of ProBuilder. The issue can't be fixed anytime soon but it's under consideration as part of future larger improvements.
Resolution Note (5.0.X):
This is a known issue that is related to the underlying serialization architecture of ProBuilder. The issue can't be fixed anytime soon but it's under consideration as part of future larger improvements.