I think I might have an idea where ali's model is coming from... Is it that company from Munich, that has it's own "realtime" software?
I get data from them every week, and it is a pile of crap. Every part of geometry is child of a least 15 Helpers/Nulls. See attached screens. And the parts don't share these helpers, every part has it's own set of them!


I don't see the reason for that, but the parts are arranged into groups and nealy all of the helpers have names like "ANIM_ROT", ANIM_SCA", "ANI_TRANS". I can't understandwhy you need seperate helpers for all the transformations, for EVERY part. I mean, while working at Mackevision I learned how to set up datasets for creating configurators and such, but it was a completely different approach that worked very well in Max.
What I do nowadays is rearrange the parts into logical groups like headlights, seats etc. and delete all the unneccesary helpers. The scene is way more responive afterwards, but you are destroying the "logic" behind the clients scene.

I get data from them every week, and it is a pile of crap. Every part of geometry is child of a least 15 Helpers/Nulls. See attached screens. And the parts don't share these helpers, every part has it's own set of them!
I don't see the reason for that, but the parts are arranged into groups and nealy all of the helpers have names like "ANIM_ROT", ANIM_SCA", "ANI_TRANS". I can't understandwhy you need seperate helpers for all the transformations, for EVERY part. I mean, while working at Mackevision I learned how to set up datasets for creating configurators and such, but it was a completely different approach that worked very well in Max.
What I do nowadays is rearrange the parts into logical groups like headlights, seats etc. and delete all the unneccesary helpers. The scene is way more responive afterwards, but you are destroying the "logic" behind the clients scene.
Comment