Emulator Issues #11372
closed
AndroidTV / NVidia Shield: Using DolphinBar with 2 Wii Remotes crashes on startup
0%
Description
Game Name?
New Super Mario Bros. Wii
Game ID? (right click the game in the game list, properties, info tab)
SMNP01 (00010000534d4e50)
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
a64956f231e877282d004093ebb323f3
What's the problem? Describe what went wrong.
When using 2 real Wii remotes via the DolphinBar, Super Mario crashes on startup.
What steps will reproduce the problem?
- Make sure the DolphinBar is directly connected to the NVidia Shield (no USB hub!)
- Make sure the DolphinBar is turned on
- Make sure that DolphinBar LED4 is on ('Wii Emulator Mode')
- Make sure that DolphinBar LED0 is on (which indicates that it has found the Wii controllers)
- Make sure that the two real authentic Wii Remotes are turned on
- Then start Dolphin
- Configure Wii Remote 1 and 2 as 'Real Wii Remote'
- Configure Wii Remote 3 and 4 as 'Disabled'
- Enable 'Continuous scanning'
- Start 'Super Mario'
- Now both controllers will rumble shortly to indicate that the controllers were found by Dolphin
- Dolphin returns to main menu, without starting game and without crash dialog
These steps are a 100% reproducable way to reproduce the bug.
However, the following related effects were observed while narrowing down the situations in which it does occur:
- With 'Continuous scanning' disabled, the game starts. Then select 'Refresh Wii Remotes'. This will rumble and crash in 90% of the cases. In 10% of the cases, the game continues and can be played with 2 players.
- With one Remote enabled instead of two, it crashes sometimes.
- Sometimes the crash happens during the rumble: in that case, the rumble of the second controller continuous rumbling forever
- Sometimes it also crashes after some minutes into the game
- On Windows it could not be made 100% reproducable, but crashes were observed
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, 8715
Is the issue present in the latest stable version?
No stable Android version was tested. However, a version of 6 months ago did work at that point.
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)
NVidia Shield 2017 edition, Oreo
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
No logs were found in Android (maybe logging must be turned on?)
Files
Updated by 
Updated by 
Updated by 
Updated by 
Updated by