Win7, MAX2014, D6. (This system dual-boots between XPx64 and Win7).
When in Win7 and MAX2014 and attempting to point RPM to the script file to use D6, the progress bars are shown successfully in green until near the end when they switch to red and the attached error is thrown. D6 fails to be setup in custom submit.
In XPx64 MAX2014, the D6 script file loads and works fine in RPM.
I have checked the filesizes, etc. between the MS used on XPx64 and Win7 and they appear identical (they were copied directly from the working XPx64 side to the Win7 side).
This is strange. It looks like it is failing while loading the SubmitMaxToDeadline.ms, and the try()catch() protection is catching that.
To debug this, you could try following these steps:
*Open the file “Deadline3dsMaxRPMClient.ms” that you are using to launch SMTD in RPM
*Add the line shown below to print the actual exception text to the MAXScript Listener
catch
(
SMTD_StartupDialog_Rollout.prg_loading.color = red
format "--ERROR: %\n" (getCurrentException()) <-- NEW CODE!
messageBox ("ERROR LOADING ["+(filenameFromPath theScript)+"] from \n"+(getFileNamePath theScript)+"\nError code: "+(theFilesToLoad[i][2]+1) as string+")") title:messageTitle
if theFilesToLoad[i][4] == true do
(
local goOn = false
exit
)
)
*Try to run RPM again and see in the Listener what is says when the error 1031 is reported. Post the text here and I will try to understand what is happening…
Bobo, thanks for looking at this but the problem now seems to be resolved.
At the time, I was using MAX2014 on Win7. (Not SP1 as AD killed the ability for MAX to function on XPx64, and my render farm is still XPx64 and I don’t take kindly to being told to spend 4K+ to rebuild systems when they are functioning fine as is). So I could not use SP1 on my workstation as I was not ready to use SP1 on the farm yet. (AD has since released SP2 which fixes the XPx64 problem). However at the time, MAX2014 was not operating flawlessly on Win7 (it was, however, operating flawlessly on XPx64). Marsel was working with me regarding errors that were being thrown on MAX2014/Win7 startup related to State Sets. (I don’t really use State Sets but since they are now part of MAX, they were being thrown upon startup). Marsel could not figure it out but as part of the process, the Autodesk.Max.Wrappers.dll was renamed to basically turn off State Sets within MAX and stop the errors. So it was at this time that the SMTD errors were being thrown (possibly by this renaming of the dll?).
Anyway, MAX2014 SP2 is now installed (since the farm will now work with it) and the new Autodesk.Max.Wrappers.dll is being used again and the SMTD custom submit error no longer happens.
