AWS Thinkbox Discussion Forums

"Machine list is a blacklist" not sticky in Nuke

Deprecated Deadline 6 Bug Reports
#1

The Machine List is a Blacklist option is not sticky, but the machine list itself is. So if you whitelist machines for one render, then submit another render… the exact opposite is now the case. I would argue both should be sticky, however regardless what you decide you have to be consistent in this matter. :smiley:

#2

Which beta version are you running? I just tested our current internal version of beta 8 and this works fine…

I tested both the integrated submitter and the Monitor submitter.

#3

Oh, I think it’s using an outdated python script. My bad. Looks like the init.py is loading a fixed copy from 3/11/13

#4

Nope, that’s not it. The Deadline-NukeClient.py just points to the repository so it shouldn’t be out of date:

[code]import os, sys
import nuke, nukescripts

def main():
# Get the repository root
try:
stdout = None
if os.path.exists( “/Applications/Thinkbox/Deadline6/Resources/deadlinecommand” ):
stdout = os.popen( “/Applications/Thinkbox/Deadline6/Resources/deadlinecommand GetRepositoryRoot” )
else:
stdout = os.popen( “deadlinecommand GetRepositoryRoot” )
path = stdout.read()
stdout.close()

	if path == "" or path == None:
		nuke.message( "The SubmitNukeToDeadline.py script could not be found in the Deadline Repository. Please make sure that the Deadline Client has been installed on this machine, that the Deadline Client bin folder is in your PATH, and that the Deadline Client has been configured to point to a valid Repository." )
	else:
		path += "/submission/Nuke/Main"
		path = path.replace("\n","").replace( "\\", "/" )
		
		# Add the path to the system path
		print "Appending \"" + path + "\" to system path to import SubmitNukeToDeadline module"
		sys.path.append( path )

		# Import the script and call the main() function
		import SubmitNukeToDeadline
		SubmitNukeToDeadline.SubmitToDeadline( path )
except IOError:
	nuke.message( "An error occurred while getting the repository root from Deadline. Please try again, or if this is a persistent problem, contact Deadline Support." )

[/code]

#5

I also see:

Reading sticky settings from C:\Users\ggreenwalt\AppData\Local\Thinkbox\Deadline6/settings/nuke_py_submission.ini Found a total of 2 write nodes Creating submission dialog... Writing sticky settings...

#6

Ok, I just went ahead and hand edited the INI… but it still is sticky with the wrong settings.

[code][Sticky]
draftextraargs =
draftversion =
draftuser =
draftentity =
machinelist = daedalus,harvey,pongoloid,beastmaster,render-i7-01,torin-tk421
usenoderange = True
group = i7_v01
concurrenttasks = 1
priority = 50
continueonerror = True
drafttemplate = T:/Scripts and Extensions/Draft/FootageDump.py
department =
submitscene = True
framelistmode = Global
limitgroups = nuke
chunksize = 10
batchmode = True
threads = 0
customframelist = 0-73
isblacklist = False
limitconcurrenttasks = True
pool = urgent
submitsuspended = True
machinelimit = 0
usedraft = True

[/code]

So I think the read/write INI code is broken somewhere.

#7

Heh, you still didn’t answer my original question - which beta version are you running? :slight_smile:

The python script on your local machine is just a proxy that calls the one in the repository, which gets updated whenever you update the repository. Beta 7 introduced a feature where sticky settings are now stored in the nuke script you are submitting, and beta 8 fixes a bug were sticky boolean values weren’t retrieved from the nuke script properly.

#8

Latest, Deadline Beta 7 as of last night. I’ll try 8 tomorrow.

Privacy | Site terms | Cookie preferences