Emulator

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

I'm not sure why this specific problem occurs, but overwriting an old install can cause problems in general and is not supported.

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

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.

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.

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

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…

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

Note I havent tested WiimoteSource1 thru 3

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

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

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

Disregard the problem still there. My default setting where conflicting on this.
previous behaviour still ocurrs

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.

Good news as of version 5.0-4719 the error is gone. I need to do more testing, but so far so good.

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

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

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

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.

Is "background input" enabled? If not, could you enable it and see if the issue is still present?

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.

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?

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.