Hi Mike, yeah the normal way to use them is to set up a keyboard shortcut and then push that key to trigger it.

Go to Options > Shortcut keys, and push "Add" to put in a new entry, in the Command part of the shortcut key put in: DistortCurves (or _DistortCurves if the files start with an underscore).

If you're trying to use them from the CustomUI, how is it that you're setting them up there exactly? I guess they are probably being run as an "instant script" instead of being run as a "command". When a command is launched, there are various other things that happen like the command system loads the .htm file that contains the command's UI part (and sometimes some of the code too), but when script code is launched as an "instant script" those things don't happen and so that's probably what you're running into at least that's my best guess currently.

Anyway, please try setting up a keyboard shortcut and see if that works ok for you or not.

- Michael

Hi mikebres,

I see that you have "My.scripts" and also "All.scripts" in the custom ui. Maybe that is the problem?
I've never set up that way. I think Burr had some such posts a while back, in the custom ui discussion?

Maybe here: http://moi3d.com/forum/index.php?webtag=MOI&msg=6507.58

Normally using the scripts is "easy."

The original Moi Shortcut key method should work well, and "easy." Both methods can be set up, and work "side by side."

- Brian

Does your ini file have an old path in it?

That was it. It needed to be setup as a shortcut. For future reference how are we to know which way to set it up?

Thanks

The customui just automatically finds and uses "what you have"... ot comes kindof preconfigured with some stuff " hence the underscore command that doesnt exist... i suspect your config files arent setup quite correct.

The config for MOI, or the Custom UI? Thanks.

Both.

Check your MoI ini file to see if it has an executable path in it and if it pointing at the installation you are using...

Also, I think I remember the customUI comes with some of the commands "preconfigured" with some of the scripts/commands, and included that underscore.... It's been awhile, so I don't remember off the top of my head, and I am not at my install setup to check the original stuff...

Either someone else can chime in on it, or I'll get a look a bit later and get back to you....