PDA

View Full Version : 3ds Max character destroyed !


sophie
07-22-2003, 03:11 PM
Hello everybody,

My problem is with character animation in 3ds Max5

When a have some objets in an open group and want to close it,
and take some bones or skin of a character in the selection of those objects, it close everything either the character and destroyed it...

It's meen that he dosen't consider my character anymore and compressed the contened as one group (hundred of bones, IK, and skin are like in a group but not editable)... and loose the yellow character pils.

It's meen that I can NOT animated anymore, such a loosing time...

And also, when I merged a character, all the contense have the same name that the characters who are in the scene. (I am animating 5 characters based on a same one so I have five time ROOT, etc... !)
Is it possible to rename hundred of bones, skins and IK in a merged operation ?

Sorry for my english, I am french speaking.
thank you for helping me.
Sophie

FabioMSilva
07-29-2003, 10:00 PM
that sux:thumbsdow

relief7
08-25-2004, 03:38 PM
I dont know if you have been able to solve your problems yet but I would recommend not to use grouping when dealing with linked objects or hierarchies or not to use grouped objects at all because it seems that MAX is still very buggy when mixing groups and hierarchies. Layers or Selection-Sets are a better and less buggy way of organizing things - at least in my opinion. So put your bones in a separate selection-set or layer, your mesh in another and so on. That should keep your whole character stable.

For your import problem, one solution would be to freeze or hide every object in your scene. Then import your new character, select all objects (the objects of your character in scene are still frozen) and rename them via "Tools->Rename Objects" and give them another Prefix, for example. Now when you unfreeze your other character, they have got different names.

I hope that solves your problems,
Markus

CGTalk Moderation
01-15-2006, 06:00 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.