Hi all,
I’m having trouble getting Krakatoa to detect and use deadline for partitioning.
I am running Krakatoa v1.6.1 in a 64-bit installation of 3DS Max 2012. I’m also running Deadline 5.0 with a functioning SMTD 5.0 script installed. I can submit render jobs to deadline just fine, and krakatoa works just fine as well, but when I go to the partitioning tab and click Detect Deadline Now! I get the following in my Krakatoa Log Window:
PRG:
PRG: -----1/3/2012 2:20:04 PM--------------------------
PRG: >Opening Krakatoa GUI…
PRG: >Initializing Krakatoa Renderer v1.6.1.44739…
PRG: +Krakatoa Renderer INITIALIZED in 3 milliseconds.
PRG: +Krakatoa GUI Floater OPENED in 3398ms.
PRG: >Detecting Deadline Render Manager…
PRG: +Submit Max To Deadline Functions ALREADY LOADED!
PRG: >Detecting Deadline Render Manager…
PRG: +Deadline Render Manager DETECTED on your system!
ERR: -FAILED to load Submit Max To Deadline Functions!
WRN: -FAILED to Detect a supported version (3, 4 or higher) of Deadline Render Manager.
I noticed another user had had this problem earlier, but their solution (submit a normal job through deadline, leave the gui open, then try to detect deadline in Krakatoa) didn’t work for me. I’ve also checked that the system path is correct by typing deadlinecommand at the win7 command prompt. It saw deadline successfully, so that’s not the problem either.
Is there any other information you need to help diagnose this problem? Or is there a known solution?
Thanks!
–David
Edit:
Additionally, as per the previous post, running FranticParticleRenderMXS.DeadlineDetected returns a value of 0.
Steps to recreate this error on my machine:
-Launch Max
-Krakatoa Menu -> Bring Krakatoa To Front!
-Click Yes in the “Switch To Krakatoa” render dialog
-Click Detect Deadline Now!
-Error appears immediately.
This was a clean install of Max followed by a clean install of deadline, followed by a clean install of Krakatoa, finishing with the Add Krakatoa To Max shortcut in the Start menu.
Finally, if I run 3DS Max as administrator, I get a slightly different result:
PRG: >Detecting Deadline Render Manager…
PRG: +Deadline Render Manager DETECTED on your system!
WRN: -FAILED to Detect a supported version (3, 4 or higher) of Deadline Render Manager.
Do you have any Service Packs or Hot Fixes installed on your 3ds Max 2012?
The shipping plain vanilla version of 3ds Max 2012 has a SIGNIFICANT bug in MAXScript - if you create a file via MAXScript, it cannot be closed, which also makes it impossible to read.
This bug makes both Deadline and Krakatoa fail at strange places without warning, and it requires at least the hot fixes or better the Service Pack 1 or the Subscription Advantage Pack to make it work.
If you have a plain 3ds Max 2012 install, it could be that.
You can try running this simple script to see what you would get:
a = createFile (getDir #temp + "/test.txt")
format "Testing\n" to:a
close a
a = openFile (getDir #temp + "/test.txt")
readLine a
close a
If it throws an error, you MUST update 3ds Max 2012.
Bobo, thanks for the fast reply!
Unfortunately, though, that wasn’t the solution. I’d already run hotfix 1, and your maxscript code didn’t kick up any errors.
Now I’ve downloaded Service Pack 2 just to be thorough, but still no luck.
I am reading through the code and it is quite possible it is some permission / folder definition issue. Not sure why nobody else it getting it, but let’s try to debug it.
Can you tell me what you get when you run the following commands:
This would be set just before the block that throws the error, so it might point me in the right direction.
Then, the location of your Script files:
GetDir #scripts
On my machine this points at the \Scripts folder and might require Admin access. But you did not get the same error in Admin mode, so it might be related…
Once I have the results of these calls, I might send you an updated version of KrakatoaGUI.ms that prints more about what it does when it fails to debug this.
I ran Service Pack 2, and then ALSO ran max as administrator. Now it detects deadline just fine.
I suspect it’s a UAC thing, which I’ll set down to zero.
Well, I would say this is a workaround and not a fix.
We should fix it so it works with UAC at maximum
Would you be interested to participate in the testing?
I can send you a version of KrakatoaGUI.ms with the try()catch() disabled to see what exactly was causing the initial problem.
Then I could fix that and you would not have to run in admin mode with UAC down…
Actually, you need a 1.6.x version, my fix was for 2.0.
Instead, try this:
Open the file KrakatoaGUI.ms and search for #scripts
Then replace it with #userscripts
Save the file, enable UAC, log in as non-admin and try again!
