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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note (fix version 2020.2):
Warning message is reported about wrongly passed VertexAttributeDescriptor order in Unity 2020.2.0a15 and above.