Summary for anyone trying to follow this thread:

Looks like retropie 4.3 defaulted to atart800 emulator. This needs a keyboard so I eventually found a hacked version of such to remap L&R shoulder to start/select to make it usable with just controller

retropie 4.4 seems to default new installs to lr-atari800 which has similar keyboard required, and doesn't seem to be able to change much via its config files. Actually it looks like to ignores just about anything given to it and there is no useful way to alter its behavior with command-line arguments. It will accept some retro arch config changes if done through the GUI console.

future.child lead me on to kat5200 emulator which an install script is available, This will download, compile, and install the kat5200 emulator into retropie.

The kat5200 emulator needs to be set up via keyboard, but once done so seems to work quite well. You will need to configure the location for your BIOS files, and then also define your input source (joystick) and re-map buttons where needed. The input screen can do most key mapping, and the user config screen has the exit emulator sequence. Two step button sequences can be set, so the usual select-start emulator exit can be emulated. Tip: seem like the config works better when you define multi press sequences in reverse, so when setting up the user input exit function, define 'start' as the first key then 'select' as the second. For my setup, I mapped #1 key to joypad-1 left soulder, #2 key to joypad-2 left shoulder, this works for some games to select 1 or 2 player. I also mapped # and * keys to X & Y on each controller as I think those are needed in some games.

I haven't tried anything beyond Atari 5200 games with this setup, but for that it seems to work well for a good selection of 5200 games.

I hope this helps someone!

@herb_fargus

The config for controller mapping in the Reicast config interface asks if you want to map buttons based off of the original controller button names, not the names of the buttons on the controller map located on the Reicast page.

This becomes a problem when the graphic on the Reicast page has a controller map with backwards buttons as you end up mapping buttons backwards. Either the Reicast mapping command prompt should change or the graphic needs to change to reflect the actual buttons. My vote is on the latter. The user must map the controller through the Reicast config prompts as none of the buttons work until you do so.

This is current as of 4.4 stretch.

The Reicast page also states that the controls are automatically configured as of 3.3. This is also false.

mame2003-plus has a new input mode specifically for this purpose.

It is activated via a core option which allows the core to process input through the either mame_keyboard interface or the retropad -- or both simultaneously as with classic mame2003 (although that is not as useful as you are finding out).

Unfortunately it does not seem to work.
I hpe that the regular hatari gets button configuration support so no keyboard is needed...

@darksavior said in psx emulator not working. tryd everything:

@steptoe Eh..even the most minimal of compression, eboot conversion is still my preferred way. Especially to convert multi-disc games to a single eboot file. You still need a cue file for .img.
It also doesn't hurt that just about every US release is already converted and it's more convenient to download those instead.

I pretty much do the eboot way as well cause some of my games i have copied over to ISO's would total up to around 1.4GB which after converting them to eboot files it would usually drop down to a little over 900mb instead which i am able to add more games onto my Pi because of that.

@mitu , thanks mate, exactly what I was looking for.

@cloudlink Not currently.

IIRC there is no root password.
Single user mode won't help as it requires root password too, and you need to be root to edit /boot/cmdline.txt in order to remove this.
So you can :

use a windows computer to add init=/bin/sh at the end of cmdline.txt in the /boot (fat) partition of the SD card use a linux computer (live distro if you don't have one), then mount root partition of the SD card and change ownership of sudoers.

@nestor1924 If you want to have a better scrapping for your games/systems i would suggest using Universal XML Scraper V2 since it looks better than the default scraper on the Pi.
Also Universal XML Scraper V2 you have to use on your PC but it is very simple to use.

@bpmnyc

It wouldn't work for a couple of reasons. Primarily, RetroArch will only use a mouse or pointer device to emulate a light gun. Popular solutions to this are AimTrak USB guns, as well as a Dolphinbar/Wiimote/Gun casing combo. Another big hangup was input lag, as the screen flash has to occur at the exact moment the trigger is pressed. However, thanks to recent developments that were previously thought to be somewhat impossible, this would no longer be an issue when using capable hardware. Still, support would nonetheless have to be added for RetroArch to interface with actual light guns.

@mediamogul This worked. It's not perfect for me as I prefer to skip the intro, however this is much easier.

I figured it out (Wii U), thank you so much!

@semper-5 sorry my mistake! I was on my phone and it abbreviates the titles of posts, so you are right I misunderstood.

@mitu This is what I’m talking about: xboxdrv. Scroll to the xboxdrv section and it talks about how this was broken. I ran into this on either retropie 4.3 or 4.2. I can only assume it is still broken, but I’ll give it a try again.

@batesman

Not a problem. I'm glad it worked out in some capacity.

@markyh444 I did your instructions and deleted the downloaded images and xml games list file on samba shares because I was tired of looking at the scrapes art on emulation station.

Only problem is that I rebooted emulation station and there is no recreated xml file, I checked on samba shares too. Not sure why there’s no new xml...

@chizzer thanks for the reply ill give it a shot

Here is another fact, I started a new image from scratch and moved exactly the same amount of roms, the system is duplicated manually in a fresh install and it takes 2.84 seconds more to load ES on the new PI3B+ running Retropie 4.4 than the PI 3B running 3.9, its akward, but true. I have an intro video wich overlays the ES loading screen and now I have to make it that time longer because Retropie 4.4. with a PI3B+ takes more time loading.