After CC suggested seeing how it handles stag cutscenes, I tested it with a split file that had RidingStag as a start-triggering autosplit.
Unlike most other start splits, RidingStag does not actually correspond to a load, so this uncovered an issue with the load remover having "startup time" which affects the timer on the first run to a difference of ~0.9 seconds relative to all other runs after that.
To fix this, any pointers used by the load-remover should be initialized before the timer is running, and not during the first tick after the timer is running.
After CC suggested seeing how it handles stag cutscenes, I tested it with a split file that had
RidingStagas a start-triggering autosplit.Unlike most other start splits,
RidingStagdoes not actually correspond to a load, so this uncovered an issue with the load remover having "startup time" which affects the timer on the first run to a difference of ~0.9 seconds relative to all other runs after that.To fix this, any pointers used by the load-remover should be initialized before the timer is running, and not during the first tick after the timer is running.