The Pyro simulation in Cinema 4D builds up over time; I'm unaware that anything could be set to a later starting point (precalculated frames - not shown) and placed that one to frame zero.
However, if you cache the simulation and open it in RS Volume, you can offset this Freely. The single (per frame) cache files contain the needed information and do not build up on each other.
If storage space requires it, the frames not included in the renderings can be deleted. I would keep at least the frame before, as I'm unaware how other renders might require this data for motion blur (Just a gut feeling, as I have no 3rd party render engines here running).
RS Volume will recognize the available range, and if the "Detect Frame" is pushed again, it will set the first available cached frame to frame zero. If you need a different starting point, use the provided Offset parameter.
The idea was to provide these dynamic or progressive Voxels to limit the memory needed. The more classic approach is to define a single space that requires a lot of memory from the start.
But, yes, when you go tiny, as mentioned, you quickly have a thousand times more of these cubes, which goes tough on the memory then.
In the old Pyro (two decades ago), there was a 2D version for a more distant objects, I wish we had that also here, even just to comp on the 3D view 🙂
Yes, that is the point. Hence why I gave you a procedure that eliminates all influences that prevent it otherwise.
I have made a feature Request to have this as an option. It should be possible to get from 24fps to 25fps to 30fps, etc., without any concerns about changes.
If the app would work on a simplified idea of Pyro, I could see that easily done.
But my personal impression is that the complexity is working against it.
For example, Gravity results in an acceleration expressed in m/s^2, which means it doesn't have a linear relationship to fps. So what is wanted is an artist call, slow it down, and violate the physics of time or following gravity laws? We can't have both. Not to discuss it here, but to leave this as an example that things are often not as simple as push of a button decision.
Cinema 4D should be easy to operate and art direct, at least to my understanding. So I will also prepare some suggestions toward this. After all Pyro is the first release.
So, since this is a Q&A forum, I have to ask you to either go to the support and communicate this as a problem or go to the "Share Your Idea" option and suggest what you need to have it working for your needs. I certainly will you support with that.
Both options are here: https://www.maxon.net/en/support-center