Problem summary
When some non-ASCII fonts are installed, the Text node will crash Nuke when font paths are re-scanned.
If the font is removed/uninstalled, re-scanning fonts will work as expected.
Customer reported version
nuke.10.5v4
Customer reported platform
centos6.8
Steps to reproduce
1) Install your affected font to your OS (Install attached font files)
2) Open Nuke and create a text node
Result: Crash to desktop (sometimes)
4) If no crash, go to 'project settings>font' tab and click 'Rescan font paths'
Result: Crash to desktop
5) Alternatively, open the Script Editor and enter the following command:
nuke.rescanFontFolders()
Result: Crash to desktop
Workaround
- Uninstall the font causing issues within Nuke. Unfortunately there is no way to use the specific font type without the crashes.
-Alternatively, you can work around this by navigating to Edit > Project Settings and opening the Node tab, then unchecking the include system fonts option. This will stop Nuke from scanning for fonts that are installed on your system and should prevent the crashing. However, this will limit the font types you can use in Nuke.
Reproduced by support
This problem has been reproduced on:
Nuke11.1v2 - CentOS 6.9 - MacOSX 10.12 - Windows 7
Nuke 11.0v1 - CentOS 6.9 - MacOSX 10.12 - Windows 7
Nuke 10.5v5 - CentOS 6.9 - MacOSX 10.12 - Windows 7
Nuke 10.5v1 - CentOS 6.9
Nuke 10.0v6 - CentOS 6.9
Nuke 10.0v1 - CentOS 6.9 - MacOSX 10.12 - Windows 7
Nuke 9.0v9 - CentOS 6.9
Nuke 9.0v1 - CentOS 6.9
Nuke 8.0v7 - CentOS 6.9
Nuke 8.0v1 - CentOS 6.9 - MacOSX 10.12 - Windows 7
Earliest version tested
Revised text node did not exist before Nuke 8.0v1
Expected behaviour
No crash when creating a text node when this font is in the font directory
Actual behaviour
Crash when creating a text node when this font is in the font directory