Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capture with Maya 2018? #87

Open
ISkipy opened this issue Aug 1, 2018 · 12 comments
Open

Capture with Maya 2018? #87

ISkipy opened this issue Aug 1, 2018 · 12 comments

Comments

@ISkipy
Copy link

ISkipy commented Aug 1, 2018

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

@BigRoy
Copy link
Collaborator

BigRoy commented Aug 1, 2018

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.

@ISkipy
Copy link
Author

ISkipy commented Aug 2, 2018

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.

@mottosso
Copy link
Member

mottosso commented Aug 2, 2018

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.

@ISkipy
Copy link
Author

ISkipy commented Aug 2, 2018

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')

@mottosso
Copy link
Member

mottosso commented Aug 2, 2018

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)?

@mottosso
Copy link
Member

mottosso commented Aug 2, 2018

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.

@ISkipy
Copy link
Author

ISkipy commented Aug 2, 2018

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

@ISkipy
Copy link
Author

ISkipy commented Aug 2, 2018

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

@aardschok
Copy link
Contributor

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.

@ISkipy
Copy link
Author

ISkipy commented Aug 2, 2018

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

@ISkipy
Copy link
Author

ISkipy commented Aug 2, 2018

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

@mottosso
Copy link
Member

mottosso commented Aug 2, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants