Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.0b11
Issue ID
1199899
Regression
No
[MeshAPI] Warning/error should be reported for wrongly passed VertexAttributeDescriptor order
New 2019.3 Mesh API expects a certain order of VertexAttributeDescriptor structs (https://docs.unity3d.com/2019.3/Documentation/ScriptReference/Rendering.VertexAttributeDescriptor.html) but it does not warn or error if they get passed in the "wrong" order. Should be improved.
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
- 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
Resolution Note (fix version 2020.2):
Warning message is reported about wrongly passed VertexAttributeDescriptor order in Unity 2020.2.0a15 and above.