Project

General

Profile

Actions

Emulator Issues #12998

open

1080 Avalanche - Replays Do Not Sync Between Dolphin and Console

Added by JMC4789 over 1 year ago. Updated about 1 year ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

1080 Avalanche

Game ID? (right click the game in the game list, Properties, Info tab)

GTEE01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

dd2a3befbcb26481ba5edd203e470174

What's the problem? Describe what went wrong.

When playing on BBA with a real console, after about 3 seconds the game decides that an error has occurred and disconnects everyone. I decided to investigate this further and found out this game has a replay system which allows you to save replays onto the memory card. By using that, I was able to record a replay in Dolphin and create something that would be testable on console. When replayed on console, I found that the replay desynced and never finished the race. Even more curious, I tested on the AArch64 JIT with Android... and it also desynced! Interpreter does sync with JIT64, however.

What steps will reproduce the problem?

1: Run a race in 1080 Avalanche
2: At the end, highlight view replay but do not select it.
3: Hit left or right on the joystick to reveal "save replay"
4: Save the replay
5: Watch the replay under the "Replay" option on the main menu on a different architecture (Dolphin AArch64 vs Dolphin x86-64 vs Console)

OR

I've provided replays of each platform to skip most of the steps.

1: Place the replay file you want to test on your memory card
2: Observe it misbehaving/behaving depending on if it matches the platform you chose to run it on.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes - 5.0-17059

Is the issue present in the latest stable version?

Yes

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

NA

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

I've attached replay files that help demonstrate the issue.

What are your PC specifications? (CPU, GPU, Operating System, more)

486 MHz IBM "Gekko" PowerPC CPU, 162 MHz ArtX-designed ATI "Flipper" ASIC, 43 MB total non-unified RAM, no operating system
Pixel 3a Adreno 615, Android 12
AMD 5950x, Geforce GTX 1070, Windows 10

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

One final note is that interpreter does agree with JIT64, though we know that JIT64 is wrong. This means the interpreter also needs repairs. I've verified that each replay worked on the platform I recorded it on as a sanity test. In the replays, I attempt to drive pretty good, but on the AArch64 one, I'm playing on a touchscreen and it gets hairy toward the end. I do make sure to win the race on all 3 recordings.

Note: It seems JIT64 and JIT AArch64 are closer to one another than console, as I accidentally made a replay that at least completed on both JITs, though there may have been some small differences that ended up not mattering due to how easy the first course is. I've only included replays that fail on the other platforms in this issue report.


Files

01-GTEE-replaydolphinx64.gci (40.1 KB) 01-GTEE-replaydolphinx64.gci JMC4789, 07/31/2022 01:11 AM
01-GTEE-console.gci (40.1 KB) 01-GTEE-console.gci JMC4789, 07/31/2022 01:18 AM
01-GTEE-replaydolphinarm.gci (40.1 KB) 01-GTEE-replaydolphinarm.gci JMC4789, 07/31/2022 02:12 AM
Actions #1

Updated by JosJuice over 1 year ago

  • Status changed from New to Accepted
  • Assignee set to JosJuice
Actions #2

Updated by JosJuice over 1 year ago

FALLBACK_IF(round_c) in ps_mulsX makes JitArm64 behave like Jit64, at least in the one replay I'm using. Further narrowing this down could be tricky.

Actions #3

Updated by JosJuice over 1 year ago

The good news: The desync between Jit64 and JitArm64 is solved by https://github.com/dolphin-emu/dolphin/pull/10953.

The bad news: We're back to square one when it comes to figuring out the desync between Dolphin and console.

Actions #4

Updated by JosJuice over 1 year ago

  • Assignee deleted (JosJuice)
Actions #5

Updated by JosJuice about 1 year ago

  • Subject changed from 1080 Avalanche - Replays Do Not Sync Between Dolphin and Console (AArch64 also does not sync with x86-64!) to 1080 Avalanche - Replays Do Not Sync Between Dolphin and Console
Actions

Also available in: Atom PDF