Emulator Issues #9886
closed
Dolphin crashes when a game launched through the terminal has a game INI that sets WiimoteSource
0%
Description
Game Name?
[Put Game Name here]
Game ID? (right click the game in the game list, properties, info tab)
R7FEGD
Multiple other games
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
aad70dfa937ebfe6c39e375e9bb5304b
What's the problem? Describe what went wrong.
I found a problem that seems to only occur when using command line to play Wii/WiiWare games only. I see the behaviour using rocket launcher or plain command line. This error does not occurs by using the gui. Basically Dolphin crashes with error *** Caught unhandled unknown exception; terminating" This only happens on any revision above 881. I tested all the way to 1316 and the error happens. It does not happen on revision 867 and below. The command I use is R:\Emulators\Dolphin\v5.0\Dolphin.exe /b /e "R:\ROMS\Nintendo Wii\Final Fantasy Fables - Chocobo's Dungeon [R7FEGD].wbfs"
Note that the games works and have been working in any revision from 867 and below
From 5.0 thru 5.0.1316
What are your PC specifications? (CPU, GPU, Operating System, more)
Machine Id: {C0328FB0-C767-40C6-A1E2-1C53F92D9EA2}
Operating System: Windows 10 Pro 64-bit (10.0, Build 14393) (14393.rs1_release_inmarket.161102-0100)
Processor: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16318MB RAM
DirectX Version: DirectX 12
Graphics Card: NVIDIA GeForce GTX 770
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
I also notice that it happens on must games but not all. if I run R:\Emulators\Dolphin\v5.0\Dolphin.exe /b /e "R:\ROMS\Nintendo Wii\Arc Rise Fantasia [RPJE7U].wbfs" or R:\Emulators\Dolphin\v5.0\Dolphin.exe /b /e "R:\ROMS\Nintendo Wii\Castlevania Judgement [RDGEA4].wbfs" this two games run. So far I have tested 12 games I have I keep you posted with more findings. How can I debug to see what is causing the problem?
Files
Updated by Egnom over 8 years ago
Ok. Tested from fresh install and it works fine. I dont know what is the error when you over write existing files, but if I overwrite the files the error comes back up. Ill continue testing over the weekend dont have much time today
Updated by JosJuice over 8 years ago
I'm not sure why this specific problem occurs, but overwriting an old install can cause problems in general and is not supported.
Updated by Egnom over 8 years ago
Ok. Tested fresh install and it works fine on all my games. For some reason after 881 overwriting installation breaks the command line portion of the emulator. Thanks all for your time and patient
Updated by Egnom over 8 years ago
Hello everyone. I have being out for a bit and the issue stated above had returned. I have narrowed it down to the User GameSettings inis if I delete the game ini that I'm calling via command line it give the error. Again it happens only in command line and only to wii games this far I haven't tested all of them, but so far 10 out 165 show the error. Now I'm not overwriting the installation file I get the new version and moved the user folder. I notice that Dolphin worked when I did not move the user folder and I started to move each folder until I got the error only with the Game Setting folder.
I did not notice that when I was testing previously When I tested before I did not put the User folder on the clean install, when I overwrote the original installation folder that one had the User folder. What I need to do to narrowed down the issue.
Updated by JosJuice over 8 years ago
- Subject changed from Command line Issue om git 881 and above to Command line Issue on 5.0-881 and above
- Status changed from Invalid to New
Can you clarify what you mean by the user folder? Do you mean the Sys folder, or are you actually using a User folder with portable.txt?
Updated by Egnom over 8 years ago
- File R9IE01.ini R9IE01.ini added
Using the User folder with the portable.txt. I will delete the portable.txt and try the User folder (the one that gets created on My Documents) and report back if I get error.
The Game inis I'm talking are the ones that the user configures not the default inis.
Attached is the one for pikmin.
If I delete the content of the custom ini and it works. That the reason I had some games that worked and others that did not was because I did not have custom inis on all my games now I do and so far all of them fail to load in command line. Now that I'm back getting all my systems squared away i notice the issue and this issue is very evident on any version after 5.0-881. This is the command line I use for pikmin R:\Emulators\Dolphin\v5.0\Dolphin.exe /b /e "R:\ROMS\Nintendo Wii\Pikmin [R9IE01].wbfs"
It works fine on the via gui launch, but I'm testing RL and it use command line to launch the games. I have done the command line without RL and still shows the same error
Updated by Egnom over 8 years ago
I just tested without the portable.txt and move the custom ini to the GameSettings folder under the User folder and the error persist. I delete the custom ini and it works.
Updated by JosJuice over 8 years ago
- Subject changed from Command line Issue on 5.0-881 and above to Dolphin crashes when a game launched through the terminal has a game INI that sets WiimoteSource
- Milestone set to Current
- Regression changed from No to Yes
- Regression start set to 5.0-881
Thanks for narrowing it down. It seems like you have the same issue as this user: https://forums.dolphin-emu.org/Thread-can-t-use-per-game-inis-for-wii-remote-anymore
Updated by Egnom over 8 years ago
After looking at the user thread I remove the [controls] and the lines below and it worked. So the error is related to the handleling of the controllers in the custom inis.
Edit the ini for fire emblem as follow:
Before (error happens)
[Core]
DSPHLE = False
[Controls]
PadType0 = 6
WiimoteSource0 = 0
PadProfile0 = F710
After (error does not happens}
[Core]
DSPHLE = False
Updated by leoetlino over 8 years ago
I strongly doubt the issue was introduced in 5.0-881. Rather, this commit is likely the culprit. I added the lock to avoid a crash if Wiimotes are connected the WX app finishes initialising, but this seems to cause a deadlock in some cases…
Updated by Egnom over 8 years ago
I did more testing and it seems the error only happens for games were the WiimoteSource0 is used and is set to other than 0.
I will try to set the wii mote on the gui as a default and over write on the custom ini and see if that works. I will report back later this afternoon
Updated by Egnom over 8 years ago
Well I tested by enabling the Wiimote on the gui and deleting the entry on the custom ini and the game works, but when games that I need the Wiimote disable and the pad enable the error comes back. The error still tied to the WiimoteSource. Makes sense???
Updated by Egnom over 8 years ago
Tested with 5.0 Release today and the issue is not present on that version. I tested in the past and the error started on 5.0-881, but I can keep testing for you guys to get the specific place were the issue started. Let me know
Updated by Egnom about 8 years ago
Tested with 2472 and the issue is gone. I only tested with to games and Have not try GC or WiiWare yet, but the issue as of now is not there
Updated by Egnom about 8 years ago
Disregard the problem still there. My default setting where conflicting on this.
previous behaviour still ocurrs
Updated by sdspiros about 8 years ago
I ran into this same issue after I uploaded a new version of Dolphin. I figured out that versions 2872 and 3036 trigger this error, but for whatever reason, version 2670 does not.
Updated by JosJuice almost 8 years ago
- Has duplicate Emulator Issues #10025: Dolphin crash when starting games through command line added
Updated by JosJuice almost 8 years ago
- Has duplicate Emulator Issues #10404: Launching from command line with WiimoteSource0 in game config will crash emulator added
Updated by Egnom almost 8 years ago
Good news as of version 5.0-4719 the error is gone. I need to do more testing, but so far so good.
Updated by Egnom almost 8 years ago
Egnom wrote:
> Good news as of version 5.0-4719 the error is gone. I need to do more testing, but so far so good.
Disregard Hyperspin and RL were opening 5.0. Behavior still exist. When I ran the cli manually it did not work
Updated by Egnom almost 8 years ago
Egnom wrote:
Egnom wrote:
> Good news as of version 5.0-4719 the error is gone. I need to do more testing, but so far so good.Disregard Hyperspin and RL were opening 5.0. Behavior still exist. When I ran the cli manually on 5.0-4719 it did not work
Updated by Egnom almost 8 years ago
Egnom wrote:
Egnom wrote:
Egnom wrote:
> Good news as of version 5.0-4719 the error is gone. I need to do more testing, but so far so good.Disregard Hyperspin and RL were opening 5.0. Behavior still exist when I ran the cli manually on 5.0-4719 it did not work
Updated by leoetlino almost 8 years ago
- Status changed from New to Fixed
- Fixed in set to 5.0-4825
Should be fixed in 5.0-4825
Updated by Egnom almost 8 years ago
True it does not crash anymore great that is fixed, but now the pad wont work. I got the pad to work after I open the configuration windows and press any of the buttons that are configure under that window. In the other hand the Wiimote (real one) works fine.
Updated by leoetlino almost 8 years ago
Is "background input" enabled? If not, could you enable it and see if the issue is still present?
Updated by Egnom almost 8 years ago
Tested on 5.0-4952 and the issue was resolved. Tested about 10 games 5 pad 5 wiimote and they all work fine.
Big props on this fix.
Updated by Egnom almost 8 years ago
background input is not checked. But when tested on 5.0-4952 all work as intended.
Background input is new what is it use for?
Updated by leoetlino almost 8 years ago
I was trying to figure out whether you were hitting another bug (Dolphin sometimes has issues detecting whether the render window is active). Since the issue ended up not being present in the latest version, it may have been already fixed at some point. Glad to hear it's now working fine for you.