Problem summary
Errors are given when loading a Nuke script with relative file paths in Classic 3D nodes.
This has been seen to occur with the following nodes: Camera3, Light3, Axis3, and was not occurring in Camera2, Light2, or Axis2 nodes.
Customer reported version
Nuke 15.1v6
Customer reported platform
Windows 11
Steps to reproduce
1) Create a Camera3 node and add a file path pointing to any USD/ABC/FBX camera file.
2) Open the Project settings by pressing S in the Node Graph.
3) Click the Script Directory knob to add a python project directory.
4) Save the Nuke script to the same location as the camera file, then open the Camera3 Properties bin.
5) Make the file path relative by adding a period to the first portion where the Nuke script and camera files are stored. i.e from C:/Users/username/Desktop/test/camera.abc to ./camera.abc
6) Save the Nuke script again, then close and reload the script observing any errors.
Expected behavior
The nodes should be loaded with all knobs and appear without error.
Actual behavior
The Classic 3D nodes that have relative file paths will error and be missing knob values like the following:
Camera1.scene_graph: no such knobCamera1.{0} version: 1 + /AnimationCamera2_group/AnimationCamera2: no such knobCamera1: could not find knob "scene_graph" againCamera1: could not find knob "frame_rate" again
Workaround
There is no available workaround at this time.
Reproduced by Support in:
Nuke 16.0v1 - Windows 11, macOS 13 Ventura
Nuke 14.0v1 - Windows 11, macOS 13 Ventura
Nuke 13.0v1 - Windows 11, macOS 13 Ventura
Unable to reproduce bug in:
Nuke 12.2v11 - Windows 11 - Camera3 node did not exist.
Earliest version tested
Nuke 12.2v11 - These Classic 3D features did not exist previous to 14.0v1
