search

FLAMEGPU / FLAMEGPU2-visualiser

Cross platform real-time OpenGL visualiser for FLAMEGPU2 models.
1 stars 2 forks source link

Support visualisation rate limiting for `stepsPerSecond < 1` #123

Open ptheywood opened 1 year ago

ptheywood commented 1 year ago

modelcfg.stepsPerSecond is an unsigned integer currently, so it is not possible to have a visualisation with fewer than 1 simulation step per second.

Alternatively, exposing a new method in the FLAMEGPU/vis interface to set step_ms directly as a flaoting point value rather than as 1000/stepsPerSecond might be helpful in some use-cases.

i.e. something like:

ModelVis::setSimulationDelay(float seconds);

These would need to conflict with one another however.

Robadob commented 1 year ago

Better to update current method. I expect the implementation on vis side will need reworking to count multi frame sim steps.

On Mon, 13 Mar 2023, 14:16 Peter Heywood, @.***> wrote:

modelcfg.stepsPerSecond is an unsigned integer currently, so it is not possible to have a visualisation with fewer than 1 simulation step per second.

Alternatively, exposing a new method in the FLAMEGPU/vis interface to set step_ms directly as a flaoting point value rather than as 1000/stepsPerSecond might be helpful in some use-cases.

i.e. something like:

ModelVis::setSimulationDelay(float seconds);

These would need to conflict with one another however.

— Reply to this email directly, view it on GitHub https://github.com/FLAMEGPU/FLAMEGPU2-visualiser/issues/123, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFVGCSKTGUN7BAXECWII3LW34T2VANCNFSM6AAAAAAVZELW54 . You are receiving this because you are subscribed to this thread.Message ID: @.***>