@mrmadcatz

UPDATE: I was able to fix the issue by going to RetroPie Setup > Core Packages and returning both the Retroarch hot keys and EmulationStation controls back to their defaults. Once I remapped the controllers again in ES, they carried over to RA.

@mitu Thank you! That was exactly the step I was missing!

@mitu i discovered that the file i was trying to play had H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
codec

i tried playing a video from really old times whose pixel layout was the exact same as my spi display 320x240 codec of that file was Xvid this time it didnt play anything it just crashed

Hello! I realised that maybe you guys are assuming that my usb keyboard is a gaming keyboard. It isn't. I think I'll have to buy an actual video game controller eventually. Thanks anyway for your guys' help!

Hi All

Thought I'd put on an update to say that I've solved my own issue.

I changed the config to include a 3rd player. In the config that player shares certain keys with P1 & P2 (start, coin etc...). I can then set the first 2 players up with CD32 controllers and the 3rd player as a keyboard. As the keys are shared, I can set a mixture of controller buttons and keyboard keys to the same physical buttons.

So Far it's working really well.

@mitu Many thanks for the quick feedback!

I have followed the advice on the network interface and the use of triggerhappy. I also looked into overlays in RetroArch and developed a solution. I would like to briefly explain this so that other users can also benefit from it.

First, I configured RetroArch so that content-specific overrides are loaded (if available). For each game for which an infoscreen is to be displayed, I have defined two overlay-pictures in the override. The first image is always a blank image (blank.png) and the second image shows the controls (e.g. pacman.png).

In the background, triggerhappy queries the keystroke of an unassigned button and then sends the following commands to RetroArch: OVERLAY_NEXT and PAUSE_TOGGLE. I had to program a small script to execute both commands simultaneously. Finally, I integrated the start of triggerhappy as a daemon into the boot process. Works great! :-)

If anyone has any questions or needs help, I will be happy to provide further information.

@windg Hi again.

I took your advice and uninstalled RetroPie completely, then reinstalled everything again.

Everything works as intended, and now I can also play N64 games (mupen64plus-next wouldn't load previously).

Thanks for helping.

@Muckypaws I think you can do this with core input remapping.

For quick menu > controls > port 2 controls, you want to set the joystick directions to their right stick counterparts, and then set mapped port to port 1. Now the player 2 joystick should behave as player 1 right-stick. Save this as a game remap file and you should be all set.

https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

Just to make sure I understand, you said that the scalefx would likely not working even if they are from the repo you linked me to, correct?

Indeed.

This has been taken care of.

Download the below as zip:

https://github.com/pinkeen/libretro-common-shaders-glsl

extract to pc.

Move wanted shaders to:

[/opt/retropie/emulators/retroarch/shaders/whateverfolder/whatevershader.extension]

@billydent said in USB controllers/keyboard no longer work in games, only ES:

I didn't have to go through reinstalling Retroarch -- I deleted retroarch.cfg and rebooted and everything worked again!

As I said earlier, re-installing will add the default RetroPie configuration, which you'll need. Just removing the file and running RetroArch will generate the default RetroArch config, which is not always suited for a Pi. YMMV.

I'm not sure where the translation options are shown in the menu, if you want to enable from the configuration file I think only 2 options are really needed to start:

ai_service_enable = "true" input_ai_service = "<key>"

where <key> should be replaced by the keyboard key that will trigger the translation service. If you're using a gamepad, then input_ai_service becomes input_ai_service_btn and the value should be the code for the input button you want to use (i.e. input_ai_service_btn = "11") - you can find out the values for each button by looking at your gamepad configuration in /opt/retropie/configs/all/retroarch-joypads/<gamepad_name>.cfg.

See also https://retropie.org.uk/forum/topic/28461/translate-games-on-the-fly/8

@Manukan depends how your controller is mapped in Emulationstation maybe? If you've got the d pad and analog controls mixed up there? It'll mix them up in Retroarch.

Anyway glad you got it working, very few n64 games use dpad anyway so just map it to analog stick

@StuMcBill I’ve managed to get it working somehow! No idea how.

@oskeeeddie said in Can't change emulator:

This is what shows up.

That's after the RetroArch has started up and - as I said - you can disable the notification by modifying the configuration file.

If the button is recognized by EmulationStation, then it should work in any Libretro cores - I think you're confusing the 'home key' (keyboard) with 'home button' (joypad).
Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first - including the exact controller type and model you're using.

@spannernick1 Dude, retropie works without doing all that... only install with the script for debian and derivatives

Right now, the documentation here https://retropie.org.uk/docs/8Bitdo-Controller/ gives advice which seems kind of wrong.
First of all, you shouldn't be using Bluetooth at all. It has too much input lag for gaming. Maybe if all you want to play is visual novels or watch movies with Kodi then Bluetooth is fine but for anything video game related that has actual game in it which isn't just a video, you shouldn't be using Bluetooth at all AFAIK. Too much input lag. Use a wire.
Second, it suggests that you can go in and edit the RetroArch controller configuration files. Well, maybe. Until the next time you plug a controller in and then RetroPie's EmulationStation will overwrite those files with whatever it thinks your controller mapping should be, completely undoing all your hard work.
There's got to be a better way to handle this whole aspect of RetroPie from a design perspective.

@raspretro314 this feature is meant for retroarch's online updater, which is not what is used when updating cores on retropie.

Updated ...all/retroarch.cfg to reflect:

input_player1_mouse_index = "3" input_player2_mouse_index = "3"

...and BOOM! It worked.