01-09-2018, 06:33 PM
That make a lot sense. It accounts for how the frame rate "slowly" dies now.
I changed the solver to Simulation Order: Late Update, Disabled V-Sync and set my TimeManager as follows.
![[Image: WMgv6RZ.png]](https://i.imgur.com/WMgv6RZ.png)
With the new setting I believe I'm still seeing the death spiral, albeit much better than the death cliff I saw before.
![[Image: s1mcskD.png]](https://i.imgur.com/s1mcskD.png)
Experimenting with smaller values of Maximum Allowed Timestep does seem to help but not as much I had hoped. At .02, the lowest value it seems to allow I was able to achieve my highest stable frame rate, ~25 frames/sec. Obviously, the fluid behaves very oddly.
![[Image: 44N9RTv.png]](https://i.imgur.com/44N9RTv.png)
A reasonable max step of .1 manages about 15 frames/sec. Is it abnormal to have to change the Fluid Viscosity demo scene to late update to achieve a reasonable frame rate? it seems likely it would have already been set that way if it were actually necessary.
I changed the solver to Simulation Order: Late Update, Disabled V-Sync and set my TimeManager as follows.
With the new setting I believe I'm still seeing the death spiral, albeit much better than the death cliff I saw before.
Experimenting with smaller values of Maximum Allowed Timestep does seem to help but not as much I had hoped. At .02, the lowest value it seems to allow I was able to achieve my highest stable frame rate, ~25 frames/sec. Obviously, the fluid behaves very oddly.
A reasonable max step of .1 manages about 15 frames/sec. Is it abnormal to have to change the Fluid Viscosity demo scene to late update to achieve a reasonable frame rate? it seems likely it would have already been set that way if it were actually necessary.