Well I've run into a situation where I'm sure NextDesign's render script will be my lifesaver. However, before I try that, I'd like to know if anyone is familiar with this situation or has ideas I could try.
I have a series of objects that have a texture animated (element in ramp has changing position). Because all the objects are sharing the ramp, there is a custom attribute providing the position for the ramp element via a switch node, and that's actually what is keyed. I've attached a screenshot of the network. So the custom attribute crawlpos is what's keyed. If I hit the render current frame button, everything is peachy. But if I do a batch render, it figures out what the first frame will look like and all the rest are exactly the same, instead of animated.
Any ideas? I can't figure out what the batch render would see differently.
I'm not actually using any file texture, so checking "use image sequence" isn't an option. I did try putting an empty file node into the additional color channel and checking "use image sequence" but that didn't work.
Yeah, it works in a simple setup where I have the ramp position keyed directly. I suspect that mr isn't recognizing that a value is changing, since it's being driven by a switch node. I'll create another simple case where the ramp has a shader switch.
It's interesting, I found this in the docs:
"Animations
When rendering animation files or previewing animations inside Maya, mental ray for Maya exploits incremental changes. This means it determines if scene elements actually have changed between frames and just processes those changes, thus accelerating the render cycle. The check is based on Maya information and includes both geometry (plus instances) and shading nodes. If no changes are detected, the corresponding object or shader is not updated in subsequent frames and appear animated.
Incremental changes are not used if animations are exported as file per frame."
That sounds like this is the case, but I'm rendering out as individual frames, so it shouldn't be using incremental changes.
Okay, I created a simple test with a shading switch, and just keyed the default on that. This test failed, there was no animation rendered out. Weirdly, in this case, the wrong stuff renders in the regular single frame render, even though I can see the correct results in the viewport. I'll upload the file and I'd appreciate it if anyone wants to take a look.