ID 454904 - Exporting a shot with Unicode characters in the Nuke scripts additional nodes area will cause an error and fail

Follow

Problem summary
When exporting a shot from Hiero/Nuke Studio, you can choose to add 'Additional Nodes' to the Nuke script that is generated.


If you enter in a Unicode character within the 'Script' area, when exporting you will get the following error message and not allow you to export the shot.



Customer reported version
hiero.12.1v2

Customer reported platform
10.15

Steps to reproduce

1) Import and drag your footage into the Hiero/Nuke Studio timeline to create a clip within a sequence

2) Right-click the clip, and select 'Export...'

3) With the export preset menu open, ensure you are set to 'Process as Shots' and select 'Basic Nuke Shot'

4) Within the Export Structure area, select 'Nuke Project File' and within this content tab, check the 'Additional Nodes' checkbox and click 'Edit'

5) Once in the Additional Nodes Setup menu, click the '+' to a new condition to the shot, and within the 'Script' field, paste in the below code snippet (that contains a Unicode character)
BackdropNode {
inputs 0
name BackdropNode4
tile_color 0x388e8e00
label "2 × 2 = 4"
note_font_size 42
selected true
bdwidth 328
bdheight 119
}
6) Select 'Export' to export the shot
Result: Unicode error

Expected behaviour
Export process should not error when Unicode characters are added to the Nuke script via the additional nodes area

Actual behaviour
Export process errors when Unicode characters are added to the Nuke script via the additional nodes area

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Hiero 12.2v3 - Windows 10 - MacOS 10.15.3 - CentOS 7
Hiero 12.2v1 - Windows 10
Hiero 12.1v1 - Windows 10
Hiero 12.0v1 - Windows 10
Hiero 11.3v1 - Windows 10
Hiero 11.2v1 - Windows 10
Hiero 11.1v1 - Windows 10
Hiero 11.0v1 - Windows 10
Hiero 10.5v1 - Windows 10
Hiero 10.0v1 - Windows 10
Hiero 9.0v1 - Windows 10 - MacOS 10.15.3 - CentOS 7

Earliest version tested
Hiero 9.0v1
- This issue appears to be in all versions of the product

    We're sorry to hear that

    Please tell us why