Just come across a situation whereby I have a problem with 6.0.5.7 in that it doesn't seem to want to save my heirarchy changes with a particular model. I make the changes, save the model and then reload the model only to find that the changes aren't saved at all. Its very frustrating and a new one for me.
I will have to find a work around solution for this one if I can, otherwise its work down the drain.

Hi V_F

Thats a new one,I haven't come across that before.
Just a thought...what happens if you save the file under another name, are the changes still not saved.

Bazza

Hi Bazza,

Yes, its the first time I've encountered it, although after talking to Paul Gausden he has mentioned he has had it happen before to him.
I have exported the model into the object library after saving the hierarchy changes and then dropped it into a new scene, saved under a new name, re-loaded only to find the changes are not retained by the scene file. I've tried various combinations of the above method all to no avail. I tried the above after I initially noticed that the switching the model hierarchy was not being saved.

Its a real strange one and I'm determined to try and nut it out. Its for Train Simulator and happens even after I reset the group hierarchy naming and then go through the process of re-naming the hierarchy prior to export. I may have to build new wheels for it as this is the main problem I'm encountering. I need to export the model with a specific hierarchy order for the game engine to animate the wheels turning and at the moment I have a wheelset on each bogies dragging and not turning at all.
Normally this is an easy problem to fix by simply re-organising the wheels hierarchy into the correct order but this is now compounded by the failure of 3DC to save the changed hierarchy.
Most frustrating.
I've sent Paul the model file to look at and see what the problem is. If there's a solution he'll find it.

Forgot to add that this happens also even if I save the project under another name. Perhaps the wheelsets are corrupted somehow ?

Here's how 3DC appears to handle groups....

Each group is allocated a sequential number at the time it is created

Moving groups around in the hierarchy tree is not a true reflection of the group order in the model, only a reload will show that.

The way I fixed this for Brenttons model was to add new groups in the correct sequence to the groups that needed re-ordering.
The new groups were positioned at 0,0,0 relative to the parent and all objects in the original group were moved into the new group (and the temporary new objects removed)
Each new group was then moved up one level, so the old group is removed as it contains no objects.
I suspect a "Select group", Copy and Paste in the correct order, followed by deleting the original group, may also work.

Cut and paste may not, as the group might retain the same sequence number.

Thank you for your help Paul. Back on track now.