abstractfactory/maya-capture

Capture with Maya 2018?

Opened this issue · 12 comments

Heya,

What is the status of this project?
It seems that capture does not work on Maya 2018? -- same code running fine on maya2016.5

Cheers
Clement

What in particular is not working for you in Maya 2018? We run it in Maya 2018 without issues.

What errors are you getting?

Tagging @aardschok so he can also keep an eye on the conversation.

I'm using capture into the alembic export to get an automatic playblast on camera export.
So to debug to made this basics example:

capture

Again, i double checked in Maya2016.5 and it's working fine.
But as you can see, even this little script is crashing Maya2018 instantly.

Thanks for reporting this @ISkipy. Can you confirm that playblasting with those parameters works via cmds.playblast()?

That would help us rule out any chance of it being an underlying issue that command, which is what capture ultimately calls.

Thanks for the quick answer again.
Just tried that on Maya2018 and everything is fine yes:

import maya.cmds as cmds cmds.lookThru("RenderCam") cmds.playblast(filename=r'C:\Users\clementp\Desktop\test\test\test\test', frame=1001, format="image", compression='png')

Excellent, thank you.

It may be related to the new parallel evaluation mode in Maya 2017+. What happens if turn that off, under Preferences -> Animation (should say either DG or Off)?

The next thing I would try is disabling most or all context managers running on capture, here. I suspect one of them is causing a crash.

Next, try editing the call in there to cmds.playblast to see if excluding any of those options works.

Got the same issue either in Parallel or DG.
Will try the next step now

Removing the context managers didn't change anything.
I also tried to remove some arguments form the cmds.playblast call without success.

Here is what the script looks like for now:
capture

And if you remove the _independent_panel? That is also a context function.
If that works, try to add the contextlib.nested back into it and see how it reacts.

You right, after removing it Maya2018 was not crashing anymore.
Still working after adding contextlib .nested back.
Some of them need the panel variable though.

Current working version:
capture

So what's the next step to have the same capture behavior than on Maya2016.5 then?

Now that we've identifier the cause (great work!) the next step would be finding a suitable alternative (preferably), or (less preferably) limit that particular feature to Maya <2018. From there, a pull-request would be great.