Can I get an update on this, Grant/Bobo/Ryan?
I would like to know how we can sort this issue out once and for all 
Iāve been using the RPM Submission script for 6.0, I edited the file as Grant noted above to add the final closing parenthesis.
Iāve submitted a few dozen jobs through it now, and Itās been working fine for me. The only thing that tends to trip me up is when the network tab is set to āSAVE and use original scene fileā - This inevitably breaks visibility/properties sets etc, so needs to be switched to submit to repository, instead. This seems to happen on existing scenes (originally set up using the 5.2 script) rather than new ones, though.
Sam
Attached is an updated RPM script for Deadline 6. There is a new rollout below the original Dependency rollout that should set up dependencies similar to how they are set up for backburner. They should also work on top of any dependencies defined in the original Dependency rollout.
Limitations:
- The checked list is index based only ā if you reorder your RPM pass list, the checks do not reorder. This may be as designed.
- If you reorder your RPM pass list, it wonāt rebuild the dependency list though it will if you restore a pass, or add/delete a pass. Renaming a pass wonāt update either but if you then restore it will. It will need a modified RPM for some extra calls if this isnāt enough updating.
Please test it out and let us know if you run into any problems with it.
Thanks!
- Ryan
Deadline6_20130129_mod.zip (243 KB)
Hi,
so i tested the new RPM submission script.
the script works just fine. also the new RPM pass dependencies option is doing exactly what i needed!
i also trued the do multiple submissions and that worked as well.
the only problem that iāve encountered is that i canāt submit frame per task of 1. the minimum is 60 for some reason.
but i tried to submit with the regular submitter and the problem repeat itself. so iām guessing that itās not an RPM submission script problem but a deadline problem.
Thatās odd about the frames per task. I checked the code in the RPM and SMTD scripts, and weāre setting the minimum to 1:
spinner spn_chunkSize "Frames: " range:[1,1000,1] type:#integer align:#right fieldwidth:40 offset:[0,0]I also tested both RPM and SMTD myself, and had no problem setting the frames per task to 1. Are you able to set it to 1 in the submitter, but then it shows up as 60 after the job has been submitted?
this is the error that i get when i type 1 in frame per task:
Submission Error: The task count of 196 exceeds the limit of 60, increase the frames per task and try again
i also attached the log file
SubmitMaxToDeadline - [SB-PRE-OMERE] - 03-04-2013-0197.log (12 KB)
Hi Omere,
Can you fish out the files
āC:\Users\omere\AppData\Local\Thinkbox\Deadline6\temp\03_04_2013_16_57_23\max_submit_info.jobā
āC:\Users\omere\AppData\Local\Thinkbox\Deadline6\temp\03_04_2013_16_57_23\max_job_info.jobā
and send them over?
The SMTDSettings Struct shows Chunksize of 1, so the number 196 is nowhere to be found in the actual settings. But it is obviously somewhere in the submit info file if the deadlinecommandbg is complainingā¦
Thanks in advance!
Thanks for the log. It looks like you just need to increase your global task count limit, which can be done in the Monitor. Enter Super User Mode, then select Tools -> Configure Repository Options. Select Job Settings from the left, and under the Job Scheduling tab, youāll see a Task Limit For Jobs setting. Iām guessing this is currently set to 60. The default is 5000, so bump it up to that, press OK to commit the settings, and then try submitting again.
Cheers,
- Ryan
yaayy!!
that solve the problem.
everything is working just great now. and so from tomorrow we will start using deadline in production.
thank you very much. i will update how it goes and if we have any problems
sorry for coming back so soon. 
we encountered a problem while using the RPM dependencies system. if we enable it and mark, letās say a pass name āGIā, as the pass to be dependent on. and the next pass to submit is called āBGā.
the result, as expected will be that the āBGā pass is marked at the monitor as āpendeingā. then it will start rendering once āGIā reached 100%.
but, if we later submit only the āBGā pass, and the RPM dependencies is sill enabled. the result is the the āBGā pass is still appearing at the monitor as āpendingā. but when checking the dependency list, nothing is listed. and so āBGā is jut waiting in the render farm.
Which version of Deadline 6 are you guys running? You can check the version number in Help -> About. I checked our code, and if a job is submitted with an empty dependency list, it shouldnāt be put in the pending state in the first placeā¦
our version is 6.0.0.50841
Hi,
another thing that weāve encountered is that after submitting, deadline doesnāt remember the machine limit that was set in RPM SMTD.
also,every submission we need to set the settings. is there a way to create a default submission settings?
and lastly, after settings pools in deadline monitor, i can choose the pools and submit them, and i see the jobs assign to the pools in the monitor. but if i want to change the pools in the monitor, the only pool that i can see in the drop down list of the job properties is ānoneā.
thanks
Thanks for the version number. I looked into the dependency problem today, and there seems to be two issues:
-
It seems that RPM caches the job ID for each pass that was previously submitted. So when you submitted just the BG job the second time, it sill made it dependent on the previous GI job. This is why it shows up as pending in the Monitor, and Iām assuming that the GI was no longer in the queue, and thatās why it doesnāt show up in the BG jobās dependency list. Which brings us to issue 2ā¦
-
If a job is submitted to the queue, and it has a list of dependencies that donāt exist, it is still put in the pending state. Now Iām not sure if this should be classified as a bug or not, since Deadline gives you explicit control over whether a job should resume on deleted dependencies or not. However, the big problem is that there is no way to remove missing dependencies from a job because the Job Dependency form doesnāt show them. In beta 18, we will fix the UI so that missing dependencies show up as Deleted, so that you can remove them.
So for (1), weāll have to get Grantās take on this, and figure out what (if anything) can be done about this particular problem.
I canāt seem to reproduce this, although Iām testing with a newer version of the script where RPM just loads the SMTD scripts, rather than using its own. We hope to include these new RPM/SMTD scripts with beta 18, so youāll have to test it once itās released and let us know if this continues to be an issue.
Youāll be able to do this like you can with SMTD in beta 18.
thinkboxsoftware.com/deadlin ā¦ y_Defaults
This is a known bug that will be fixed in beta 18.
Cheers,
- Ryan
thanks. iāll wait for beta 18 and see how it works.
where do i find the option for controling over whether a job should resume on deleted dependencies or not?
Itās currently only exposed in in the job properties window in the Monitor.
Cheers,
- Ryan
the weird thing is that from shot to the dependencies acts differently.
some times it will be just fine. on other times the job to be dependent on is also pending (but has no job in the dependencies list, it goes the same for the dependent jobs).
and the other situation is that even though the RPM dependencies is active the jobs are submitted without dependencies and as active. as if the dependencies option is turned of.
Grant sent us a fix that should deal with the dependency problem. Weāll be including this in the upcoming beta 18 release, which we hope to get out this week.
Cheers,
- Ryan
great! thanks
Hi guys,
iām testing with the new versions of deadline and RPM SMTD and the dependencies still not working.