Negative timeline causes simulation up to frame 0 on render
#1
I don't know if this is the fault of tyFlow, 3ds Max or V-Ray (doesn't happen with Scanline, though) or maybe to be expected, but if the timeline and simulation starts on a negative frame and there is a modifier above the tyFlow object in the stack, rendering any frame before 0 will cause tyFlow to calculate the simulation up to 0, which shouldn't be necessary at this point in time.

Thankfully, it will no recalculate once the Playback Cache exists, but it's still troublesome.

I first noticed this with Shell (no problems with tyFlows internal options) but attached an example with Noise as that doesn't change the topology.

This will also happen with tyMesher as an intermediate (unless it's set to the first or current simulation frame only, but that's not always a viable workaround).

It doesn't seem to be related to V-Ray's light cache.


Attached Files
.max   tyflow_negative_timeframe.max (Size: 724 KB / Downloads: 4)
  Reply
#2
I can see that VRay is querying frame 0 at a certain point in the frame prep process - this causes tyFlow to update to frame 0. Nothing I can really do to prevent that from what I can tell. If you send the scene to Chaos they might be able to see where in the render pipeline the frame 0 query is happening, and why.
  Reply
#3
Thanks a lot for checking it out, Tyson, I'll let them know.
  Reply


Forum Jump: