Using dynamic mesh system from Tiny in Jobs, in hybrid unity

The Hybrid Renderer still uses UnityEngine Mesh objects, so you have to get the data into a Mesh. However, DynamicLitVertex is ultimately just a DynamicBuffer<DynamicLitVertex> -- and DynamicLitVertex is a pretty basic vertex. Your code can generate into a DynamicLitVertex on all targets, and then for the hybrid use case, you can update a Mesh using SetVertexBufferParams + SetVertexBufferData (see https://docs.unity3d.com/2020.1/Documentation/ScriptReference/Mesh.SetVertexBufferParams.html + https://docs.unity3d.com/2020.1/Documentation/ScriptReference/Mesh.SetVertexBufferData.html ) to efficiently set & upload that same data into a UnityEngine Mesh.

You can write into a DynamicBuffer from a job; there are constructs that let you split up work of populating part of the buffer to different jobs too.

 

Though one caveat that I haven't checked yet -- SetVertexBuffer* has a limitation that the vertex streams must be in the order specified in the docs (see https://docs.unity3d.com/2020.1/Doc...ence/Rendering.VertexAttributeDescriptor.html the paragraph starting "Within each stream..."). You can omit some, but the ones that are present have to be in that order. If you don't, it will just... silently not work. :/ I'm not sure if DynamicLitVertex follows that order unfortunately. (If it doesn't, we can fix that.)