Quote - Ooh!  It's available!  :woot:

I didn't quite follow the discussion in the earlier thread.  In what way is the process incompatible with Wings 3D?

Wings has a weird way of dealing with group ('g') statements in .obj files. If there's an object ('o') statement, it just ignores them. Otherwise, it treats the groups as separate objects. At any rate, the group information gets lost. What that means is that the morph loader script cannot support Wings directly. The user has to do some extra work (using UVMapper etc.) to get the grouping information back into the morphed mesh that's exported from Wings.

I hope I've described the problem correctly. At any rate, I've tested the morph loader with Wings, using my own software to reconstruct the grouping information and vertex ordering (since I like to do my morphing on a mesh split in half and mirrored), and it worked like a charm.

-- I'm not mad at you, just Westphalian.