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
- The hover selection/highlight of items in the Insert button dropdown and the Documentation button dropdown are hard to see when hovered using the Light Editor theme
- NullReferenceExceptions appear when clicking to rename and then deleting the only GameObject in a scene
- Crash on "core::base_hash_set" when using nested [SerializeReference] fields in List<T> structures
- A ghost Game Window and multiple errors appear in the Editor when a Render Texture used by a Camera's "Target Texture" property is deleted
- Color Picker feels less smooth when dragging a Variables Color property in UI Builder Inspector
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.