Hi,
If you RC a job and execute the QuicktimeSubmission.py job script, the render output’s dialog appears. Then if you select 1 or more outputs and click submit; the Quicktime dialog appears one after another for each render output enabled in the previous dialog. However, once all submitting dialogs are “closed”, the original dialog fails to close if automatically or by clicking on the close button. Clicking on the “X” in the corner will get rid of the dialog. This is an issue on Windows & OSX. Shouldn’t the dialog automatically be closed anyway? Additionally, on OSX, this script changes the input footage field in the QT submission dialog to this:
C:/MultiRegionRenderTests/PNG//test0030.png
note the double path separator between path & filename. Doesn’t do this on Windows.
Also, there use to be other RC job scripts in v5 such as:
Cleanup 3dsmax Alt Frames
Submit Fusion Quicktime Job To Deadline
Submit RVIO Job To Deadline
Strip Gamma From Quicktime
Cleanup Nuke tmp Frames
Is there no demand for these scripts anymore? Could they be re-added into the default install and then users can “disable” them if they don’t want them visible in their setup?
I can’t reproduce the QT submission issue with the double slashes in the path. Do you have any path mapping set up that could cause this behavior?
For the other scripts, there hasn’t been any demand for those, and I don’t recall ever shipping the “Cleanup 3dsmax Alt Frames” and “Cleanup Nuke tmp Frames” scripts (they’re not in our v5 repository installations). Also, the Fusion Quicktime plugin no longer exists, so that’s why there isn’t a submitter for it.
If we get demands for the other two, we’ll do it. 
No path mapping setup / no mapped drives.
See attached archived Max job, which displays the issue on OSX.
See screen-grab for more info.
Ah, the Alt & tmp Frame cleanup scripts must have been custom ones. I can’t remember if it was me or Jon who put these together? I guess leave them out for the time being?
owenm__3dsmax__DraftTileRenderingTest_MultiRegions_SingleFrame (Frame 30 - 30 Regions, 41 Sub-Regions)__5245d85b71bd0c0c24a10070.zip (36.6 KB)
Thanks for the sample scene! I was able to reproduce with it. This bug will be fixed in beta 7.
The Close button bug will also be fixed in beta 7. The problem was that the global CloseDialog function was being defined twice. This bug was also preventing the initial dialog from auto-closing.
Cheers,
