Feedback Now that we have new GetBindposes in 2022.2, How about SetBindposes?

I would like to SetBindposes with NativeArray<Matrix4x4>.

NativeArray version of GetBindposes() seems to give us direct pointer of the buffer but its length is fixed to existing bindposeCount.
It will not work with runtime generated mesh because old .bindposes property is probably the only way to change bindposeCount dynamically. And it is inefficient.

Tnanks!

Edit:
I could not find out how bindposeCount is determined for runtime-generated mesh in the document.
But if bindposeCount is automatically calculated when all bone indices decided like by calling
SetBoneWeights(NativeArray<byte> bonesPerVertex,NativeArray<BoneWeight1> weights), it is enough for my use case.(I will check that when I have time)
But even if so, it is very unclear. Either way, to replace bindposes property properly, SetBindposes should exist, I suppose.

 

Thanks a lot! I've almost given up it.
Actually I did avoid this problem by having bindposes by myself, but it was possible because I have written entirely custom solution for animation-skinning and asset definitions like mesh. It is not a normal way to avoid this issue so I am glad to have such a common solution for this problem.

Anyway, I really do appreciate the fact that you guys doing very well to make us achieve high performance things recently.

 

Would it be possible to get these bindpose APIs on MeshData in 2023 as well? It's often the one thing I have to jump back onto the main thread for when processing mesh data.