- Not 100% related to Rez, how can I view the log messages of the Deadline code?
In SubmitNukeToDeadline.py you should be fine with regular Python print statements.
- Since I cannot see
self.LogWarningmessages, when an exception of some Deadline code happens I’m not aware of it.
Exceptions should still be bubbling up, if it’s from the submitter the error should be in the Nuke console, and if it’s in the render job it should be in a task report, or in the Worker log.
- I found an error in the
event/Rez/Rez.pyfile. . .
This is fixed in Deadline 10.3! 
- After fixing the bug described above, I found the exact same bug that was described in this other thread.
That should be fixed, the thing I wasn’t sure of in that thread was if both the client and repository were running 10.3. The fix is both in the event plugin code and the code baked into our Worker that fetches executable paths. So a 10.3 Repository with a 10.2 Worker would still exhibit the issue.
- If I set
Global Enabledin the State of the Rez event plugin, how can I use the submitters included with Deadline Monitor? Should I “Rezify” Deadline itself and run Deadline Monitor from this package to have Deadline Monitor running in a Rez environment?
Yep! That way when Rez.py checks for a set environment it’ll be able to populate the job’s extrainfo settings with tool info.
- Related to the previous question, what is the best approach to using Rez to manage Deadline customizations?
I don’t know Rez well enough to suggest a best approach, but I don’t know if Rez would be the right application. As I understand it (please correct me!) Rez is going to be best at starting applications and setting environments. For a CustomSanityCheck.py that’ll be pulled in by the submitter on load, and it’ll just pull in whatever file is in place.
For Nuke that’ll be whatever is in the [Repository]\submission\Nuke\Main folder, and there isn’t a way to override where to pull submitter scripts from an environment variable like there is on jobs for plugin files.