Max 2010 64-bit 1.4.9 RC2, oh man I see you just posted RC3 but there was no mention of this AFAICT (as far as I could tell)
I quickly checked the reference for any mention of it but didn’t see anything. So I am counting this as a bug.
It seems it should work I scrub and render a single frame and I get an update render. It is just when I hit render with active segment or range it happens to render the current frame that the timelslider is on for the amount of frames specified.
A real quick simple attached file below, had something using prwapper, so I did a sanity check to make sure… Max2010_KRK-RC2_AniPRTvol.zip (17.8 KB)
When you say “the same problem” do you mean PRT Volume does not respect the animation of the RealFlow loader?
Because it would depend on the validity interval of the source object and getting a notification that something changed.
If the PRT Volume is not getting notified of changes, it can very well be a NextLimit problem and not ours.
Try setting some animation keys on some animatable parameter in the source object (or add a keyframed modifier on top of it) and see if this changes anything.
In general, PRT Volume will only update if Max tells it via its notification system that the dependency object has changed.
I added a barely noticable noise modifier to the top of the mesh loader modifier stack, still no dice. In the mean time, I’ve worked around the problem by just using a script that loops through all the frames, incrementing currentTime and calling the render() function, but a fix or workaround would be great.
What happens when you create a Mesher compound? Does it mesh correctly on every frame?
If it does, what happens if you create a PRT Volume from the Mesher?
If it does not work with the Mesher, it would be time to talk to Next Limit.
