Project

General

Profile

Actions

Emulator Issues #11478

closed

Mario Kart: Double Dash!! - Unknown SI commands when "GameCube Adapter for Wii U" selected without being plugged

Added by tony971 almost 6 years ago. Updated almost 5 years 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-10417

Description

Game Name?

Mario Kart: Double Dash!!

Game ID? (right click the game in the game list, properties, info tab)

GM4E01

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

97f9ebc39ab4244e419848793988561a

What's the problem? Describe what went wrong.

If "GameCube Adapter for Wii U" is selected as a controller option without actually having the adapter plugged in, several "SI: Unknown Direct Command" prompts will appear on startup before loading the game.

What steps will reproduce the problem?

Select "GameCube Adapter for Wii U" as a controller option (in any slot) and boot past the GameCube Main Menu. Do not plug in a GameCube Adapter.

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

Dolphin 5.0-9202

Is the issue present in the latest stable version?

[Yes/No and version number here]

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

[First broken version number here (if applicable)]

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)

Intel Core i5-6300U, Nvidia GeForce 940m, Windows 10 Pro build 1809

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

[Anything else here]

Actions #1

Updated by Techjar almost 6 years ago

Confirmed this happens, but only on Windows. I couldn't reproduce it on Linux.

Actions #2

Updated by JMC4789 over 5 years ago

  • Status changed from New to Accepted

I've had this happen in any game actually. Not sure what causes.

Actions #3

Updated by FireNX70 over 5 years ago

This does not seem to be related to whether or not the adapter is plugged but to wheter the controllers themselves are plugged in or not as I'm getting this error with the adapter fully plugged (i.e. both USB connectors are plugged) in but only a controller on port 1 while having all 4 players assigned to use the WiiU adapter. 5.0-8764 is the first version to show this behavior.

Actions #4

Updated by tony971 over 5 years ago

FireNX70 wrote:

This does not seem to be related to whether or not the adapter is plugged but to wheter the controllers themselves are plugged in or not as I'm getting this error with the adapter fully plugged (i.e. both USB connectors are plugged) in but only a controller on port 1 while having all 4 players assigned to use the WiiU adapter. 5.0-8764 is the first version to show this behavior.

I've encountered this in both scenarios. Both with the adapter plugged but with less controllers connected than selected, and with the adapter unplugged. If you have "GameCube Adapter for Wii U" selected as a controller option without actually having it plugged, you will get this error.

Actions #5

Updated by FireNX70 over 5 years ago

Fixed by 5.0-10417

Actions #6

Updated by Billiard26 almost 5 years ago

  • Status changed from Accepted to Fixed
  • Fixed in set to 5.0-10417
Actions

Also available in: Atom PDF