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
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
- Crash on Scripting::LogException when async HTTP callback executes after scripting domain teardown
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.