State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:351968|
Problem summary
str(nuke.root().frameRange()) fails to return a custom root frame range.
Customer reported version
nuke.11.1v2
Customer reported platform
centos7
Steps to reproduce
1) In a new Nuke script, open the Project Settings ('S' key when the cursor is over the Node Graph).
2) Change the root frame range to any custom length.
3) Open the Script Editor by right-clicking on any pane > Windows > Script Editor.
4) Select the Viewer node. Enter and run the following command: str(nuke.root().frameRange())
Regardless of the values you set for the root frame range, this command will always return:# Result: '1-100'
Workaround
You get the correct root frame range if you access the Viewer knob directly using the following command:nuke.root()['last_frame'].value()
Reproduced by support
This bug has been reproduced in:
Windows 10
11.1v3
11.1v1
11.0v4
11.0v1
10.5v7
10.5v1
10.0v6
10.0v1
9.0v9
9.0v1
8.0v6
7.0v10
macOS 10.13
11.1v3
7.0v10
Earliest version tested
7.0v10 - This issue appears to be in all versions of the product
Expected behaviour
The str(nuke.root().frameRange()) should return the values set in the frame range setting of the Project Settings.
Actual behaviour
The str(nuke.root().frameRange()) returns the frame range '1 - 100' regardless of the actual root frame range.
We're sorry to hear that
Please tell us why