Infuriating transform problem

[re:FORM]

Anyone had this problem where after, say, unparenting a onyx leaves from its treestorm object, it seems to mess up all transforms such that when you try to move any object(including new objects in new scenes!) in the scene they end up flying away at high speed?

I think I need to go and lie down....

/// edit /// That's right, even RESETTING and making a sphere then trying to move it results in the sphere flying off exponentially faster into oblivion. I cant work out if its vray mesh to proxy or treestorm thats the culprit (or max2008 for that matter). I remember having this problem a long time ago but it was never this regular!

[Clifton Santiago]

Sounds like a origin problem. Or geometry that has been moved more than 100k units away from the origin. Can you select a stable mesh object and then attach the offending geometry? Detach later if necessary...

[mikeh]

Anyone had this problem where after, say, unparenting a onyx leaves from its treestorm object, it seems to mess up all transforms such that when you try to move any object(including new objects in new scenes!) in the scene they end up flying away at high speed?

I think I need to go and lie down....

/// edit /// That's right, even RESETTING and making a sphere then trying to move it results in the sphere flying off exponentially faster into oblivion. I cant work out if its vray mesh to proxy or treestorm thats the culprit (or max2008 for that matter). I remember having this problem a long time ago but it was never this regular!

The flying away problem was what i had when using the maxtreme driver for my nvidia card. i dumped that driver and use the latest from their website and only use the OGL...not direct whatever it is. This is on a 64 bit machine. When your max crashed it may have reset your settings to something other than what you want. Onyxtreestorm crashed my max and corrupted the ini file that loads the toolbars. i had to delete it and let max rebuild it.
mh
mh

[re:FORM]

Hi aaron,
Well it can't be an origin problem I would have though, if when you go to file-reset, and create a new sphere, the problem is still there. Restart max entirely and the problem is fixed.

It might be a problem with the ini file that gets fixed whenever you exit max... but I never need to delete the ini file like you describe. I'm using directx drivers for my video, not openGL so that may be a contributing factor. Maybe treestorm works better in opengl.... I'll do some experimentation when my blood pressure's dropped a bit.

I've resorted to importing 3ds files from onyx and all my troubles have gone away....

[Sawyer]

I have had a similar problem where when I try to move certain vertex's just a nudge they fly 100' feet or so away. Restarting max will fix that for me. But its a pain in the ass.