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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.