@mitu they were inserting spam links into quoted text.

@jordanhuckaby

Update if anyone is looking for a solution:

I confirm I now have a working solution to play Backyard Football 2-Player using two built-in joysticks.

Since lr-scummvm already recognized the first joystick as a mouse, I left player 1/joystick 1 untouched. My problem was with joystick 2; ScummVM would not recognize this as a keyboard, and thus Player 2 could not control anything.

I used xboxdrv to configure the second joystick as a keyboard when ScummVM is used. This was done by editing the runcommand-onstart file, as outlined here: https://retropie.org.uk/docs/Universal-Controller-Calibration-%26-Mapping-Using-xboxdrv/. Since Backyard Football only needs the keyboard directional keys and the right-control button, I only mapped these (joystick as the directional keys, and a cabinet button as right-control). Once ScummVM closes, this virtual keyboard gets eliminated through the use of the runcommand-onend file (again, in the doc linked above).

After doing this, a notification would appear when opening ScummVM mentioning that an X-Box Keyboard Emulator has not been configured. This was a positive sign because it shows that the virtual keyboard was being created by opening ScummVM. Unfortunately, Player 2 still was not configured to use this keyboard.

The final step was then editing the retroarch.config file for ScummVM. I first had to map Player 2 to use the new virtual keyboard, which was done by pointing to the new joystick number (2 in my case). I also had to re-do the B=right-control mapping in retroarch that was done in the runcommand-onstart file.

After doing this, Player 2's movements were being registered in ScummVM. Strangely, Player 2's movements were also moving the mouse cursor (Player 1). The final step was to tell the retroarch.config file that player 1 should not have any keyboard functionality. I did this by manually mapping each directional key and right-control to "nul" for player 1, similar to the following: input_player1_up = "nul". Now, moving joystick 1 controls player 1 (mouse), and joystick 2 controls player 2 (keyboard, via xboxdrv).

Good luck!

@buzz Thanks! That worked!

@doctorbeefy said in Majority of screen hidden when launching game:

Bumping this as I am having the same issue. Anyone come across a fix? it seems to only happen for Sega Mastersystem/genesis and lr-genesis-plus-gx, other systems and cores work fine.

For most people, this glitch is something that originates in RetroArch and needs a fix. A future release of RA will probably take care of it. In the meantime here is a workaround:

After the game starts and you see this happen, use (Hotkey + "B") to reset the ROM. It should come back with the whole screen visible.

EmulationStaton doesn't need sudo to run and never has.
We don't support DietPi on the Pi, so I'm not sure you're using the RetroPie main repository or some fork that supports DietPi.

@mitu Thank you so much for your help. I really appreciate it. I'm sorry ended up with some custom BS image, but at least I'll learn more by starting from scratch.

handshake.png

@buzz Thanks, I'll try this, then.

Cheers!

@jayjayuk said in Emulation Station Gamepad Enumeration:

They are all using generic USB encoders which detect as Dragon Rise
Is this the expected behaviour? or a bug?

This is expected - the input configuration is tied to the name of the controller, so configuring one of the controllers will generate a configuration for all of them. When you configure one of the 6 buttons controllers, the same configuration is applied to the rest of the controllers with the same name (including the ones with the 4 buttons layout).

I would add that in the /boot/cmdline.txt parameters, I changed the resolution to 768x768 and everything is now centered and looks correct....except, the top few lines of the [TAB] menu in Mame are cut off....

This is so strange.....

I figured it out.

It was under "Experimental" modules.

So, in other words, the card doesn't have a software volume control and you had to add a fake one to keep ES (or other ALSA based mixers) happy. That doesn't seem too practical if your Pi is not easily accessible.

Glad you got this sorted out, it's a good use case to have in mind.

@ilchymis
I would just like to add that the BIOS file for lr-genesis-plus-gx is different from the one for lr-picodrive.

It sounds like your lr-picodrive BIOS file is correct, while the one for lr-genesis-plus-gx is not (as mitu has suggested).

I'm pretty sure your issue is not the same as mine, since my BIOS files were correct. It simply couldn't find them due to mis-configuration.

Thank you for your post. Having two SF30 pro and got the same issue.
After configuring as per you post above, the mapping is strange. For example, the hotkey is used to jump under tomb raider.
In other words, the controller map is not as per lib-retro "standard" for psx. Any idea how to be back on standard lib retro mapping ?
My config : retropie 4.7.3 / pi 4

Bonjour, j'utilise retropie sur ubuntu 18.04 et installé dolphin.
tout fonctionne a part que si je met la langue de la wii en francais , a chaque démarrage du jeu avec emulationstation le jeu change de langue automatiquement et repasse en anglais.
sur la gamecube je n'est pas ce probleme
quand je lance dolphin sans passé par émulationstation la langue que j'ai choisi se met bien et reste tel que je l'ai mise, des que je lance les jeux avec emulationstation la langue se modifie et ce n'est plus celle que j'ai mise
Es-ce que quelq'un a déja eu le cas et a une solution
merci

I found another option for getting performance information logged - RetroArch performance counters: https://docs.libretro.com/guides/generating-retroarch-logs/

I haven't seen anything useful logged yet though :/

Ok, so having spent quite a bit of time on this, I would have to downgrade my assessment to semi-successful - ha! I ended up having to install alot of emulators that I thought would still be on there as they were on my old build, and nearly all the other emulators had binary updates for me to run.

My RetroPie build is very basic really, with the only tweaks being those detailed in the official docs, so looking back I think if I was to do this process again, I would just start completely clean and go through each system one by one to check all is working correctly and updating/tweaking as appropriate. At least then I would know what needed to be done, rather than finding some things had copied over and other bits hadn't. This is most definitely due to errors on my part I'm sure.

On the plus side, on my 4.4 build my Sega CD and ZX Spectrum games wouldn't work (Sega CD would jump back to ES, and ZX Spectrum would crash the Pi) but now they do, so not sure what happened there but it's all good now - ha!