Mesh class and Jobs/Burst/Mathematics question

What are best practices of using Job System, Mathematics, Burst and setting/getting Mesh data without generating garbage?

Mesh.SetVertex needs List<Vector3>, but Burst is optimized for Mathematics, which is <float3>. Do i have to create and copy hundreds of thousands of data to an intermediate NativeArray<Vector3> and then copy that to List<Vector3> just to assign verts to a mesh? Mesh class makes it really hard to work with. Same with just peeking into data.

Please help.

 

Yeah, meshes are pretty lame atm, here is a feedback request for upcoming improvements https://forum.unity.com/threads/feedback-wanted-mesh-scripting-api-improvements.684670/

You might want to look at https://docs.unity3d.com/ScriptReference/Graphics.DrawProcedural.html and friends as it needs no mesh

In general I would say you will have more luck asking questions like this here https://forum.unity.com/forums/data-oriented-technology-stack.147/

 

OMG thanks! Awesome stuff!