Thank you Dr Sassi.
I guess my main issue is, you cannot create a pyro simulation at a regular frame rate (e.g. 25fps) and then adjust the frame rate afterwards.
Seemingly the only way to achieve a simulation that replicates one created at 25fps, when the project settings are at 200 fps, is to adjust the temperature of the pyro to the highest it allows.
There is no parity between different frame rates in the simulation. You cannot just change the frame rate and achieve the same look. The frame rate should have no effect on the attributes of the simulation itself, but the frame rate wildly effects the simulation itself.

The simplest example of this i can show, is simply dropping a pyro tag on a standard sphere at 25fps, without changing any settings, leave at default, and run the simulation.
Then adjust the project frame rate to 100fps, and run the simulation again.
The simulation is drastically different, although none of the settings have changed.

Thanks for the response Dr. Sassi,
Unfortunately this has the same effect as setting the frame rate higher, it completely dampens the simulation. It doesnt just make is slower. If you try with a simple sphere and default pyro settings, then adjust the scene time scale down to .25 (1/4 speed), the simulation barely flickers with a flame.
The only way to counter this seems to be to up the fuel and pyro settings to make a more powerful pyro simulation, which is then so powerful and fast, that it negates the speed slow down.

Embergen has a hz setting that just slows down the simulation exactly how it should. I was hoping i wouldnt have to jump over there to create a vdb, as the current pyro object with an octane tag works very well!

Hi there,

I'm trying to create a slow motion Pyro sim.
I have a good setup with a normal frame rate of 25fps.
When i change the projects frame rate to 200fps, the simulation barely exists, there's not much fire or smoke etc.

There is mention in the release notes that there is a "simulation time scale", but i cannot find that setting anywhere.

Any help would be appreciated! or advice on how to slow down the simulation.