Running 2024. Pyro caching is extremely unreliable and also randomly laggy as hell.
This sim runs in the viewport at about 5 fps, yet takes anywhere between a couple of minutes to almost an hour (!) to cache frames. Is there a huge amount of data being cached that is not being processed for the viewport preview? This still wouldnt account for some frames ( see vdb files 198, 210, 215, 221 in the screengrab ) taking 30/40 mins sometimes.
For a sim that is less that 500 frames long, that runs in the viewport at a reasonable pace, this length of time for caching is far from practical. I would be more than happy to discover I am doing something wrong!
Here's the screengrab showing time taken for each frame:
One assumption I am reaching is that the caching system does not use the GPU. Which is ridiculous, surely? I am running this on a 3090 and surely I should expect to see this GPU utilised for the caching process, not just the preview.
Additional - it seems Pyro caches several frames at the same time. If I refresh the explorer window, I can see the file sizes for the last 5 or 6 vdb files increasing with each refresh. Would this again suggest this is being done on the CPU entirely?
Dr. Sassi last edited by Dr. Sassi
If I read the data correctly, each frame has over one GB of data. This means if you expect to have that running in real-time, you would need something that has around 40GB/sec sustained reading speed available.
This is only to access the data; rendering such data is slightly more demanding.
I can't answer your question other than that. Screenshots, as I mentioned often, have very little information in them.
Have you tried the 2024 cache options?
If you have the feeling that something is off, and your setup should have the capacity to wrangle the data, then please get in touch with tech support:
All the best
Hi Dr Sassi, thanks for the reply. I am not actually focusing on whether things run in real time - I dont expect heavy sims to do that. I am just comparing the preview in the viewport, running at 5 fps to when its time to cache the same sim, each frame takes an hour. I have used TurbulenceFD for over 10 years so I am fairly familiar with the sim/caching process, but I have never seen caching of sims take anywhere near this long, or cause this number of crashes. Am I to assume I should not be treating the Pyro system as a reliable one?
Dr. Sassi last edited by
It sounds like an interesting case to study for the support and developers.
Would you mind checking with them, as I have no other answer, and an hour per frame sounds like something support should take a deeper look at.
My best wishes.
Ok will do when I have some downtime - many thanks again, for all your work on here!
Dr. Sassi last edited by
Thanks a lot, ideal-error,
For your patience with this case, and thanks for the kind feedback.
Have a great weekend.