feat(simulation): add deterministic fixed-step execution - #27
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SimulationClockto decouple real frame time from fixed simulation ticksmaxTicks, and configured timestep operate through fixed-step simulation timingSimulationWorldRNGWhy
The simulation previously advanced directly from variable frame delta and used separate hidden random sources. This made behavior dependent on frame timing and prevented reliable reproduction of a simulation run.
This change establishes a deterministic simulation foundation: with the same initial state, seed, fixed timestep, and tick sequence, the simulation follows the same path within the same execution environment.
Validation
std::random_deviceor hiddenthread_localRNG