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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Warning message is reported about wrongly passed VertexAttributeDescriptor order in Unity 2020.2.0a15 and above.