-
Notifications
You must be signed in to change notification settings - Fork 129
Maya: Fix extract review and thumbnail for Maya 2020 #4744
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didnt get a failed extraction in develop
but got the error message.
With this PR I can still publish successfully, but getting this error message instead;
Instance:
reviewMain
Message:
Cannot apply options Invalid flag 'gpuCacheDisplayFilter'
Plugin:
pyblish.ExtractPlayblast
Path:
C:\Users\tokejepsen\OpenPype\openpype\vendor\python\common\capture.py
Line:
756
Level:
ERROR
Thread:
MainThread
Millis:
59.0000152588
@tokejepsen Just wondering - did you have the I'm pretty sure the issue is there. I feel this is rather a design issue with I feel we should patch up The other way would be to capture any errors on flags passed to the I'll refactor it within a day to patch this up. I'll however need to move the |
Yeah, the plugin was disabled. Enabling it and we get no errors :) |
This way we can pass e.g. `gpuCacheDisplayFilter` value preset setting for a plug-in even when it might not exist as an argument.
…nPype into maya_2020_fix_capture
Try again @tokejepsen I've tested here in Maya 2020 + 2023 with gpuCache enabled and disabled, etc. and now it seems fine. This change in settings now also allows to customize and add other plug-in display filters on might have. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works well in Maya 2023 and 2020.
Changelog Description
Fix playblasting in Maya 2020 with override viewport options enabled. Fixes #4730.
Additional info
More info see issue #4730
I chose to adjust vendorized
capture.py
instead of editing both of maya's ExtractPlayblast and ExtractThumbnail plug-ins because I noticed it was already changed locally from the actual upstream capture.py - the Py3/2 compatibility was added differently upstream in the original capture.py repository. By doing this it also resolves issues with other usages of capture that maybe a studio had implemented.Testing notes:
Both should work fine.