State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:138430|
Problem summary:
An export can fail when non-ascii characters are in the file path while rendering in Nuke Studio/Hiero.
This has been shown to occur predominantly within the use of non-English language versions of Windows. (For example Japanese or Russian)
Update: Microsoft has released a fix in Windows 10 that resolves the issue, Unfortunately, the issue still occurs in Windows 7 and 8.
Customer reported version:
Nuke11.2.v5
Customer reported platform:
Windows 10
Steps to reproduce:
1) From Nuke Studio/Hiero, create a script using non-ascii characters.
2) Export the script and observe the output for any errors.
Workaround:
As the issue is generally associated to the Windows language version and its interpretation of the uni-code, it is possible to change the interpretation of the uni-code within Windows.
To do this follow the below steps.
For Windows 10:
Click Additional date, time, & regional settings under the heading Related settings in the top right of the window
Click on Region
Select the Administrative tab
Within the field that says Current language for non-Unicode programs, ensure that it says English (United States).
Within the field that says Current language for non-Unicode programs, ensure that it says English (United States).
Reproduced by Support in:
Earliest version tested:
10.5v8 - This issue no longer occurs and has regressed.
Expected behavior:
The export should render all available files without giving an error.
Actual behavior:
The export fails with an error: "RuntimeError: 'ascii' codec can't decode byte 0xcf in position 11: ordinal not in range(128)"
We're sorry to hear that
Please tell us why