backpackvacuum

Yeah, that is unfortunate that it’s not directly possible with the new system.

However, I’ve just done some testing, and it looks to me like there is a workaround that could be scripted and included in the V3D exporter.

If you take your shape-keyed object and split each shape key to its own object, (duplicate the object for each shape key, set that key to 1.0 and the rest to 0, then delete all the keys, deleting the key set to 1.0 last), you can then apply the modifier, then join your objects as shape keys, and re-apply any animations that you had.

This method doesn’t leave the modifier intact like the “bake modifiers” option in the V3D exporter currently does, but I’m not sure how you guys are doing that or whether the same approach could be applied here with my method described above?

kdv wrote:

Actually, it is. Three cubes are in the group “export”. Only the blue one (child.001) is not in that group.

You’re correct that Verge3D has placed the red cube into the “export” group, but if you look in the Blender file, you’ll see the the red cube is not in that collection. I guess v3d might not support children being excluded from a collection that their parent is in?

What was your method for exporting the file in that second screenshot? Was it exported from V3D or from Blender?

Also note, the blue cube is not in the “export” collection, and it is also not a child of anything in the “export” collection, and it behaves as expected and is not exported.

Also, my zipped project folder did not attach on the first post. I’ll try to attach it here.

I’m not sure what you mean by “baking” a shape key animation? I create my shape keys and put keyframes on their values (see screenshot.)
For this project, all of the animations are done in Blender and played back in sequence, so we don’t use things like morph puzzles.

• This reply was modified 9 months, 2 weeks ago by backpackvacuum.

Was able to find a solution using a follow-path constraint and twisting the path points.