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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note (fix version 2020.2):
Warning message is reported about wrongly passed VertexAttributeDescriptor order in Unity 2020.2.0a15 and above.