Wii controller not working

Nintendo64 · 2019-03-19T12:32:30+00:00

Hey I had a question about the wii games. I'm running batocera 64 bit 5.20 (the latest version) and I put some wii roms on the emulator and they work but the...

nadenislamarre

@BMC_War_Machine or maybe you broke something with the gui configuration that is not controlled by batocera.
can you rename system/config/dolphin and rerun a wii game without changing configuration via the gui

Dragu

nadenislamarre
In 5.20 the WII emulation mode was working perfectly, even if some people didn't arrived to configurate it.
On 5.21 this was not the case anymore and it was no individual configurations reloaded at game start. Now,
for me, if you dont switch back to 5.20, concerning Dolphin, you will never resolve the problem in emulated
game controllers. That you look for real WIImote connection is ok, as long as it not destroy functioning of emulated
game cube controllers, what is the case for 5.21.

marcelosofth

nadenislamarre Mario Kart Wii really works the control, but I do not see any advantage in just let this game work if the others do not work, I will give another example, one of the best games of the Wii is Donk Kong Country, this game requires Wiiremote and also of the motion sensor mapped, otherwise the Monkey can not leave the house in the first phase, ie outside the Gui it is possible to map all the buttons, however within the Gui these settings are ignored and only work the standard buttons and does not solve the problem of button mapping, motion sensor, etc.

I am not sure why the Atari 800 and Atari 5200 are separate because they can not run their bios separately for their systems, that is, whenever the last selected bios will call the next system, it is urgent to do the same process that is done in Colecovision and MSX where Bios exists as "Auto".

BMC_War_Machine

nadenislamarre sorry for the late response. I tried that and had no luck. Really this is the only thing i cannot get working right with Batocera. Everything else works beautifully. I don't stress too much on the negative comments. People sometimes get frustrated when they are tinkering with things for days and weeks on end with no success, even when others say "it works for me". Im guilty of that myself at times lol. I understand what it's like to be working on something with a very small team and it can get hectic at times for sure. Just know that a lot of us on here appreciate what you guys do.

nadenislamarre

@Dragu ok, but you must be more precise while it works on my side.

batocera 5.22 :
nothing in batocera.conf about wii.
classical pad plugged > starting mario kart => working
classical pad plugged + wii.emulatedwiimotes=1 > starting mario kart => working

however, just understand that in this order, my pad is configured for both gamecube+wii, thus maybe it may cause trouble. but it works.

can you give me a way it is not working please ?

nadenislamarre

@marcelosofth in the thread, Nintendo64 is talking about super mario kart. you told it is a known issue. in your last post, you say it works.
i understand that there is a problem, but we must be precise, otherwise, i will not found the problem.

nadenislamarre

"I am not sure why the Atari 800 and Atari 5200 are separate because they can not run their bios separately for their systems, that is, whenever the last selected bios will call the next system, it is urgent to do the same process that is done in Colecovision and MSX where Bios exists as "Auto" : not understood.

marcelosofth

nadenislamarre they use the same core and that is why there is only a single configuration for the 2, so when I choose Bios Atari 5200 it is also used for the Atari 800 and there are the big problems because it has Atari games 800 that do not accept Bios Atari 5200.

Ps: This happens also with Colecovision and MSX, but there is the option of "Auto Detect" as well so the system identifies what type of game is running and calls the corresponding bios, that is what must exist for the Atari 800 and 5200.

bluemsx_cartmapper = "Auto"

nadenislamarre

i've created a patch that may solve your issue.
please test and report the next 5.22 beta https://batocera-linux.xorhub.com/upgrades/x86_64/beta/
so that i see if that's enough or something must be done before the 5.22 release.
i will build it in the coming hours.

Dragu

nadenislamarre
Sure, I can give you. So, if in 5.20 I configurate the joysticks and buttons of my USB controllers as Game cube emulation, this is normally the default configuration that will not be erased when I leave ES. I can also save this configuration under a profile where I choose the name and that I can reload at wish after boot.
In both case I can just play with the configuration from last time. In 5.21, as soon as I start game, he use a phantasy configuration that I never defined and that he probably derive from some retroarch config that was never in relation to a dolphin game in my gameplay. To be accurate, I have no idea where this configuration is coming from. And even when I reload my saved profile configuration, I always land at startup with the phantasy one.
You can just not use always the same keys for different games because of the differences in the games. Therefore in Dolphin as in Dosbox, standard automatic game control make just no sense.

nadenislamarre

@Dragu this is not a bug. batocera handles itself the key from the menu>controller section.
whatever you do in the dolphin-emu configuration tool about pad will not be applicated.
this is wanted.

@BMC_War_Machine
can you provide me a step by step way to reproduce. the issue for the moment is that i understand that in some case the pads are not working, but i don't understand how to reproduce.

Dragu

nadenislamarre this is not a bug. batocera handles itself the key from the menu>controller section.
whatever you do in the dolphin-emu configuration tool about pad will not be applicated.
this is wanted.
So, I have no solution to stick with 5.20 or to move on another platform.
I cannot agree with you, as this configuration should be modifiable by the user, otherway if you dont have the original gamepads and in general for all bartops and other arcade machines you just forget Dolphin on Batocera.

BMC_War_Machine

nadenislamarre I'm not doing anything other than configuring the controller on the first start up of Batocera. When i try to launch the Wii with games that are compatible with the Gamecube controller, it works perfectly. But anytime i try to launch a game that is a wiimote only, either from the side or vertical, it says all 4 wiimotes are disconnected. I edited the line like you have suggested on emulated wiimotes = 1. It does save that, even after a reboot. But when launching games like i mentioned it still says disconnected.

If i open up Dolphin under the file manager > applications > Dolphin, i can open the controllers tab, then on the "emulated wiimote" section i can edit my controls. By default the screen with the controller assign is blank. By controller i assign i mean the dropdown list with which controller you are using generic xbox pad/etc. If you launch a game while still in the dolphin menu it works perfectly. But as soon as you quit the file manager, and try to load the same game (or even others like it)from the batocera menu, it still gives the "wiimotes disconnected" message. It seems like something inside of the default setup of batocera is fighting with what can be edited in file manager, after the changes are made and it's closed they are either not being saved or overwritten by something else.

Fransis

nadenislamarre Thanks buddy, I already assumed that it had to be the dongle or the wiimote, I imagine that the dongle of asus does not work very well in linux, I remember that I already had problems with it in the past.
I will search for a compatible realtek or similar and try again, the truth is that I really want to play Wii again.
thanks for the great work and attention

nadenislamarre

@BMC_War_Machine the beta2 for 5.22 x86_64 is available.can you confirm you've still the bug please ?

BMC_War_Machine

nadenislamarre Downloading now. I'll report back ASAP

Dragu

nadenislamarre
I think that your dev team has a basic understanding problem concerning key mapping in Dolphin.
And it seems, reaction the same as in Recalbox. No critic allowed, devs become angry. So, last time I will repeat myself what was already told endless times here in the forum and that nobody reads, as you hang just around in this awfull chat.
Dolphin is in key mapping pretty the same as Dosbox but I doubt somebody in your team also really knows Dosbox. Lets take two Pads, first for Player 1 and second for Player 2. In Dosbox you can map controls of Player 2 to Player 1 in order to use it (as example) as mouse for Player 1, if configurated this way.
In Dolphin, if you need Nunchuck. you can also map controls from Player 2 to Player 1. In the controller configuration of Dolphin and depending of the game where you have to do with. It is IMPOSSIBLE to resolve this by automatic configuration out of the emulation station controller menu. What you also dont do for Dosbox.
I am not waiting for a solution, its summer, I have other things to do, but next autumn/winter I must find a solution that works.

BMC_War_Machine

No change. I tried going straight into a game that uses the wiimote from the side and got the same error message. I went into the Dolphin GUI and mapped the controls, changed the settings, saved the profile and launched from inside the GUI and it worked just fine. After exiting the GUI and File Manager it gave the same error message when i tried to load it from the Wii menu.

nadenislamarre

@BMC_War_Machine which game are you trying to play that i test in the same condition please ?

@Dragu you should switch to retropie ; it is a system for more advanced users wanting advanced configuration like you want.

BMC_War_Machine

nadenislamarre New Super Mario Bros Wii, Donkey Kong Country The Return, Kirby.

« Previous Page