ID 562535 - Not all Camera4 knob values are exported correctly from Nuke

Follow

Problem summary:
Not all Camera4 knob values are exported correctly from Nuke
 
Customer reported version:
Nuke 15.0v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke and create a Camera4 node in the Node Graph.
2) In the Camera's Properties, switch to the Projection tab and set values on all the knobs:


3) Create a GeoScene node (optional).
4) Add a GeoExport node, and export the Camera to an ABC or USD file.
5) Create a new Camera4 node, and load the exported Camera file.
6) Compare the values in the Projection tab against the original values from step 2, noticing how only the Focal Length, Horizontal Aperture, Vertical Aperture, and Fstop match:

 
Expected behavior:
Camera knobs in Nuke should be exported and imported without alteration. 
 
Actual behavior:
After exporting a Camera4 node from Nuke and re-importing it, the Camera's near, far, win_translate, win_scale, winroll, focal_point, shutter, and shutteroffset knobs will either be not preserved or set to an incorrect value.
 
When repeating this process with the Classic 3D System Camera node (Camera3), almost all the knobs align with their original counterparts:

 
Workaround:
No known workaround at this time
 
Reproduced by Support in:
Nuke 15.0v2 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10
Nuke 14.0v1 - Windows 10
 
Earliest version tested:
Nuke 14.0v1 - This feature (Camera4 node) did not exist before this version

    We're sorry to hear that

    Please tell us why