04-16-2019, 04:06 PM
If you're noticing problems like this, please send the file to support@tyflow.com. There could be a variety of things causing the recalculations. One thing you can do on your side is enable "print sim reset info" in the debugging panel of your tyFlow. Then watch the maxscript listener to see if/when it prints out which reference node is causing it to reset and recalc.
Also if you don't have caching enabled, rendering with moblur will cause a reset because max will query past frames for the moblur interval. So for example, if you render frame 100, the renderer may ask for frame 99.5 and 100.5 to calc the motion blur interval....but since tyFlow is history dependent, if you have caching disabled it will have to recompute the entire sim to query the previous frame.
Also if you don't have caching enabled, rendering with moblur will cause a reset because max will query past frames for the moblur interval. So for example, if you render frame 100, the renderer may ask for frame 99.5 and 100.5 to calc the motion blur interval....but since tyFlow is history dependent, if you have caching disabled it will have to recompute the entire sim to query the previous frame.