Problem summary When saving a comp as a new version, if the Nuke script is within a folder path containing non-ASCII characters, Nuke throws the following exception:
The path above should be named "/Nuke_Projects/¡¡¡¡¡¡¡/test.v002.nk"
The script is not versioned up.
This issue only occurs on Windows operating systems
Customer reported version nuke.11.1v2
Customer reported platform n_a_windows
Steps to reproduce
1) Open Nuke
2) Create a Checkerboard
3) Save the Nuke script to a directory containing non-ASCII characters, e.g: "/path/to/¡¡¡¡¡¡¡/test.v001.nk"
4) Make some changes in the script
5) Use file -> Save new comp version to version up the script.
Result: Nuke fails saving the project, throws an error prompt similar to the one above
Expected behaviour Nuke version ups the script.
Actual behaviour Nuke fails to version up the script, an error prompt is thrown.
Workaround Remove any non-ASCII characters from file directories to avoid the issue occurring.
Reproduced by support
This bug has been reproduced in: Nuke11.3v3- Windows 7 - Mac10.14 - CentOS7 Nuke11.3v1- Windows 7 Nuke11.2v1 - Windows 7 Nuke11.1v1 - Windows 7 Nuke11.0v1 - Windows 7 Nuke10.5v1 - Windows 7 Nuke10.0v1 - Windows 7 Nuke9.0v1 - Windows 7 Nuke8.0v1 - Windows 7
Unable to reproduce bug in: Nuke11.3v3 - Mac10.14 - CentOS7
Earliest version tested - This issue appears to be in all versions of the product
