Search Issue Tracker
Fixed
Fixed in 6.0.X
Votes
0
Found in [Package]
6.0.1
Issue ID
PBLD-115
Regression
No
PolyShape meshes are not visible and "Object may be corrupted" warnings are thrown when creating a new PolyShape with GPU Resident Drawer enabled
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/Scenes/SampleScene“ scene
3. Create a new PolyShape (Tools > ProBuilder > Editors > New PolyShape)
4. Observe the Scene View and the Console window
Expected result: The created PolyShape is visible and no errors/warnings are thrown in the Console window
Actual result: The PolyShape is not visible and the “Material count in the shared material list is higher than sub mesh count for the mesh. Object may be corrupted.“ warning is thrown in the Console window
Reproducible with: 6.0.1 (6000.0.1f1)
Couldn’t test with: 5.2.0 (2021.3.33f1, 2022.3.15f1), 5.2.2 (2021.3.38f1, 2022.3.28f1) (due to GPU Resident Drawer feature not existing)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Note: When creating a Shape and selecting any of the shapes (Tools > ProBuilder > Editors > New Shape), the issue does not reproduce. Reproduces only when creating a new PolyShape
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [sw-unity-6-1] UI Toolkit Debugger's "Pick Element" functionality does not work when hovering on any Editor panel except the Game view
- [Silicon] Crash with multiple StackTraces when entering Play Mode in a project with corrupted FBX files
- Index Out Of Range exception when trying to use Rendering Layer Override in Probe Adjustment Volume without a mask defined in lighting settings
- [Android] [Vulkan] [WebCamTexture] "WebCamTexture.Play" crashes the application when the camera is started
- Huge performance overheads appear when there is a large amount of bindings in the UI Toolkit
Add comment