Description
I've had this issue since 2.4, then 2.4.2, 2.5.2 and now 2.6, on the game Crash Team Racing for PSX. (NTSC-U / J / PAL)
I will include some tasproj i started collecting recently to hopefully provide more material towards fixing this issue.
These kinds of desyncs cant possibly be fixed by messing around with the inputs afterwards, usually lag frames mess up everything, once a desync happens, no matter what i try, its hopeless. Even without lag frames, it seems re-syncronization is still impossible.
DESYNCS tasproj folder: https://mega.nz/folder/i1U1RC7a#5WfxDsNAqhRFMescyxYmXw
I've had 3 different desktops, and ive had the same issues on all of them. Today another taser from this game tried to switch from 2.3.0 to 2.4 but he faced the same issues. This happens in all versions of this game. I actually have no idea if it depends on the game or bizhawk specific psx core, but i suppose so since in 2.3.0 noone of this happens.
Im also guessing that these desyncs tend to happen more in this game, as it doesnt seem plausible that not so much people get PSX desyncs so often.
It happens in random time frames. Can happen in the menu, while playing, loading. It doesnt seem to present any similarities with the exception of being unfixable. I've tried in the past 6 months to analyze even more in depth if some ways of tasing triggered this mechanism, but there was nothing i could find that proved this theory. Also this other taser doesnt even drag inputs like i once did, and he still gets this very annoying issue.
Is the only answer still using 2.3.0? (My only problem with not sticking to 2.3.0 is that its incredibly slow, despite having a decent desktop)
Usually there are no error outputs, at least on the newer versions of bizhawk, but if i manage to replicate on an older version, and getting an error when switching between the sync/desync sections, ill make sure to update it here.
