As a result, the list of system fonts available in Nuke may be different to that available in other software applications on the same machine. Note:Only fonts that are physically stored in a file are available in the font controls. See Third-Party Libraries and Fonts for a list of fonts that ship with Nuke. If you disable Project Settings > Font > include system fonts, only the fonts that ship with Nuke are available in the font controls. To avoid this, Nuke ships with several fonts common to all platforms. In general, there is no guarantee that a font family and style, such as, will render identically cross-platform. Note:If several locations contain the same font, Nuke uses the font from the first directory it finds it in. For example, on Windows C:\Windows\Fonts\. The system fonts folder, assuming that Project Settings > Font > include system fonts is enabled. On Windows, for example, you could specify "c:\windows\font1 c:\windows\font2. Note:Locations 1 and 3 allow you to specify multiple paths using the OS standard syntax. The location specified by the NUKE_FONT_PATH environment variable. nuke/fonts directory and all other plug-in folders. The location specified in the Project Settings > Font > project font path control. Nuke retrieves the fonts available in the Text node from various locations in a set order, before caching them: 1. Note:The font cache file is not used when rendering and is not required on a render farm. Note:See Environment Variables for more information on setting environment variables. See Updating the Font Cache for more information. The font cache XML file is called fontmapping.fcache and its location is specified by the environment variable NUKE_TEMP_DIR. In order to display the available fonts faster in the font dropdown menu, these fonts are cached as an XML file when you open a Text node's properties panel.
The FreeType library used by the Text node supports a large number of fonts, including TrueType, OpenType, and PostScript fonts.
0 kommentar(er)
