Fluid Domain (Liquid mode) - changing "Frame Start" setting for sim causes strange Replay errors #79423

New Issue

Libor Batek · 2020-07-31T12:27:02+02:00

Libor Batek commented

2020-07-31 12:27:02 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48

Blender Version
Broken: version: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd749
Worked: (newest version of Blender that worked as expected)

After changing frame start from default frame 1 to something else (later in time) causes Replay cache problems in playback.
It doesnt show correct sim particle data but old one mixing it with the new sim after the new Start Frame.

Exact steps for others to reproduce the error
Create some simple sim using liquid domain and flow objects.
Run simulation for one time to see results (default 1-50frame)
Go to frame 01 and change domain settings for "Frame Start" to let say frame 25
Hit playback...
Replay is not showing accurate results but broken mixed up cache?

Thx!
Libor

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48 **Blender Version** Broken: version: 2.83.3, branch: master, commit date: 2020-07-22 06:01, hash: `353e5bd749` Worked: (newest version of Blender that worked as expected) After changing frame start from default frame 1 to something else (later in time) causes Replay cache problems in playback. It doesnt show correct sim particle data but old one mixing it with the new sim after the new Start Frame. **Exact steps for others to reproduce the error** Create some simple sim using liquid domain and flow objects. Run simulation for one time to see results (default 1-50frame) Go to frame 01 and change domain settings for "Frame Start" to let say frame 25 Hit playback... Replay is not showing accurate results but broken mixed up cache? Thx! Libor

Libor Batek commented

2020-07-31 12:27:02 +02:00

Added subscriber: @LiborBatek

Libor Batek commented

2020-07-31 12:33:01 +02:00

After some thinking, I guess that blender doesnt throw away cached frames after changing sim lenght from frame 1-50 to 25-50 ...the cached frames are still used in 1-25 frame range. They should be thrown away to not use it/display it.

Generally going from longer sim to shorter should clean up cached replay accordingly to not display it when out of range.

L.

After some thinking, I guess that blender doesnt throw away cached frames after changing sim lenght from frame 1-50 to 25-50 ...the cached frames are still used in 1-25 frame range. They should be thrown away to not use it/display it. Generally going from longer sim to shorter should clean up cached replay accordingly to not display it when out of range. L.

Richard Antalik commented

2020-08-02 00:54:44 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-08-02 00:54:44 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Richard Antalik commented

2020-08-02 00:54:44 +02:00

In #79423#988295, @LiborBatek wrote:
After some thinking, I guess that blender doesnt throw away cached frames after changing sim lenght from frame 1-50 to 25-50 ...the cached frames are still used in 1-25 frame range. They should be thrown away to not use it/display it.

There may be other animated elements influencing simulation so cleaning up cache may be necessary, not sure if this is testable with relations currently.

> In #79423#988295, @LiborBatek wrote: > After some thinking, I guess that blender doesnt throw away cached frames after changing sim lenght from frame 1-50 to 25-50 ...the cached frames are still used in 1-25 frame range. They should be thrown away to not use it/display it. There may be other animated elements influencing simulation so cleaning up cache may be necessary, not sure if this is testable with relations currently.

Sebastián Barschkis commented

2020-08-04 11:48:20 +02:00

Added subscriber: @sebbas

Sebastián Barschkis commented

2020-08-04 11:48:20 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Sebastián Barschkis closed this issue

2020-08-04 11:48:20 +02:00

Sebastián Barschkis self-assigned this 2020-08-04 11:48:20 +02:00

Sebastián Barschkis commented

2020-08-04 11:48:20 +02:00

@LiborBatek I hope I understood your issue correctly. In the latest version of master (03c2439d96) the viewport will never show any fluid if the current frame is outside of the cache start / end frame range.
Feel free to reopen if this was not what you had in mind!

@LiborBatek I hope I understood your issue correctly. In the latest version of master (03c2439d96e8) the viewport will never show any fluid if the current frame is outside of the cache start / end frame range. Feel free to reopen if this was not what you had in mind!

Richard Antalik commented

2020-08-05 02:02:18 +02:00

I understood this in a way that if you want to move simulation in time, you just change frame start to later frame, but that will just "not display" simulation.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Fluid Domain (Liquid mode) - changing "Frame Start" setting for sim causes strange Replay errors #79423