Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commodore 64 - desync issue (loading/savestate related?) #3563

Closed
DrD2k9 opened this issue Feb 17, 2023 · 2 comments
Closed

Commodore 64 - desync issue (loading/savestate related?) #3563

DrD2k9 opened this issue Feb 17, 2023 · 2 comments
Labels
Core: C64Hawk Commodore 64 core Heisenbug Bug that can be reproduced, but not consistently Repro: Fixed/added in 2.9 Tool: TAStudio

Comments

@DrD2k9
Copy link

DrD2k9 commented Feb 17, 2023

Summary

I have had a number of instances where TASing using the C64 core results in desyncs after TASing a while and then clearing greenzone. Specifically, I'll load/run a game and begin TASing. Then after clearing greenzone the game will load in differently causing a desync for inputs beyond the loading process. I'm wondering if this has to do with changes in input during loading and/or savestates during loading affecting the Loading process of the games, but I don't know how to describe much beyond this.

I can say that nearly every time I've had this occur, the loading time after clearing the greenzone appearss to be faster, but not always.

I've only ever TASed in BizHawk using TAStudio, so I don't know if anyone donig classic frameadvance TASing would also experience this issue.

In discussing with NYMX, he has also seen this issue.

I probably should have reported this issue before, but wasn't sure exactly how to describe it. I'm not even sure what I have described is enough for the devs to go on.

Repro

I unfortunately don't have a way to definitively reproduce this bug. Soemtimes it happens, sometimes it doesn't.

Output

There are no error codes associated with this bug.

Host env.

-I've had the issue with multiple host computers from different manufacturers (MSI, Dell, HP) with both AMD and Intel processors.
-I've seen this issue over multiple versions of BizHawk. I'm fairly confident I've seen as far back as version 2.0, but I can't remember exactly when I first encountered it to know if I also saw the issue in 1.x.x versions.

@YoshiRulz YoshiRulz added Core: C64Hawk Commodore 64 core Tool: TAStudio Heisenbug Bug that can be reproduced, but not consistently labels Feb 17, 2023
@CasualPokePlayer
Copy link
Member

CasualPokePlayer commented Apr 1, 2023

I fixed some issues with states here: cd4c3cc

It's not perfect, floppy disks are not properly savestated (being any changes to the internal copy are not stated). But this might fix the issues you personally encountered (you don't describe the type of games (rom/tape/disk) you encountered this with so I don't know)

@YoshiRulz YoshiRulz added the Repro: Patch pending Potentially fixed in dev build, see readme for download label Apr 1, 2023
@CasualPokePlayer
Copy link
Member

CasualPokePlayer commented Apr 2, 2023

As of 86b33bd the disk serializing issues should be fixed. I believe that should fix all remaining savestate bugs with C64.

EDIT: Fixed performance issues from the disk stating, I think I'll call this case closed. Reply if you still get a desync.

@YoshiRulz YoshiRulz added Repro: Fixed/added in 2.9 and removed Repro: Patch pending Potentially fixed in dev build, see readme for download labels Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core: C64Hawk Commodore 64 core Heisenbug Bug that can be reproduced, but not consistently Repro: Fixed/added in 2.9 Tool: TAStudio
Projects
None yet
Development

No branches or pull requests

3 participants