Turn off strict error checking globally for Maya jobs?

Deadline
1

Hi all,

I have a problem whereby I have to turn off strict error checking manually for Maya submissions. I am aware that there is a check box in the submitter but for some reason deadline is ignoring the state of that check box and it makes no difference. I was wondering if there is a way to turn it off globally, since I can see any good reason to have it active at all.

Thanks, Tom

(and if there is a good reason please let me know)

edit

Would an event plugin be able to do this automatically?

2

It sounds like the error we’re catching on is considered a bad thing. “Strict error checking” is for some of the lighter issues.

Can you post the error you don’t want to catch on and I can show you where to add the #hashmark to stop it from catching? Knowing your exact Deadline version is going to help too.

3

The error we are getting is as follows

Error: Strict error checking on, caught the following error or warning.
*** Fatal Error: Failed creating shelf directory: /Volumes/projects/…/…/data/maya/shelves
If this error message is unavoidable but not fatal, please email support@thinkboxsoftware.com with the error message, and disable the Maya job setting Strict Error Checking.
at Deadline.Plugins.PluginWrapper.RenderTasks (System.String taskId, System.Int32 startFrame, System.Int32 endFrame, System.String& outMessage, FranticX.Processes.ManagedProcess+AbortLevel& abortLevel) [0x002c8] in :0

We are currently running deadline Client version: 10.0.14.1

Thanks,
Tom

4

So,

I have a workaround. The folder in question doesn’t exist (clearly because it says so)… So I created it manually and problem solved. However, for future reference, which file in the plugins directory requires comments for errors? Mayabatch.py?

Tom

5

Yeah, it’ll be MayaBatch.py. I think a shelf creation warning at render time should absolutely be non-fatal. Nobody is going to be able to see the shelves anyway!

Looking into it, that “Fatal Error” seems to be on Maya’s end, so the way we can quiet that would be to paste this into “MayaBatch.py” just after the line “#FumeFX STDout Handlers”:

        self.AddStdoutHandlerCallback( ".*Fatal Error: Failed creating shelf directory.*" ).HandleCallback += self.HandlePointCloudOutput

it should end up looking like this:

        self.AddStdoutHandlerCallback( ".*Fatal Error: Failed creating shelf directory.*" ).HandleCallback += self.HandlePointCloudOutput

        # FumeFX STDout Handlers (requires min. FumeFX v3.5.3)
        self.AddStdoutHandlerCallback( ".*FumeFX: Starting simulation \(([-]?[0-9]+) - ([-]?[0-9]+)\).*" ).HandleCallback += self.HandleFumeFXProgress # 0: STDOUT: "FumeFX: Starting simulation (-20 - 40)."
        self.AddStdoutHandlerCallback( ".*FumeFX: Frame: ([-]?[0-9]+)" ).HandleCallback += self.HandleFumeFXProgress # 0: STDOUT: "FumeFX: Frame: -15"
        self.AddStdoutHandlerCallback( ".*FumeFX: Memory used: ([0-9]+[a-zA-Z]*)" ).HandleCallback += self.HandleFumeFXProgress # 0: STDOUT: "FumeFX: Memory used: 86Mb"
        self.AddStdoutHandlerCallback( ".*FumeFX: Frame Time: ([0-9]+:[0-9]+\.[0-9]+)" ).HandleCallback += self.HandleFumeFXProgress # 0: STDOUT: "FumeFX: Frame Time: 00:01.69"
        self.AddStdoutHandlerCallback( ".*FumeFX: Estimated Time: ([0-9]+:[0-9]+:[0-9]+)" ).HandleCallback += self.HandleFumeFXProgress # 0: STDOUT: "FumeFX: Estimated Time: 00:00:18"

This is piggy backing off the HandlePointCloudOutput() function which just suppresses that line of output and should be safe.

If that works, I’ll throw that in a developer issue here and it’ll help for other folks as well.