Question about Morph Targets implementation

Animation
4

Thank you for detailed answer. I think the option AD 2 makes a lot of sense. Especially that morphs can be mixed together at runtime.

It also aligns well with my draft, however I was keen to use “normal” class instead of x3d node. But having it as TX3dChildNode descendant opens important additional options:

  1. Fully compatible with CGE philosophy,

  2. Serialisation. If stored in an external x3d file it can be read by any x3d editing tool. Also it allows extracting the morph’s data from one model and reuse it for many - as long as indexes and vertex counts are unchanged (which is always true by-design for my parametric humans, at least the closest LOD level where morphs matters most).

I’ll have a look at it. I need it anyway, but can’t promise a short time frame.

1 Like