RetroArch Wii cores

[cereal_killer]

I have a PS3 controller, now I have a hid modded version of Retroarch thanx to @Flame. My PS3 controller works right away (in the Retroarch menu and some of the cores). No need to change the driver, no need to press any buttons. But when I change the core (for example mame2003-plus_coreA_libretro_wii. dol or Arcade MAME.dol) the controller doesn't work. Neither in the menu nor when I load a rom. So, it is the cores that run the show not retroarch itself (as far as the controller is concerned)?

 

[JuanMena]

Have you tried poking around the Controller Option in the Core's Option?

There's also Input Settings in Settings.

I'm guessing you have to add your buttons in Input Settings.

Can you do the following?

• Go to Homebrew Channel
• Connect PS3 controller
• Start RetroArch BUT DO NOT LOAD ANYTHING
• Go to Settings / Input / Controller 1 (or Input 1)
• Take a picture of that screen and post it

• Load the problematic core
• Go to Settings / Input / Controller 1 (or Input 1)
• Take a picture of that screen and post it

 

[cereal_killer]

Have you tried poking around the Controller Option in the Core's Option?

There's also Input Settings in Settings.

I'm guessing you have to add your buttons in Input Settings.

Can you do the following?

• Go to Homebrew Channel
• Connect PS3 controller
• Start RetroArch BUT DO NOT LOAD ANYTHING
• Go to Settings / Input / Controller 1 (or Input 1)
• Take a picture of that screen and post it

• Load the problematic core
• Go to Settings / Input / Controller 1 (or Input 1)
• Take a picture of that screen and post it

Yeah, ok, i'll do it ASAP. I think you have a point because when I first loaded retroarch without loading any cores and went straight to the settings, there was "sixaxis controller" or something like that next to the controller 1 and once I changed it to something else (just to see what's gonna happen) the controller became unrecognizable right away and I couldn't control the menu with it. Wiimote got disconnected too by the way.

 

[JuanMena]

Okay...

Yeah, ok, i'll do it ASAP. I think you have a point because when I first loaded retroarch without loading any cores and went straight to the settings, there was "sixaxis controller" or something like that next to the controller 1 and once I changed it to something else (just to see what's gonna happen) the controller became unrecognizable right away and I couldn't control the menu with it. Wiimote got disconnected too by the way.

If you can't get it back to normal, go to your USB or SD or whatever you're using RetroArch with, and delete the settings file.

But make sure you make a backup of it in case anything goes wrong.

 

[cereal_killer]

Okay...

If you can't get it back to normal, go to your USB or SD or whatever you're using RetroArch with, and delete the settings file.

But make sure you make a backup of it in case anything goes wrong.

Yeah, yeah that's what I do when I get locked out of it. I'll report back with pictures and results

Post automatically merged: May 6, 2023

Didn’t have a chance to try what you recommended and take pictures (things have been crazy these last few days). Maybe today or tomorrow.

As for today, here’s a picture of the retroarch.cfg file (the one in the root of my SD card). With these settings (default settings when I first launch retroarch), my ps3 controller works fine in the menu and when I choose some of the cores (snes and sega genesis cores). I don’t know if it gonna be of help but that’s all I got at this point.

 

[cereal_killer]

finally, I found some time to mess around with retroarch and its cores.

From what I can tell - if the core supports the ps3 controller - it will work right away (both in the menu and when you load a game) but if it doesn't support it - the controller won't work no matter what you do and there's no way to change that in the settings.

So it is the cores that call the shots, not retroarch.

As you can see in the pictures, in case with the core that supports the ps3 controller - it is enabled by default. The cores that don't support it - there's no even the setting to enable it.