Problem summary Within Nuke it is possible to open nuke script 'autosave' files into a nuke session as a standard nuke script.
In Nuke 12.1v1 releases and later, it appears that while this process is still possible through the GUI, it is no longer possible through terminal.
Customer reported version nuke.12.1v2
Customer reported platform centos7
Steps to reproduce
1) Open a new Nuke session (12.1v1 or later)
2) Save the Nuke session as 'test.nk'
3) After saving create a Checkerboard node, avoid saving after this.
4) Keep the script open for over 30 seconds (without saving) to force the autosave file to generate.
5) Once generated, close the test.nk script (without saving).
6) Open a terminal window and open the autosave file. An example for Windows would be the following: "C:\Program Files\Nuke12.2v2\Nuke12.2.exe" path\to\test.nk.autosave
Result: autosave nuke script does not load.
Note: Repeating the same steps in the GUI will work correctly, and so will the terminal command in Nuke 12.0v7 and earlier releases.
Expected behaviour You should be able to load the autosave files through terminal in Nuke 12.1v1 and later
Actual behaviour When you open an autosave file within terminal, it will not load in Nuke 12.1v1 or later.
Workaround
From testing it appears the addition of the '-i' (interactive) flag in the terminal resolves the issue.
Based on the example terminal code above, make the following change. "C:\Program Files\Nuke12.2v2\Nuke12.2.exe" -i path\to\test.nk.autosave
Reproduced by support
This bug has been reproduced in: Nuke 12.2v2 - Windows 10, MacOS 10.15.4, CentOS 7 Nuke 12.1v1 - Windows 10
Unable to reproduce bug in: Nuke 12.0v7 - Windows 10, MacOS 10.15.4, CentOS 7
Earliest version tested Nuke 12.0v7 - This issue doesn't appear in this version and has regressed