-
Notifications
You must be signed in to change notification settings - Fork 202
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
Don't write fStop when depthOfField is disabled. #1280
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.
Thanks for the fix. I would have expected that at least one of the exported cameras in the unit tests would have a disabled depth of field on export to test that the USD stream ends up having the right values, and it would be nice to have an import test with an fStop of zero to exercise the new behavior fully.
ef424ed
to
c2b80c0
Compare
c2b80c0
to
65930f5
Compare
Added the test.. |
@marsupial please apply clang-format so we can trigger PF for this change. |
65930f5
to
0f40aa9
Compare
The two failing MacOS are known issues unrelated to this change. This change is now ready for merge. |
Maya has an explicit attribute to enable/disable depth of field, but fStop=0 does that in USD.
Currently USD import/export is a direct translation of the USD fStop attribute, which changes intent/meaning.
TODO: Might be good to export the maya fStop curve in a namespaced custom property for loseless data Maya->USD->Maya.