Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
1
Found in
Issue ID
1258543
Regression
No
Mesh.MeshData.SetVertexBufferParams function is not compatible with Burst
SetVertexBufferParams function of Mesh.MeshData uses params VertexAttributeDescriptor[] attributes that doesn't compile with Burst. There should probably exist an overload that takes NativeArray<VertexAttributeDescriptor>.
Comments (1)
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
tonytopper
Apr 28, 2025 19:28
This just bit me. The worst part is it's a silent bug. I was using the version of SetVertexBufferParams
that uses VertexAttributeDescriptor[] and it worked in a job with [BurstCompile].
When I switched to the NativeArray version, the resulting Mesh was just empty.
As soon as I removed the [BurstCompile] attribute from the IJob the resulting Mesh worked as intended.
Thankfully, I at least got a nice performance boost from eliminating the managed array from the job. But only after figuring this out.