AWS Thinkbox Discussion Forums

beta 8 feedback

Deprecated Deadline 6 Beta Discussion
#1
  1. In OSX monitor which has become disconnected from the DB, when the user selects and deletes some jobs from the queue, the job are deleted, but this error message appears in console:
2013-10-23 11:44:01:  Error occurred while updating task cache: Array index is out of range. (System.IndexOutOfRangeException)

  1. /plugins/3dsmax/customise.ms - “DeadlineUtil.LogMessage “>Version Information:” - line: #2 is 4 spaces instead of a TAB at the beginning of the line. Although std is all Deadline py scripts are now 4 spaces, scripts such as MXS should be kept as TAB’s, which work better in the native MaxScript Editor?

  2. If I drag and drop a suspended job onto another job, it confirms the dependency I want to create via the pop-up dialog, but it would be nice if it asked if I also wanted to mark the job as pending at this point as well. Instead, at the moment, I then have to RC the job and remember to mark it as pending.

  3. 3dsMax -> Draft Tile Rendering is broken in beta 8.
    (i) I thought we agreed to send the Draft Tile Assembler config txt files to the output directory for each image output sequence? They seem to have gone back to being submitted into the job aux folder.
    (ii) beauty pass works, but RE passes fail to assemble due to incorrect file paths being inserted into the config files at submission time.

See attached 2 x jobs - 1 x Max2013 teapot job + 1 x Draft Tile job. Needs following local file path to exist when you run the job at your end: “C:\MultiRegionRenderTests\PNG”

owenm__3dsmax__MaxJob__5267a96a71bd0c031457f3fe.zip (56 KB)
owenm__DraftTileAssembler__DraftJob__5267a96b71bd0c0a502847ee.zip (19.3 KB)

  1. Trying to archive 2 jobs to demonstrate the above Draft Tile Rendering issue and monitor fails to archive the Max job + pending Draft Tile job as the job names are too long! Error Message:

2013-11-05 15:48:36: Error exporting job 5267a96a71bd0c031457f3fe: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. 2013-11-05 15:48:36: Error exporting job 5267a96b71bd0c0a502847ee: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

This is understandable as an error, but this is going to be an issue going forward for when you want to archive a job automatically or send it to TBS support. I didn’t even create the job name - that was automatic! Perhaps, we need to remove the “job name” from the archive job zip file name?

  1. Should we be adding secondary pool into all areas of Deadline now? - ie:submission script UI’s, ready for v6.1 launch?

  2. monitor boot-up via launcher reports:

2013-11-02 11:13:24: Deadline Monitor 6.1 [v6.1.0.53441 R] 2013-11-02 11:13:24: The current PYTHONHOME environment variable will be modified to avoid potential Python conflicts 2013-11-02 11:13:24: The current PYTHONPATH environment variable will be modified to avoid potential Python conflicts

but boot-up monitor NOT via launcher on OSX and you don’t get the 2 python STDout lines. UPDATE: Re-visited this 2 days later and now either way, the python environment print statements don’t get created in the monitor console! Is this right?

  1. Add Houdini 13, VRay v3, SGO Mamba FX support to Deadline v6.1?

  2. Not sure but I think this was beta 9 (instead of beta 8), but on OSX, specific user account access permissions have been stripped on all directories under the main “DeadlineRepository6” directory on my OSX machine. Only default/std permissions remain. (After installing over the top of an existing beta 7 or 8 repo with the OSX deadline repo installer)

  3. OSX slave is reporting its IPv4 address as one of my vmware vmnet virtual IP addresses instead of either my wireless IP or wired IP address. Should it not be biased towards physical/wireless connections over virtual?

  4. Job reports are now awesomely reporting lots of “slave information”. Excellent. However, there is a difference between the amount of info provided under the “Slave Details” section when you compare a successful job “log” report to an erroring “error” report. Would be good to have all the info in an “error” report also available in a normal, successful, completed “log” report. I know this info should be within the job overall info, but it’s the concept of having all relevant info enclosed within the reporting system for portability and possible log parsing at a later date.

LOG REPORT - Slave Details:

[code]=======================================================
Details

Date: 11/04/2013 12:34:04
Frames: 0-899
Job Submit Date: 10/31/2013 10:30:08
Job User: owenm[/code]

ERROR REPORT - Slave Details:

[code]=======================================================
Details

Date: 11/04/2013 12:42:33
Frames: 0-899
Elapsed Time: 00:00:00:06
Job Submit Date: 10/31/2013 10:30:08
Job User: owenm
Average RAM Usage: 10043423858 (59%)
Peak RAM Usage: 10082996224 (59%)
Average CPU Usage: 16%
Peak CPU Usage: 25%[/code]

  1. “Quick Filters” in monitor - would be nice, if you could RC and collapse/expand the quick filter groups. Similar to the way you can collapse/expand the groups within job properties > plugin settings section.

  2. OSX slave log is empty during normal job processing. Yet job report makes it to the completed log reports in the job. Looks like STDout streaming is broken for OSX slave? – “Open Slave Log…” on local slave whilst rendering results in it just saying…”Connecting to [slaveName]…” - UPDATE: now fixed in beta 9…strange?

  3. mini-map doesn’t remember it’s ON/OFF (ie: is it visible) setting between monitor sessions. In fact, none of the dependency view display options are saved between monitor sessions. Should they be?

  4. 3dsmax submission script on OSX, 2nd tab – “Override Langua” text string cut-off on OSX UI submission form. Needs to be a touch wider :slight_smile:

  5. “Show Slave Info…” button at the bottom of SMTD > “Limits” tab > “Blacklist/Whitelist Slave” is broken. Possible DeadlineCommand.exe change since v6 platform?

  6. I think back in v5.x days, you could select multiple jobs in monitor and when you bring up the job reports, it would show all the reports (log or error or re-queue) for all the selected jobs in 1 big stream. How about re-introducing this functionality, but instead it shows the reports individually in the job reports window? The various columns provide clarity on which slave generated which report and the new filtering system allows customisation of the view if required by user.

  7. job dependency view > “toggle selection mode” icon - seems to not be positioned correctly compared to the other icons to the left of it on OSX monitor? The icon also doesn’t provide enough space before the text to the right of it starts. Feels very bunched up / spacing needs improving. The actual display of the toggle selection icon isn’t very clear when it’s in the depressed mode. You can hardly see the green, surrounding bit.

  8. tooltip for “Show/Hide the minimap”, should be a capital “M” for “Show/Hide the Minimap”?

#2

  1. Logged as a bug.

  2. Fixed internally.

  3. Seems to work properly here. I tested it and it prompted me to mark the job as pending. Can you confirm if this is still a problem for you in beta 9?

  4. I’m pretty sure both (i) and (ii) have been addressed already. I’ll confirm with Grant here, but can you double check if this is the case with beta 9?

  5. We’ll have to do some chopping there. I think the job name is helpful when importing, so I don’t think we wan to remove it entirely. Maybe what we do is have a maximum for each part of the file name.

  6. No plans to do this currently, but that could change if more people want to start using it. So far, it’s only been used by clients that are already writing their own custom submitters. Artists already have enough options to choose from anyways. :slight_smile:

  7. This was addressed in beta 9. Please check to confirm.

  8. Houdini 13 will be supported in beta 10. We don’t have access to vray 3 beta at this point, but initially it should just work. We can add more vray 3 specific stuff in 6.2 as necessary. We can put Mamba FX support on the roadmap for 6.2, since I don’t think there is enough time to add support for it and have it properly tested.

  9. Hmm, we don’t explicitly set any permissions with the Repository installer. Not sure why this would happen…

  10. We currently just pick the first. That’s why there is the option to override it in the slave settings. We’ve considered storing all network interfaces in the slave settings at some point, but nothing on the roadmap at this time.

  11. Yeah, we can add that to the log report.

  12. Hmm, you skipped over 12… :slight_smile:

  13. We can put that on the wishlist.

  14. Weird. Glad it’s working properly in beta 9.

  15. Has already been addressed internally.

  16. This will be fixed in beta 10.

  17. Logged as a bug.

  18. I just checked the v5 source and we never supported this. :slight_smile:

  19. Already addressed internally.

  20. Thanks! We’ll get that fixed.

Cheers,

  • Ryan
#3

Hi Ryan,
Thanks for the notes.

  1. OK, it was me. However, just to clarify: if I drag one job onto another so it becomes dependent - this works, but it doesn’t apply an automatic dependency option such as “resume on complete dependency” which I thought is probably the most often used option…UPDATE: just checked the default behaviour in v5.2 and it’s the same EXCEPT that the “resume on complete dependency” is checked ON for default jobs submitted into the v5.2 queue even if they do NOT have any dependencies applied, which is different from v6.x behaviour…I kind of like the v5.2 behaviour as you only have to drag’n’drop and it works for most cases? - How about the pop-up dialog gives you the dependency checkbox options?

  2. (i) has been done in beta 9. However, beta 9 is still broken for (ii). Essentially, the RE filename hasn’t got the original 3dsmax main render output filename as a prefix. ie: currently it’s giving the RE filenames such as “VRayVelocity_region_bla_bla”, when it should be “test_VRayVelocity_region_bla_bla”, where “test_” is the filename of the main render output. Also, when (ii) fails via Draft Tile Assembly py code, it dumps a “config” txt file EVERY single time it tries to execute, so you end up with multiple copies of the same file in each output directory but with a slightly different timeStamp. I assume fix the first issue and then this other issue won’t happen?! :slight_smile:

  3. Yeah, sounds logical. If poss, please try and give as much of the string info as possible as this will aid in recognising the jobs in the future :slight_smile:

  4. Agreed. Fixed as of beta 9.

  5. My bad. It is actually when you select more than 1 job report for the same job in the job report window. Just checked and this does work in v5.2, but this function no longer works in v6.1 and just leaves the bottom window blank.

Thanks,
Mike

#4

  1. Strange. I checked here, and “Resume On Complete” is set to true by default for all jobs, regardless of if they have dependencies applied or not. I can’t find a single job in our current queue with it set to false, and the new ones I’ve just submitted have it set to true.

  2. I’ll check with Grant about (ii). Thanks for confirming that (i) is working as expected though.

  3. Yeah, we didn’t want to keep this behavior in 6.0 for performance reasons. In 6.0, we only load the report log from the repository when the job is clicked on, so if you clicked on 2000 reports, we would have to load 2000 report files from the repository, and that would just be painfully slow (it was painfully slow loading 2000 reports back in the v5 days).

Cheers,

  • Ryan
#5

Hey Mike,
#4 is in now, it appears that the way that i tried to solve the old problem of not working for render elements failed, so that is now all fixed up

Grant

#6

Cool. Thanks.
I’ll test again in beta 10 :slight_smile:

#7

Hey Grant,
re: issue: #4
Yep, tested my Max Job against your tweaks and all working now. However, can you comment out the “print” command on line: #5760 in functions.ms?
Thanks,
Mike

#8

Yup, we’ll comment out that line. Thanks!

Privacy | Site terms | Cookie preferences