Fixed Timestep Simulation Planner
Plan update interval and estimated simulation CPU load.
Your inputs
Calculation results
Formula & assumptions
CPU time per second = updates × cost; mean updates/frame = updates/frame rate.
Values use the specified units. Calculations use floating-point arithmetic. Check input measurements and formula assumptions before applying the result.
Compare your scenarios
Save up to five results to compare changes side by side. Scenarios stay in this tab until you clear or reload it.
Using Fixed Timestep Simulation Planner
Plan update interval and estimated simulation CPU load.
- Enter updates per second, cost per update, frame rate using the units printed under each field.
- Choose Calculate, or enable live updates. Review the result labels and formula assumptions.
- Save scenarios to compare up to five variations, then copy the report or download JSON or CSV.
Example
Updates per second: 60 updates Cost per update: 2 milliseconds Frame rate: 30 frames per second Update interval · milliseconds: 16.666667 Mean updates per frame: 2 Single-core time used · percent: 12
Questions & answers
What does Fixed Timestep Simulation Planner calculate?
Plan update interval and estimated simulation CPU load.
Which units should I enter?
Updates per second uses updates. Cost per update uses milliseconds. Frame rate uses frames per second. Convert values to these units before calculating.
Which formula does it use?
CPU time per second = updates × cost; mean updates/frame = updates/frame rate.
What does the included example show?
Updates per second: 60 updates; Cost per update: 2 milliseconds; Frame rate: 30 frames per second. Result: Update interval · milliseconds = 16.666667; Mean updates per frame = 2; Single-core time used · percent = 12.
Can I compare different settings?
Yes. Save a scenario, change the inputs and save another result. Up to five scenarios are compared in this tab; they disappear when you reload or leave.
Can I export the calculation?
Copy the JSON report or download JSON and CSV with inputs, result labels and numeric values. Processing uses local JavaScript; no calculation request is sent to our server. Displayed values use up to 10 significant digits; exports retain JavaScript numeric precision.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.
