quicktime - job dependancies and draft

Deadline
1

I used to use the generate quicktime feature constantly, however now when i submit this the render job and the quicktime assembly job both appear, but the dependency is missing.

It appears as though I could be using draft to do this, but it seems like an overkill as I just want a quicktime from my frames, no overlays or slates or anything.

any ideas why the job would submit without the dependency?
thanks,

2

Hi,
Could you confirm what ‘render’ job you are referring to and how you are submitting the job into Deadline? via in-app submission script? If so, what app? Or via monitor submission script? If so, which one?
Thanks,
MIke

3

I am submitting to deadline through Max in the app
“render job” would be a frame sequence of PNGs
we are running deadline 6.1

Thanks for your help

4

Hello,

Could you provide the steps and settings you are using to trigger the dependent job, as I just want to have something to go by in trying to reproduce. Thanks.

5

Hi,
Right, got to the bottom of it. It’s just a spelling typo. To fix:

  1. Backup this file before doing anything to another file location: “[repo_path]/submission/3dsmax/Main/SubmitMaxToDeadline_Functions.ms”
  2. Open this file in a text editor and look for this line of code around: line #2971, it should look like this:
if SMTDSettings.RegionRenderingMode != #node and SMTDSettings.RegionRenderingMode != #maxRegion then --if tile or multi-region rendering

change it to this:

if SMTDSettings.RegionRenderingMode != #none and SMTDSettings.RegionRenderingMode != #maxRegion then --if tile or multi-region rendering
  1. Save the file.
  2. Make sure you restart all copies of 3dsMax as the maxscript files are cached between sessions.

Let us know if this fixes the issue for you?
Mike

6

when i compare those 2 lines of code they seem identical,
am i missing something?

7

node != none :slight_smile:

8

oh… man i looked at that like 20 times and didnt see it.

thanks!

9

This corrected the behavior!

thanks

10

Great. This fix will be included in the next v6.2 beta (7) release.