Emulator Issues #12369
open
Program crashes upon opening Emulated Wii Remote Configuration with complex settings while a game is running
0%
Description
Game Name?
N/A. Crashes with any Wii game.
Game ID? (right click the game in the game list, Properties, Info tab)
N/A. Crashes with any Wii game.
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
N/A. Crashes with any Wii game.
What's the problem? Describe what went wrong.
While any game is running, attempting to click "Configure" for any Emulated Wii Remote controller with complex settings will cause the entire program to forcefully close.
What steps will reproduce the problem?
- In Controller Settings, set "Wii Remote 1" to "Emulated Wii Remote".
- Click "Configure" for "Wii Remote 1".
- Load the provided ComplexWiimote.ini controller profile for the Wii Remote 1 controls.
- Close the Wii Remote 1 controls.
- Start any Wii game.
- Wait for game to fully start. Proceeding while game is still starting will not trigger the crash.
- Click "Configure" for any Emulated Wii Remote controller. The Controller Settings window may be opened before game is started or not.
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. Present development version is 5.0-13374.
Is the issue present in the latest stable version?
Unknown. Attempting to run the stable version results in several "Trying to read from invalid SYSCONF" error dialogues, and Wii games cannot run due to being unable to find "connection handle 100".
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-11035 "Expression parser improvements (PR #7663 from jordan-woyak)"
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
N/A. Not a graphical issue.
What are your PC specifications? (CPU, GPU, Operating System, more)
See PcSpecs.txt for CPU-Z report.
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Make sure to download ComplexWiimote.ini as a testing file. It is one which I use for a gimmick setup for Super Mario Galaxy, and it triggers this crash.
Unfortunately, no useful information shows in the log. It seems the program crashes too quickly for anything to print if it's trying.
Files
Updated by JosJuice over 3 years ago
- Milestone set to Current
- Regression changed from No to Yes
- Regression start set to 5.0-11035
Updated by
Updated by JMC4789 almost 3 years ago
- Status changed from New to Accepted
Any update on this, Billiard?
Updated by Dentomologist over 1 year ago
I haven't been able to reproduce this on either current master or 5.0-13374.
Windows 10 1903
Direct3D 12 and OpenGL
I used the included ComplexWiimote.ini profile and waited for the Mario Galaxy title screen to come up before doing step 7.
If you're still able to trigger this can you try doing it with a fresh portable build? Put an empty text file named "portable.txt" in the same directory as Dolphin.exe, which will cause Dolphin to create and use a new user folder inside the Dolphin directory (leaving your old one alone). Add the ini to the new user folder the same way you did the old one, and see if it happens again.
Once you're done testing, delete portable.txt to get your original user folder back.
Updated by yoshimo over 1 year ago
I am unable to reproduce this for myself on current master, but it does still happen on the original current version for the bug report. Using a fresh portable build avoids the crash; however, when using Super Mario galaxy at the title screen, the emulator seems to forget that the Nunchuk is connected briefly, for the game displays a prompt to reconnect the Nunchuk.
Updated by AdmiralCurtiss over 1 year ago
If you can't reproduce it in master, maybe it was fixed by 5.0-16790? Can you compare these two builds?
https://dolphin-emu.org/download/dev/de3d1344d5ed939faedae9c19e2e340a83038aba/
https://dolphin-emu.org/download/dev/24498ca3159130eca123dc25ccae92781fdc3c34/
Updated by yoshimo over 1 year ago
5.0-16788 produces the same Nunchuk disconnection as when using a fresh portable build on 5.0-13374. Note that a fresh portable was not used for 5.0-16788.
5.0-16790 does not produce any errors, and seems to function the same as 5.0-17258, the current master used for my last addendum.