There is a UX issue regarding the use of MaterialX on Samba network shares. When selecting .mtlx paths in the exporter dialog or MaterialX operator node, it requires that the path separator character be a backslash rather than a forward slash. However, forward slashes are used by default when using the file browser dialog. When using forward slashes, the exporter will correctly export the first look, but will overwrite the file rather than appending additional looks on subsequent writes to the file. In the operator, upon starting the render, it will log to the script editor something of the following nature:
`Error: [materialx] aiMaterialx: file missing when loading "//server/path/to/looks.mtlx": Failed to open file for reading: server\path\to\looks.mtlx`
This behavior is not observed when working with local file paths, so forward slash-separated paths would still work correctly on the C drive. With awareness of this issue the tool is still usable, but hopefully this UX can be solved in future updates.
Hi Tim
We've got a ticket for this. Thanks for reporting the issue.