The Texture Manager has one simple role: convert images to RenderMan's texture format, using txmake. It handles single images as well as texture atlases (UDIM, Mudbox, ZBrush).
When you open a new scene, the Texture Manager will find all images used as textures and add them to a queue to convert them. The conversion settings will be based on a set of rules defined in a json file (see below).
Just press Parse Scene whenever you want new textures to be converted. Pick Image and Pick Directory allow you to pre-convert images without having to know how to use txmake.
Stop / Start the conversion queue
By default, the conversion queue is always running, but sometimes you may want to stop the conversion process.
The conversion queue can be stopped and restarted by clicking on the icon on the right of the progress bar. When the queue is stopped, the running txmake processes are immediately killed but existing textures are intact. When you restart, it pick up where it left.
There is a disk usage and progress indicator at the bottom of the Texture Manager window.
Each file in the list also has a status icon.
Interactive versus Batch rendering
- During interactive renders, the texture manager will add new textures to the queue and return a temporary texture until the conversion is done. Once done, it will send an update to the renderer and your texture will appear.
- When you start a Batch or a Preview render, you need all your textures to be converted first. Starting with 22.3, RfM will stop the conversion queue and add any remaining conversion task to the LocalQueue or Tractor job to ensure you always get the expected image.
Number of processes: How many txmake processes will be launched at the same time. The default is 2 but it is often beneficial to add more processes to speed up the queue.
Fallback Texture Path: By default, the texture manager saves the texture next to the source image. If, for any reason, it is impossible to save in that directory, the fallback texture path will be used.
Always Fallback: Always save converted textures in the fallback texture directory.
Show Advanced Options: Show more advanced options in the user interface.
Texture extensions: All texture file extensions so the texture manage knows which files can be marked as already converted.
The texture manager uses a set of rules to choose optimal txmake parameters based on:
- The type of node using the texture:
- A set of base parameters for that type of node
- one or more rules to modify the base parameters when considering the file's name, the bit depth, etc.
Custom settings can be defined by the ocio configuration.
The default rules are build for efficiency and you shouldn't have to modify them unless you have specific pipeline requirements