Does Deadline 10 uninitialize Maya before shutting it down?

Deadline
1

This is a bit of an odd question, it’s not quite a bug, but I’ve hit a slightly annoying issue and I’m curious if it’s something that is fixed in Deadline 10. My manager is pushing IT to finally upgrade from 9 to 10, so this could be all the more reason for them to do so sooner.

In short, I’m attempting to track certain events, and have registered a kMayaExiting callback to determine when Maya closes. If in batch mode, this callback will only trigger if maya.standalone.uninitialize() is used correctly shut Maya down.

I’ve fixed our local code, but I’ve noticed our version of Deadline simply quits the process without doing anything else (I’ve pasted the function below).
Is this something that has been changed at all in the years since our old version was installed?

def EndJob( self ):
    self.LogInfo( "Ending Maya Job" )
    self.FlushMonitoredManagedProcessStdoutNoHandling( self.ProcessName )
    self.LogInfo( "Waiting for Maya to shut down" )
    self.ShutdownMonitoredManagedProcess( self.ProcessName )
    self.LogInfo( "Maya has shut down" )
2

The Deadline 10 integration code looks identical to what you posted.
If you feel we should be calling maya.standalone.uninitialize(), I can make a ticket for the product team to look into adding it. In the past 17+ years, nobody seems to have cared enough to request it :slight_smile:

3

Haha, I’m really not surprised to be honest. I guess for the “feature completeness” of Deadline it could be worth making a low priority ticket, if it’d only take someone like 15 minutes to implement.

I’ll live with filtering out all batch sessions in my script for the time being :slight_smile: