AWS intergration/rendering

[martythinkbox]

Hey there,
Not sure how far you guys have got with regards to best practices with AWS integration and rendering, but I will note my config and maybe you can suggest some things to try figure some bits out.

• Server 2012 node with all rendering software installed including deadline (pointed to deadline license server and repository)
• VPN connection to our local network
• Local network with working deadline repository

I can see the node pick up a license then job task then begin task, attached is the error report of said task.

As far as I can tell there appears to be an error/timeout to do with the customize.ms script, is there anyway I can tweak the timeout limits or check a log to glen any more additional info.

Any thoughts would be grand!
Job_2014-10-29_15-30-28_5451a2b395545a0950dd9044.txt (18.9 KB)

[MikeOwen]

Hi,
Thanks for the attached error report from 3dsMax. There are a number of issues in the 3dsMax report that I can help explain to you:

1. Win 8 & 7 are the only officially supported OS for 3dsMax 2014 according to the Autodesk min. system requirements. It will probably work on Win 2012 R2 server OS but I guess Autodesk have the option to flag this if you get into any further issues in the future. BTW - Deadline should work just fine on this Win OS.

2. You have missing plugins which although you can tell 3dsMax to ignore, it’s best practice to get as clean a setup as possible here:

2014/10/30 02:09:03 ERR: [03328] [03332] DLL <C:\Program Files\Autodesk\3dsMax2014_Plugins\ServerOnly\StokeMX.dlo> failed to initialize. Error code 126 - The specified module could not be found.
2014/10/30 02:09:03 ERR: [03328] [03332] DLL <C:\Program Files\Autodesk\3dsMax2014_Plugins\ServerOnly\hotOcean_Max_2014.dlm> failed to initialize. Error code 126 - The specified module could not be found.

3. You need to make sure all machines have the latest SP 5 for 3dsMax 2014 installed. I would never cross-submit between versions. Keep everything identical is key here:

0: INFO: Slave 3dsmax.exe version: 16.1.178.0
0: INFO: Slave 3dsmax.exe description: 3dsMax 2014 + servicepack_sp1
0: INFO: Submitted from 3dsmax.exe version: 16.5.277.0
0: WARNING: Slave’s 3dsmax version is NOT the same as the 3dsmax version that was used to submit this job! Unexpected results may occur!

4. Please can you update to Deadline v6.2.0.32 (public release) as you are running v6.1. (If your on support, please contact sales@thinkboxsoftware.com for an updated v6.2 license file). If you hang on for say another week, as per my announcement in our Deadline webinars earlier this week, there will also be a v6.2.1 maintenance release, which is highly recommended.

5. Finally, the actual sticking point to stopping the job from rendering is more than likely “StateSets” dialog being visible when you submit the job or more importantly, “StateSets” metadata is present (saved) in the actual Max scene file. I’m working on an automatic fix for this which should hopefully ship with Deadline v7.0. However, for the time being, if your not using State Sets and your running Deadline Slave / 3dsMax as a service, then please follow the instructions in the attached infographic to remove all trace of State Sets in your scene file prior to submitting. Note, this needs to be done per scene file.

[attachment=0]How_To_Fix_State_Sets_Issue_3dsMax.png[/attachment]

Finally, the “customise.ms” issue is a false positive and the solution is NOT extending timeout, but rather fix the issues above, namely #5 in this case.

Regards,
Mike