[Closed] Evaluating script != Run Script?

Question, if you ‘Run Script’ it twice does it do what you imagine it should?

Things like this tend to be a variable scope issue, IE: you may be assuming a variable is set earlier than it really is in your script, since it may be left over from the previous run?

Hard to say without seeing the script exactly though.

It’s a script to make it easier to mirror morph targets, and it might be a little hack-ish, but as described, it does work when evaluating

edit: should probably add instructions (I’d add interface etc to it but I want to get it working first!), what you do are:

1. Copy the morph target
2. Mirror it
3. deselect everything
4. select your “base” mesh
5. while holding Ctrl, select the mirrored morph target
6. run script
7. if done from editor, rejoice, if done using run script, tear out hair and spend a few hours muttering “I don’t get it”

The script is this:

  
  			starttime = sliderTime
  			sliderTime = 0
  			basemesh = selection[1]
  			leftexpression = selection[2]
  			print ("Base mesh: " + basemesh.name)
  			print ("Mirror morph: " + leftexpression.name)
  			addModifier leftexpression (Morpher ())
  			WM3_MC_BuildFromNode leftexpression.morpher 1 basemesh
  			sliderTime = 10
  			with animate on
  			(
  			WM3_MC_SetValue leftexpression.morpher 1 100.0
  			)
  			baseduplicate = Copy basemesh
  			baseduplicate.pos = leftexpression.pos
  			addModifier baseduplicate (Skin_Wrap ())
  			baseduplicate.modifiers[#Skin_Wrap].meshList = #(leftexpression)
  			baseduplicate.modifiers[#Skin_Wrap].distance = 0.001
  			sliderTime = 0
  			convertToPoly baseduplicate
  			leftnavn = leftexpression.name
  			leftwire = leftexpression.wirecolor
  			delete leftexpression
  			baseduplicate.name = leftnavn
  			baseduplicate.wirecolor = leftwire
  			sliderTime = starttime
  
  

Out of curiosity, what happens if you use the Evaluate command in the Script Editor’s menu instead of Ctrl+E?

The obvious difference between running and Ctrl+E is that the Ctrl key is pressed down while the script is running (or at least in the beginning), which I have seen causing a difference.
Also, it would be cool to know WHAT exactly goes wrong when using Run, which would be the first step to debugging the problem.

Thanks for your answers Vsai and Bobo,

I tried Evaluating from the menu, same result as using Ctrl+E, so still working.

What happens when I Run Script instead, is that the mirrored target turns into the Base mesh, rather than the mirror of the Morph Target.

I’m rather confused as to why this happens, the script is pretty short, I’ve tried commenting out small parts of the script, but with no success so far.

It looks to be a scope problem- putting the script in parenthesis and evaluating yields the ‘Run Script’ result. I don’t think the time is changing, but I’m looking now.

And the problem is definitely something to do with the selection[] lines (assigning an object like $Sphere01 works correctly both ways). Even though basemesh and leftexpression are not undefined, they are not being added to the morph modifier- this is the cause of the result.

And interesting enough, the “WM3_MC_BuildFromNode” function that is not working is returning ‘true’ nonetheless.

(
	local base = selection[1]
	local theMorph = selection[2]
	
	local m = Morpher()
	
	WM3_MC_BuildFromNode m 1 base
	
	addModifier theMorph m
)

That doesn’t work (base is not added as a target to the morph modifier), no matter what I do with the modifier. I think this is a bug, also using Max 2008 32 bit on XP SP2. Also same result on Max 9 32 bit.

Yeah the selection[1], selection[2] part is definetely a bit hackish, and I suspected that as well. But I went ahead and built an interface with pickbuttons, and it gives the wrong result as well. The reason I used selection[1] selection[2] is that is was just intended as a quick fix to get some morph targets mirrored here and now. The thing is, I’ve tried adding prints to all sorts of places in the script, and it IS returning the right objects, but it’s simply not working when “Run”, only when evaluated from editor. Can any of you confirm (or deny) the errors I’ve seen (ie, it works when evaluated, fails when Run Script) ? I’ve tried it myself, and the animator (who discovered the error) has the same problem on a seperate PC, but it’s such a strange error that I still think it might be some quirk we’re only having with our installations (though there’s little to no custom stuff about them except for having a lot of versions of Max installed, in some cases all the way back to Max 6).