Problem summary:
GSVs do not de-serialize correctly if they contain backslash characters
If a GSV has a trailing backslash, this will cause all Variables to be deleted
Customer reported version:
Nuke 16.0v1
Customer reported platform:
N/A
Steps to reproduce:
1) Launch Nuke and navigate to Edit > Project Settings
2) Switch to the Variables tab, and create a new Variable
3) Paste \some\string into the Variable's Value:
4) Save and close the file
5) Reopen the file and open the Project Settings, observing how the backslash characters have not been saved:
Alternative steps:
1) Launch Nuke and navigate to Edit > Project Settings
2) Switch to the Variables tab, and create a few different Variables and Variable Sets
3) Paste word\ into one Variable's Value:
4) Save and close the file
5) Reopen the file and open the Project Settings, observing how all the Variables and Variable Sets have been deleted:
Expected behavior:
GSVs containing backslash characters should save without issue.
Actual behavior:
When a GSV contains a backslashes, those character will not be saved correctly. If the backslash is the last character in the Variable Value, all Variables will be deleted when the file is opened next.
Attempting to escape the character with another backslash (\\) does not change the outcome.
Workaround:
No known workaround at this time.
Reproduced by Support in:
Nuke 16.0v1 - Windows 11, macOS 14 Sonoma
Nuke 15.2v1 - Windows 11, macOS 14 Sonoma
Earliest version tested:
Nuke 15.2v1 - This feature (GSVs) did not exist before this version
