Page MenuHome

Objects: make evaluated data runtime storage usable for types other than mesh
ClosedPublic

Authored by Brecht Van Lommel (brecht) on Jan 28 2020, 11:26 AM.

Details

Summary

This is a change from the new-object-types branch, so we can use it like this:
rBd6f02083a418: Objects: use evaluated data runtime storage for hair, point clouds and volumes

This only changes mesh_eval. It seems logical to do the same for mesh_deform_eval, and perhaps make instancing mechanism using Mesh_Runtime.mesh_eval generic as well. But I wanted to check first if this is the right direction.

Diff Detail

Repository
rB Blender

Event Timeline

Ping, any opinion on this?

Rebase on latest master.

Remove accidentally added file.

Seems good and logical.

Would think that eventually, would be nice to have an assert in BKE_object_get_evaluated_mesh() to catch logic mistakes like "give me mesh for volume object". But can happen later as well, as it's possible that some of the users of BKE_object_get_evaluated_mesh don't check object type first.

This revision is now accepted and ready to land.Feb 27 2020, 3:18 PM

Would think that eventually, would be nice to have an assert in BKE_object_get_evaluated_mesh() to catch logic mistakes like "give me mesh for volume object". But can happen later as well, as it's possible that some of the users of BKE_object_get_evaluated_mesh don't check object type first.

I will check on this still, to see if we can add an assert.

Maybe in the future "give me mesh for volume object" may actually be a valid request if we have modifier nodes, though likely the API function for that will be different.