4 réponses à ce sujet

[Killmonger]

Hey there all,

 

So while working feverishly with some simple geometry I noticed that max had moved my pivot point from 0,0,0 to the center of the geometry. I did not save that way. Max reports the pivot to still be at 0,0,0 but when I manipulate the geometry the gizmo is offset to align with the center of geometry.

What has happened?

 

1) The original file was saved with the pivot position at 0,0,0 and the lowest portion of the geometry recorded only slightly below 0. Most of the geometry is above the plane of 0.

 

2)Despite any effort to move (and save) the pivot back to it's origin position it remains centered to the geometry.

 

Could it be due to the base geometry being saved with the Aurora Trimesh modifier applied?

But other saves without said modifier are also afflicted.

I want the rotation to occur at the end of the geometry not the center

 

Most times I use the standard X Reset Xform in the max utilities rollout.

On occasion, I have used the NwMax v5.06.01 ResetXForm with SafePivots selected, But some of the files I am concerned with have never had that rollout by MDA applied. 

 

How do I fix/avoid this issue?

 

Only if I turn max off and on again do the files appear to be restored correctly.

 

A little assistance please?

[MerricksDad]

in maxscript listener, run this

toolmode.pivotCenter()

If that doesn't work, we'll try something else.

[MerricksDad]

As for avoiding it, I don't know how. I've come across it a lot over the years. While coding for max, I have found that max silently brain-farts and a process is not captured correctly. Many scripts (such as some of mine) overload the redraw cycle and it can then easily lose track of order of operations. I don't know why they wrote it that way. On my machine, a lot of times the last few lines of code may or may not actually process in any given script.

If you crack open some of the nwscript parts, you will see that it does some stuff you don't usually think of when you are doing stuff manually. Hard to explain if you haven't seen it, and there are a lot of little behind the scenes things that make maxscript perform faster for heavy loads.

 

So if you can imagine, a script may change the pivot point for some reason or another, and then at the end of that set of functions inside another function, they simply don't get run. But max doesn't know they didn't get run, and finishes the function call anyway. Leaving you with a few issues I have seen over the years, including:

 

enableSceneRedraw is disabled

toolmode.selectionCenter() is enabled

coordsys world is enabled

object.pivot does not match object.objectOffsetPos and object.objectOffsetRot

newly script-created object does not actually have a 3d structure in the draw window

array fails to populate with ANYTHING you just fed it

 

all very annoying. No really working around them, especially because checking for some of them requires you to code for it, but coding for it does not see issues in the display window.

[Michael DarkAngel]

What are you using, gMax or 3DSMax?  If 3DSMax, what version?  If you're using gMax or 3DSMax 6, 7 or 8, you could send a save file my way (tbotr at tbotr dot net), I'd like to take a look at what's going on.  If you're using something newer than 3DSMax 8, maybe take a screenshot.

 

 MDA

[Killmonger]

Thanks guys for the response.

 

For right now, I'm just trying to be super careful that I don't corrupt my output files. But I truly appreciate the wisdoms gleened.

By restarting max the problem seems abated. But when I have time to produce some screenshots of the problem I will upload for everyone's edification.

 

@MDA > I regularly use max7 (I prefer the "white" skin).

 

As yet I have not come across the problem in max12 (btw: Is there a way to change the "black" skin to white?)