3Dsmax2023 migration with filein function used

[administrationFUNCG]

Hello,

I use Scripted plugin object based on the Helper class who launch scripted when scene are open.
Basiquely, you create this null object in your scene and you assign a script file to launch when it will be open with the scene.
The embeded script use the filein function to run the defined script file in the object property.

It works perfectly in 3dsmax2021 (local and commandline) but since 3dsmax2023 it seams to not working properly on AWS/Deadline (so in command line) but still working on local.

Do you see the reason? is that a security tool issue?

launching *.ms file through objects in scene opened through commandline...

in the custom script I used mergemaxfile function and #filePostMerge callback, maybe it s more about that?

thanks

[administrationFUNCG]

Hi,

I push my investigation deeper,
Forgot the custom script, I tried to simplify it by just launching the Merge function and it do nothing on AWS/Deadline.
So the problem is more from the scriptedplugin that have a "filein" function within a "on load" event to run this Merge function.

Do you know if there is restrictions regarding this structure and what would be the good way to have an object in the scene that load custom scripts when it load.

let me know thanks

[denisT.MaxDoctor]

try disabling the "Security System" on your machine first and see how everything works without it...

[administrationFUNCG]

Hello Denis,

it seems to not working 😞

samething...

[denisT.MaxDoctor]

You haven't provided any code, example scene, or error messages... I'm out of blind advice.

[administrationFUNCG]

Oky just ask and I ll provide 🙂

first step is to know if the problem is known 😉
I tested different things and now I know that it works with a simple Box to merge.
now that indicate to me few possibilities...
-there is timeout in 3dsmax2023 or Deadline for 3dsmax2023 that kill the load before the end through Deadline.
-there is limit regarding the file size in 3dsmax2023 through Deadline
Because the test pass with a box to load (272kb) but not with 352Mb file model...
Unfortunately I can't join the model to this forum... but the file merge perfectly in local way... very disturbing...

Here I put 4 files (scripts in zip file)
PIXIscriptstarter.ms : the scriptedplugin that un automatically script on load

TEST-ISSUE.ms : the script that the PIXIscriptstarter need to run

test-issue2021.max : the scene that contend the PIXIscriptstarter object (without problem)

test-issue2023.max : the scene that contains the PIXIscriptstarter object (with problem only with Deadline)

Normally if the filepath to merge in the TEST-ISSUE.ms is correct and you install well the scriptedplugin in your 3dsmax2023 and or 3dsmax2021, when you open the scene, it will merge the external file into the scene automatically.

it work for both version of 3dsmax but not if I pass through Deadline only with 3dsmax2023...

[administrationFUNCG · Accepted solution]

ok I solve the issue

The file that we tried to merge is the issue.

How did we do that :

We convert the scene from 3dsmax2021+vray5 to 3dsmax2023+vray6

We did that by opening 3dsmax2023, open the scene that is compatible in this way, and we save this scene as new version 2023.

It seems, we this method, Deadline + 3dsmax2023 + vray6 + scriptedplugin + unluck, detect something with wrong conversion in the scene to be merged.

What was my workaround : open a new 3dsmax2023 scene, merge all the 3dsmax2021 scene objects in and save this scene and now it works on deadline…

Hope that case can helpe anyelse

Thankyou Denis

[denisT.MaxDoctor]

I looked at your pipeline ... I don't see the point of such a complicated setup if you have to deliver the plugin file anyway. It can only be useful if the MAX file will be sufficient for distribution by itself, without additional accompaniment by other files (plugin, script, etc.).

but you can partially improve your pipeline if you replace the plugin with a custom attribute...