You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Exporting a camera as USD does not write the usd attributes "shutter:open" and "shutter:close". However it does seem like something is happening to them as I cannot write them with the json attribute convention either. I can use the json convention to read the attribute and write it out with a different name though. The maya attributes that would be required for these values would be either shutterAngle or aiShutterStart and aiShutterEnd.
Global settings and any modifications to the parameters seem to have no effect
Steps to reproduce
Steps to reproduce the behavior:
Create a camera via Create>Cameras>Camera
Select the camera
Click File>Export Selection ... give it a filepath
use usdview to inspect the camera ... no shutter values written
Expected behavior
1 of 2 things should happen:
Shutter angle (viisble in the special effects section of the camera attributes) should get converted to shutter open and shutter close
aiShutterStart and aiShutterEnd should be written to shutter:open and shutter:close
Attachments
Attached you can find a source maya file as well as a usd file created with it camera_files.zip
Specs (if applicable):
OS & version: Rocky Linux 8
Plug-in version: 0.24.0
Maya version 2023.3
Maya USD commit SHA n/A
Pixar USD commit SHA n/A
Additional context
Apologies if this issue has already been fixed. I do not have the liberty to update freely as I am working in a studio environment. If that is the case, please let me know
The text was updated successfully, but these errors were encountered:
Hi @CarlosPfisterMilk thank you for reporting this. I believe this is something we currently just don't have the support as of yet. I will bring this up to the team for discussion so we can figure out next steps and how this might fit with the plans for the team.
Hi @santosg87
Thank you for the reply and looking into this. If this is considered a feature rather than a bug I would still like to highlight the fact that this usd attribute seems to behave different from other standard camera usd attributes.
A brief explanation of what I meant with this line:
However it does seem like something is happening to them as I cannot write them with the json attribute convention either
Using the json attribute syntax I was able to write and overwrite any attribute (i tested) on the exported camera. I specifically tested attributes that receive information, such as exposure. I also tried exporting similarly name attributes such as "shutterino:open", which worked perfectly fine, however the attributes that I actually need: "shutter:open" and "shutter:close" were not writeable (always comes out as 0) indicating that something is behaving differently than usual.
Shutter values define the motion blur, so I had assumed that something was in play and not working properly as this is one of the few key attributes of cameras and the behaviour is non-standard for this specific attribute.
Describe the bug
Exporting a camera as USD does not write the usd attributes "shutter:open" and "shutter:close". However it does seem like something is happening to them as I cannot write them with the json attribute convention either. I can use the json convention to read the attribute and write it out with a different name though. The maya attributes that would be required for these values would be either shutterAngle or aiShutterStart and aiShutterEnd.
Global settings and any modifications to the parameters seem to have no effect
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
1 of 2 things should happen:
Attachments
Attached you can find a source maya file as well as a usd file created with it
camera_files.zip
Specs (if applicable):
Additional context
Apologies if this issue has already been fixed. I do not have the liberty to update freely as I am working in a studio environment. If that is the case, please let me know
The text was updated successfully, but these errors were encountered: