You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 25, 2023. It is now read-only.
Description
Currently, the final time of a marble is calculated by using Date.now() at the race start and at crossing the finish line. Lag(spikes) and/or small accumulated inaccuracies during the physics updates could affect the end result. It's definitely negligible for the vast majority of races, but for accuracy's sake and in case of lag spikes, using a frame counter would keep the timing consistent.
Minimum Acceptance Criteria
Physics should use frame counting in combination with the tickrate to determine the finish time of marbles, where counting starts when the gates are opened.
Physics' onMarbleFinished event should return the finish time of the marble, using the same time format that's currently used.
Description
Currently, the final time of a marble is calculated by using
Date.now()at the race start and at crossing the finish line. Lag(spikes) and/or small accumulated inaccuracies during the physics updates could affect the end result. It's definitely negligible for the vast majority of races, but for accuracy's sake and in case of lag spikes, using a frame counter would keep the timing consistent.Minimum Acceptance Criteria
onMarbleFinishedevent should return the finish time of the marble, using the same time format that's currently used.