By cgbeige
#338777
I wanted to try Maxwell for this project but then once I started, it was clear I wasn't able to. Texture caches don't update with proper UVs and the FIRE display had a different crop than actual renders. But the texture cache thing I know isn't new, so this something that can be fixed? It's a bit of a showstopper and I'm sure there are technical reasons that make it difficult but V-Ray seems to do it fine with these TIFF files.
User avatar
By Mihnea Balta
#338803
The viewport representation of Maxwell materials doesn't update when you edit UVs, is this what you mean by texture cache? This is caused by a limitation in the Maya API, but you can overcome that by telling it to display only the texture you're interested in, not the entire material. You can either click "Enable viewport override" in the Maxwell rollup of the file node, or select it from the "Viewport Override Texture" dropdown in the Global Parameters section of the material.

There used to be a problem with FIRE not taking overscan into account, which caused it to have different framing that the production render, but that was fixed 3 versions ago. If you're still having problems with this, please post an example so I can investigate it.
Maxwell Rhino 5.2.6.8 plugin with macOS Tahoe 26

Grazie Ferdinando, prima di aggiornare il Tahoe 26[…]

So, is this a known issue?