As title, the removal of PredictedGhostSpawnRequest seems cause misspredictions as it does a structural change. I can see these issues when doing predicted spawn, where after comes partial ticks from the latest prediction state. This solves itself next time you do a full rollback, but it creates frame glitches for the misspredicted part. Still trying to figure out the details why this would happen. Are there any other known components in netcode that cause structural changes on either client or server side that one should be aware of?
Backups are tracked by chunk, which means that if a structural change happens, the chunk is different. We have a fix incoming for this in 1.3 that should allow tracking old chunks and still be able to rollback properly.
1 Like
Any ETA on 1.3? Considering making PredictedGhostSpawnRequest enableable or forcing rollback on structural chunk change + missing prediction history entry for now.
We’re talking days (or sooner) if everything goes well 
1 Like
1 Like