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
- UI Builder windows text rendering breaks when using Rich text combined with an underlined emoji
- [Linux] Crash on mono_runtime_invoke when executing a specific script
- Installing the HDRP Water Samples doesn't notify the user to enable the "Water" on HDRP Asset
- Persistent Memory Leak in `ChunkDrawCommandOutput` and `CullingSplits.InitializeSplits`
- 1 KB or more of GC is allocated when Debug logging
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.