...
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.
...
These settings are defined in a $RMANTREE/etc/txmanager_rules.json.
| Info |
|---|
The default rules are build for efficiency and you shouldn't have to modify them unless you have specific pipeline requirements |
JSON structure
Here is a very basic example. See $RMANTREE/etc/txmanager_rules.json for the real rules.
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"pattern": {
"args": {
"texture_type": "regular",
"smode": "periodic",
"tmode": "periodic",
"texture_format": "pixar",
"texture_filter": "catmull-rom",
"resize": "up-",
"data_type": null,
"compression": "lossless",
"compression_level": null
},
"rules": {
"'_i8t' in '%(img_name)s'": {
"args": {
"texture_format": "tiff",
"data_type": "byte"
}
}
}
}
} |
Category
HereIn the example above, the category is pattern, but there are other pre-defined categories: light, lightfilter and imageplane.
args
This section is a dictionary representing default txmake parameter values for the current category. The key names (texture_type, smode, tmode, etc) are coming from the TxParams class of the txmanager python module.
...
... matches "_i8t" in the image name, which is here interpreted as shorthand for "8 bits integer tiff format" and sets the texture format to "tiff" and the image to "byte" (8 bits integer, see txmake documentation). For example, a file named "roof_top_diffColor_i8t_v01v06.png" would match that rule.
...