AWS Thinkbox Discussion Forums

Caching of renderer-specific modifiers

Hi all, since XMesh Saver by default saves the final render-time tri-mesh without the modifiers, how does one work with renderer-specific modifiers like V-Ray’s VRayDisplaceMod? Are these kinds modifiers supposed to be applied after XMesh saving? Is there a way to say, keep the top modifier in the stack while saving and re-apply it to the XMesh Loader? Perhaps via scripting?

In production, we baked the geometry without the VRay displacement mod and added it to the XMesh after the fact.
This is one of the few cases where it needs extra attention because of the way VRay implemented its displacement as a modifier - it goes a bit against the 3ds Max concepts since the effect is calculated inside the renderer. The (pretty awful) 3ds Max displacement from materials is actually supported by XMesh, but nobody should ever use that :wink:

We could look at automating this when saving single objects or when all objects to be saved have the same modifier.
It would get tricky if half of your objects have VRay displacement and each has its own settings but you want them all saved as one XMesh - that would not work.

We are open for ideas how to automate this process, but when I was using XMesh in VFX, we just did it manually.

Privacy | Site terms | Cookie preferences