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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2020.2):
Warning message is reported about wrongly passed VertexAttributeDescriptor order in Unity 2020.2.0a15 and above.