The need to repeat Maxscript commands in order for them to work

[Anonymous]

I don't remember this being a problem until recently, but lately I've been finding that when I am running scripts I will have to run them twice in order for the intended outcome I'm looking for. It's as if the first time I run it it's getting ignored. I've attached an example of this weird behavior to this message- this screenshot is just a simple change of the coordinate system, but as you'll see in what gets printed out, I need to make calls multiple times to switch back and forth from local to world. Anyone know why this could be happening? 

[Swordslayer · Accepted solution]

It works as expected, quoting from the reference:

• All the set constructs are expressions that yield the context setting that was in force at the time the new context was set.
• This allows you to simulate the standard nested forms of these constructs by storing the old context in a variable and using that to restore the context later.

oc = set coordsys parent -- remember old coordsys
rotate $foo (quat 30 z_axis)
...
set coordsys oc -- restore it