Project

General

Profile

Actions

Emulator Issues #12970

closed

GameCube Service Disc-Optical Disc Drive

Added by ZephyrSurfer almost 2 years ago. Updated over 1 year ago.

Status:
Fixed
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:
5.0-17116

Description

Game Name?

US GameCube Service Disc

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

301E01

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

536dba21b557c8d8cd8292534cfaa260

What's the problem? Describe what went wrong.

The Optical Disc Drive test results in Dolphin failing the second of two tests. It outputs the following error at it's end: "TEST FAILED" and "direg2.dol Code:5000000".

What steps will reproduce the problem?

Run the "Optical Disc Drive Test"

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-16831

Is the issue present in the latest stable version?

No, 5.0

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.)

5.0-11476 -> https://dolphin-emu.org/download/dev/966e1b31ba42f836df2f2c8fff98687267912885/

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

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

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

i7-8750H
GTX 1060
Windows 10
8GB DDR4

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

[Anything else here]


Files

working_5.0-11458.png (131 KB) working_5.0-11458.png Working in 5.0-11458 ZephyrSurfer, 07/09/2022 12:11 AM
broken_5.0-11476.png (138 KB) broken_5.0-11476.png Broken in 5.0-11476 ZephyrSurfer, 07/09/2022 12:11 AM
optical_disc_drive_test_log_5.0-11458.txt (36.3 KB) optical_disc_drive_test_log_5.0-11458.txt Working Log (5.0-11458) ZephyrSurfer, 07/09/2022 12:25 AM
optical_disc_drive_test_log_5.0-11476.txt (36.3 KB) optical_disc_drive_test_log_5.0-11476.txt Broken Log (5.0-11476) ZephyrSurfer, 07/09/2022 12:25 AM
optical_disc_drive_test_log_5.0-12426.txt (36.3 KB) optical_disc_drive_test_log_5.0-12426.txt 5.0-12426 ZephyrSurfer, 07/09/2022 12:59 AM
optical_disc_drive_test_log_5.0-12436.txt (36.7 KB) optical_disc_drive_test_log_5.0-12436.txt 5.0-12436 ZephyrSurfer, 07/09/2022 12:59 AM
optical_disc_drive_test_log_5.0-16831.txt (36.5 KB) optical_disc_drive_test_log_5.0-16831.txt 5.0-16831 ZephyrSurfer, 07/09/2022 12:59 AM
fixed_PR-10821.png (131 KB) fixed_PR-10821.png Now Resolved PR-10821 ZephyrSurfer, 07/09/2022 02:01 AM
optical_disc_drive_test_log_PR-10821.txt (36.5 KB) optical_disc_drive_test_log_PR-10821.txt Now Resolved PR-10821 ZephyrSurfer, 07/09/2022 02:04 AM

Updated by ZephyrSurfer almost 2 years ago

Some sort of difference between physical and virtual memory. Is that significant?

Let me know if you need anything, I'll see what else I can do.

Actions #2

Updated by pokechu22 almost 2 years ago

That error code corresponds to DriveState::MotorStopped (5), DriveError::None (000000). 5.0-11476 introduced an issue there (see #12017), which was fixed in 5.0-12436 (PR 8571). Can you check that version and provide logs for it and the current version?

The difference with the physical/virtual addresses is because I changed the masking on s_DIMAR. I don't remember if there was a related hardware test or not, but this affects all games and is likely not relevant.

Updated by ZephyrSurfer almost 2 years ago

I included three. The one right before 5.0-12436 as well in case it helps in comparisons. A log from latest development version is included too

Actions #4

Updated by pokechu22 almost 2 years ago

OK, after looking at this further, I think I confused myself with that 0x5000000 motor stopped comment. With a current log, there would be logging for when a read is attempted with the motor stopped, and logging for when the game checks the error code.

There is, however, this in the log (which wasn't there in the working version):

58:28:616 Core\HW\EXI\EXI_DeviceIPL.cpp:306 N[OSREPORT]: 
test 0x600, pad bits set

The commit where I removed that masking was this one, where I note that it is "Based on a hardware test on a Wii". It's quite likely that the Wii handles masking differently here, since it has MEM2 from physical address 0x10000000 to 0x13FFFFFF in addition to the GameCube's MEM1 from physical address 0x00000000 to 0x017FFFFF. And, I'm guessing that this is specifically testing for that masking behavior, as it also tests what happens when writing to DICFG (at 0c006024), which should be nothing.

Can you test https://github.com/dolphin-emu/dolphin/pull/10821?

Actions #6

Updated by flacs over 1 year ago

  • Status changed from New to Fixed
  • Fixed in set to 5.0-17116
Actions

Also available in: Atom PDF