Skip to content

fix: support desync detection with sparse saves#115

Merged
gschup merged 2 commits into
mainfrom
fix-desync-sparse-saving
Jun 17, 2026
Merged

fix: support desync detection with sparse saves#115
gschup merged 2 commits into
mainfrom
fix-desync-sparse-saving

Conversation

@gschup

@gschup gschup commented Jun 17, 2026

Copy link
Copy Markdown
Owner

fixes #107

@loganmc10

Copy link
Copy Markdown

It is tough to say, something in the recent batch of commits makes the emulator freeze, so when I build from this branch, it also freezes. I'll try to bisect which commit started the problem.

@gschup

gschup commented Jun 17, 2026

Copy link
Copy Markdown
Owner Author

My bad, as per usual I tried doing many things at once :D

@loganmc10

Copy link
Copy Markdown

No worries, I release broken things all the time, this isn't even released.

The issue starts for me with this change: #109

I see this in the logs over and over:

[2026-06-17T13:13:52Z WARN  ggrs::network::protocol] Discarding input packet starting at frame 2; expected at most 0
[2026-06-17T13:13:52Z WARN  ggrs::network::protocol] Discarding input packet starting at frame 2; expected at most 0
[2026-06-17T13:13:52Z WARN  ggrs::network::protocol] Discarding input packet starting at frame 2; expected at most 0
[2026-06-17T13:13:52Z WARN  ggrs::network::protocol] Discarding input packet starting at frame 2; expected at most 0

@loganmc10

Copy link
Copy Markdown

I believe it is probably related to the input delay, which was set to 2 in this case

@gschup gschup force-pushed the fix-desync-sparse-saving branch from 290d964 to a493778 Compare June 17, 2026 14:04
@gschup

gschup commented Jun 17, 2026

Copy link
Copy Markdown
Owner Author

I tried a new LLM-based coding tool. Due to the new UI I missed a bug that was introduced. Whelp, it should be fixed now. Both on main and this PR.

gschup and others added 2 commits June 17, 2026 16:23
Regression test for the input_delay > 0 freeze: verifies that a first
packet with start_frame=2 (as sent by a peer with input_delay=2) is
accepted and decoded using the NULL_FRAME sentinel as reference.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@gschup gschup force-pushed the fix-desync-sparse-saving branch from a493778 to 4faf71f Compare June 17, 2026 14:26
@loganmc10

Copy link
Copy Markdown

yes, seems all good now, thanks!

@gschup gschup merged commit 6cbcbbf into main Jun 17, 2026
2 checks passed
@gschup gschup deleted the fix-desync-sparse-saving branch June 17, 2026 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incompatibility between desync detection and sparse saving

2 participants