@sugarfree yeah, it's kinda what I had in mind.
I'm not very practical about shell scripting, however from what I could grasp it seems that they're creating a whole new mapping script to create evdev mappings.
Since I was trying to create a Python script that was going to be launched when a ROM had been selected and didn't want to add more dependencies, I tried to use SDL2 as library in my script: however the naming a of the buttons are extremely different from what you could get from evdev and had to make an intermediary translator between evdev and Dolphin passing through the SDL mapping of that gamepad.
Their solution is far more practical. However I think one of their bigger limits is that the script essentially creates a Dolphin profile for each gamepad, basically a 1:1 mapping between the gamepad and the GameCube controls. For the GameCube I think it's a pretty neat solution. Different matter is when you try to apply the same strategy when mapping a Wiimote: one profile isn't enough since you can have more peripherals setups on a Wii.
Two things I could think of are: making a profile for each possible setup (Wiimote, Wiimote+Nun chuck, Wiimote+Classic Gamepad etc...) and asking at each ROM load which profile should be loaded to each player, probably with a nice whiptail+joy2key TUI; or creating on the fly a configuration after asking which peripheral setup the player wants.

@sugarfree the game works well, except for the map only showing black screen,, which was supposed to have been fixed in newer versions, only doesn't seem to work on pi5.

@retropieuser555 said in Dolphin - GameID Identifier script help:

Ok dokay, I'll take a look. Is it usually Sony controllers that seem to have the issues? Or am I reading into that too much?

No, it's not a rule - it's just something I noticed at the time with the gamepads I tested.

First thought, it'd need to be done at the configscript point from ES mapping, as that's the point when the controller will be connected. Unless the input configuration script is run without the controller plugged in. Which I think is unlikely from a user perspective.

You can search at runtime and - if found - store it. I'm not sure if there's a rule, but tend to no assume that the device is connected and look only at the values given.

I'd envision searching for keywords to match SDL against evdev name, the only trouble is if the user has multiple controllers connected it may get it wrong.

Arcade cabinets have always controller(s) connected.

@sugarfree Ok nevermind. At first maybe I thought it was an rvz vs ciso thing, but I just loaded the .ciso 1080 Avalanche 5 times and on the 5th time it crashed. So I don't think the file type has anything to do with the random crashes.

@retropieuser555 Thank you! I will look into that!

These lines appear in the standalone version too but only affect the intro. The game is working without issues.

@sugarfree Ok that's great to know about the Vulkan driver. I do have it installed and working on lr-flycast-dev but was never able to get it running on the standalone version of Dolphin. It keeps throwing me an error.

So I'll give these scriptmodule changes a try right now.

Thank you!

@mitu said in Error installing dolphin...:

Well, that's a first. Auto-correct gone wrong ?

dolphin is not installable due to requiring an 64bit OS, the image for the Pi 3B+ is based on a 32bit Raspbian. Regardless of that, the 3B+ Pi model is not even close to be able to run the Wii/Gamecube emulator at an acceptable performance level.

ohh... ok..

Thx

@TPR I think that's this option:-

[Video_Hacks] DisableCopyToVRAM = False

you'll need to check the options they have documented on retroarch's wiki:-

https://docs.libretro.com/library/dolphin/

Although they're not named the same as regular dolphin so you might need to trial and error a bit

There was already a bug report - https://bugs.dolphin-emu.org/issues/13416. Furthermore, the Libretro port is not maintained by the Dolphin team, so your report will probably be closed/forwarded to the libretro repository.

It was possible to configure my controller with the instructions from this topic:

https://retropie.org.uk/forum/topic/35466/dolphin-controller-not-working/3

@retropieuser555

Hi,

You are right, dolphin works with OpenGL! I guess I did something wrong in my first test.

Dolphinbar work too and I didn't need to configure any rules for wiiremotes.

Thanks

@retropieuser555 yeah that's most certainly an option, but from what I've seen on the standalone, it isn't much different from the libretro core where you just go and manually load up the next disc, right? Disc Control > Eject Disk > Load disc.

That seems to work fine, I was just surprise to see the m3u format didn't want to pre-load the disc images.

@retropiedude said in Dolphin or lr-dolphin change emulator on RetroPie to OpenGL or start from:

Oh, that's interesting. Any idea what it's cause then?

Seems that Dolphin uses a Vulkan/GL extension which is not supported by the Pi5 drivers - https://gitlab.freedesktop.org/mesa/mesa/-/issues/10250. The issue has also been reported to upstream Dolphin, but I doubt it's going to be solved, in a reasonable time frame or at all.

@sugarfree That makes sense. I could have thought of this earlier. Big thanks!

Hi! I just ran into this myself, and thought I'd post this for anyone else who had this issue to give an alt method, If you want to configure it with the GUI (which may be easier). It takes a few steps, and you will need a mouse.

install Desktop in Raspconfig
2 use the dekstop terminal to run QT_QPA_PLATFORM=xcb /opt/retropie/emulators/dolphin/bin/dolphin-emu
3 configure your controller
4 important- while you are here, configure your hotkeys as well. Dolphin does not recognize the normal hotkey /exit button, it uses its own.

You can edit both GC and Wii controls this way

@TPR
If you want to play GameCube or Wii at fullspeed on a Pi5. You must use Dolphin standalone.
You just need to set your controller once and create hotkeys like lr-Dolphin and it will be like the lr-dolphin with the same hotkeys.

@mitu @abj Pressing hotkey+x the retroarch menu opens and I can change core options => language
Thanks for that, so I guess instead of using the gameini, I can also change language here