🐛 Description
A main thread stall (from any form of Godot lag) can cause the RollbackSyncronizer to go out of history and not work. This is especially problematic when first joining, as lag is expected to happen.
Steps to reproduce
- Download MRP
- Run MRP (2 instances)
- Host with instance 1
- Join the server with instance 2
- Observe the console.
Expected behavior
The RollbackSyncronizer should continue to function despite the slight freeze, or add support for planned lag spikes.
Observed behavior
Rollback does not work for a while, and spams the console.
Versions
- Godot version: 4.5.1-stable
- netfox version: 1.35.3
MRE
mrp.zip
🐛 Description
A main thread stall (from any form of Godot lag) can cause the RollbackSyncronizer to go out of history and not work. This is especially problematic when first joining, as lag is expected to happen.
Steps to reproduce
Expected behavior
The RollbackSyncronizer should continue to function despite the slight freeze, or add support for planned lag spikes.
Observed behavior
Rollback does not work for a while, and spams the console.
Versions
MRE
mrp.zip