Search Issue Tracker
Fixed in 5.0.0
Votes
0
Found in [Package]
4.1.0
Issue ID
1315335
Regression
Yes
[ProBuilder] ProBuilder generates Meshes with empty Submeshes when the Mesh Renderer has more Materials than Submeshes
How to reproduce:
1. Open project "Case_1315335" and load Scene "SampleScene"
2. Select the Cube GameObject in the Hierarchy
5. In the Inspector, under the Mesh Renderer's Materials section, add additional Materials
6. Open the Probuilder Window (in the Menu Bar click Tools->ProBuilder->ProBuilder Window)
7. Select the Cube and ProBuilderize it
9. View the Cube's Mesh
Expectęd results: The Cube Mesh does not have any additional Submeshes
Actual results: The Cube Mesh has the same number of empty Submeshes as Materials in the Mesh Renderer
Reproducible with: ProBuilder 4.1.0 (2018.4.32f1, 2019.4.21f1, 2020.3.0f1), 5.0.0-pre.7 (2021.1.0b10, 2021.2.0a7)
Not reproducible with: 3.10.1 (2018.4.32f1, additional Materials get removed after ProBuilderizing it)
Notes:
- Many actions from the ProBuilder Window show the same behavior, not only ProBuilderizing
- The created Submeshes are made of 0 triangles and 0 indices
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
Add comment