Search Issue Tracker
Fixed in 5.3.3
Votes
0
Found in
5.3.1p1
Issue ID
765378
Regression
No
[DrawMeshNow] materialIndex is being ignored and all submeshes are drawn
Repro steps:
1) Open DrawMeshNow project I attached and asd.scene
2) Notice three objects(1st drawn with DrawMesh(), 2nd - DrawMeshNow, 3rd- simple gameobject)
3) Notice that part of front(lamps in white) is missing in the 1st object
but not in the second, as only one submesh was drawn
4) Open DrawMesh.cs and look at OnDrawGizmos
5) Notice that DrawMeshNow().materialIndex is the same as DrawMesh().submeshIndex
6) According to docs:
(DrawMesh)submeshIndex Which subset of the mesh to draw
(DrawMeshNow)materialIndex Subset of the mesh to draw.
Expected: DrawMeshNow().materialIndex should work the same as submeshIndex, as written in docs
Actual: All submeshes are being drawn
Reproduced in: 5.4.0b7; 5.3.3f1; 5.2.3p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment