running script at file open and access global variables in UI

[mark_aldred]

I have a script controlling objects and to get it working I'm evaluating it after I open up the file containing the objects. I have two questions ..

1. what's the best way to set it up so that the script is evaluated automatically when the file is opened?

2. what would be the best way to make for example the variable "speedMultiplier" available in the UI?

Here is a sample of the script ..

global speedMultiplier = 1000
global plMultiplier = 4.029
global initialPlPosition = 254.52
global positionOffset = 0

$pl.position.controller=position_script()
$pl.position.controller.script = "$pl.transform.controller.Position = [$plOrbit.radius*cos(positionOffset+initialPlPosition+360*speedMultiplier*plMultiplier*F/2700), $plOrbit.radius*sin(positionOffset+initialPlPosition+360*speedMultiplier*plMultiplier*F/2700), 0]+$plOrbit.transform.pos"

[miauuuu]

1. use callbacks

callbacks.addScript #filePostOpen ...

2. the "speedMultiplier" is defined as global variable, so you can access it directly in your UI

[mark_aldred]

Thanks.

So if I evaluate a script as part of a callback, that script is registered with the file and executed for example on #filePostOpen? Where does the script actually reside? What if I want to edit the script? Is there a way to access it from inside max, or do I have to edit an external copy and evaluate that?

[miauuuu]

The script resides in 3ds max memory. To edit it while 3ds max is running open the script(from the maxRoot/scripts/startup folder if you placed it there), edit it in the MaxScript Editor. Then save the script and evaluate it. 3dsMax will use the updated version of the script(because you evaluated it). And, since you edit(and save) the script in the startup folder, next time you run 3ds max the updated script will be executed.

[mark_aldred]

Thanks.

So a callback script has to be saved in the startup folder? I thought maybe it would be saved as part of the *.max file. If it's a separate file, the only advantage is that it can be executed automatically? Not that it travels as part of the max file?

[miauuuu]

To bind your code to the max scene try this:

[code]

myCA = attributes myAttributes
(
fn My_Fn =
(
-- "code to execute goes here"
)
-- "should be executed when the file is open"
on load do My_Fn()
)

custAttributes.add rootnode myCA

[/code]

Save the file, reset 3ds max, load the file.

[Serejah]

---

@mark_aldred  написал (-а):
... I thought maybe it would be saved as part of the *.max file. If it's a separate file, the only advantage is that it can be executed automatically? Not that it travels as part of the max file?

---

You can place the script inside custom attribute, scripted controller so it will be stored in max scene file.

Another story how would it execute when you load the scene. Especially after AD introduced super-security-anti-virus thing it could be a problem.

[mark_aldred]

Thank you both!

The custom attribute is working. Is this the normal way to do things?

Regarding callbacks, what is the difference between callback and bind? Are callbacks never saved with the file?

Apologies for all the questions. I'll go through help myself too.

Edit: Incidentally, where do the custom attributes reside and how can I access them?

[mark_aldred]

Bump: anybody know how I can access those custom attributes?

Thanks

[istan]

https://help.autodesk.com/view/MAXDEV/2022/ENU/?guid=GUID-ADFD29E4-9751-4F55-98CC-F7C721C9AEE2 

[mark_aldred]

Thanks. I've been looking at that page.

I have a couple of questions ..

"Custom attributes is currently supported only in the Material Editor and the Command Panel, so you can only see any rollouts associated with the custom attributes on base objects, modifiers, and materials."

This means I need to associate a custom attribute to some kind of object to be able to create a rollout?

And .. how can I actually access the custom attribute script itself? Do I have to save it separately and execute it every time I edit?

All I need is an editable script that travels with the file.

[istan]

From a security point of view, I would not allow the execution of a script, which comes with a scene. The same applies for word, excel, ppt,.. files.