3dsmax 2010 Support for Deadline 3.1

Deadline
21

I think I’m getting the very same problem as mbort after just updating to 3.1 SP1…

22

Ack, I think I was getting my Deadline versions mixed up. Deadline 3.1 SP1 included Max 2010 support out of the box, so the patch isn’t required if you’ve installed this version. The patch is only necessary if you’re running the original Deadline 3.1.

If you guys reinstall the Deadline 3.1 SP1 repository (just install over the existing repository without uninstalling), it should restore the changes the patch made. Then, you can setup submission using the mcr file \your\repository\clientSetup\3dsmax and we can go from there.

Sorry for the confusion. :blush:

Cheers,

  • Ryan
23

I didn’t apply the patch, I’ve just installed 3.1 SP1 over 3.1.

With the new SMTD which comes with the SP1 (…\DeadlineRepository\clientSetup\3dsmax\Deadline-SubmitMaxToDeadline.mcr), I get the “Runtime error: No such macro-script: SubmitMaxToDeadline” error in Max. Using the non-SP1 3.1 SMTD script works without throwing that error.
It’s no biggie for me to continue using the previous SMTD script if these is no functionality lost.

Any thoughts?

24

Can you post the …\DeadlineRepository\clientSetup\3dsmax\Deadline-SubmitMaxToDeadline.mcr and …\DeadlineRepository\submission\3dsmax\SubmitMaxToDeadline.ms files from the new 3.1 SP1 installation? I’ll take a look at them and try to figure out what the cause would be.

Thanks!

25

I’ve attached the files.

Thanks Ryan.
Deadline-SubmitMaxToDeadline.zip (38.6 KB)

26

Hmm, it looks like the SubmitMaxToDeadline.ms file in the repository wasn’t updated properly. I’ve tweaked the mcr file so that it should now work with your current SubmitMaxToDeadline.ms file. Just install it like you did for the other clientSetup mcr file and let us know if you have any problems.

Cheers,

27

rrussell,
thx, i did a “repair” in the 3.1 SP1 Repository installation, and get the original sp1 .mcr file.
It works, the maxscript seens ok now.

but i’m still having some problems with external map files. The unique solution so far is to point the mxp file.
A new option came with the .mcr from 3.1 sp1, “Cache Textures On Slave”, but when i select i got an error:

“could not find Auxiliary submission file: \render01\DeadlineRepository\submission\3dsmax\DeadlineMaxCacheTexturesOnSlave_PreLoad.ms (Deadline.Submission.DeadlineSubmissionException)”

there is no file there beggining with “DeadlineMax”

Copy Local/All to repository didn’t seens to work as the file is copied with and different name the job goes Red when i tell deadline to not ignore missing files.

Is that normal?

28

Thanks Ryan,
It looks like you were right that it wasn’t updated properly.The version you uploaded works fine…
Is there any difference between the 3.1 and the 3.1sp1 versions of SMTD?

29

Rob:
There are differences, but because the change I made was in the mcr file, you’re actually using the 3.1 SP1 version of SMTD. Sounds like doing a repair on the install fixes the problem though, so it might just be best to do that (see post above this one).

mbort:
The “Cache Textures On Slave” option was a beta feature we were testing internally, but everything that is required to use this feature will be included in the next release.

We’ll look into the external map file problem to see if we can figure out what’s going on. Glad to hear that there is a workaround for now though.

Cheers,

  • Ryan
30

The external map problem was actually a 2 part problem. The first being that the external files were being renamed to something like “{FDC1670A-18F3-4BD5-9BB3-255B6DD65CA9}”. This is actually a 3dsmax 2010 problem that was fixed with by a recently released Hotfix. The new Asset Handling was causing MAXScript to see the internal ID of the resource instead of the file name.

Download:
usa.autodesk.com/adsk/servlet/ps … ID=9241178

Readme:
images.autodesk.com/adsk/files/3 … eadme1.htm

After installing the patch, the file names were saved correctly, but Max still wasn’t finding them. Something else that changed within Max 2010 was that Max was no longer including the scene folder in the session paths. More specifically, it was including the deadlineMaxStartup.max file path, which Deadline passes to max on startup, but not the path to the actual scene file that was loaded after the fact. We were able to implement a fix, but unfortunately this will have to wait until Deadline 4.0 is released around the end of November.

Thanks again for bringing this to our attention, and hopefully the workaround you’re currently using gets you by until the new release comes out.

Cheers,

  • Ryan