@cmscss Yes... the multi_switch.sh script always provides safe shutdowns.

Deepsleep happens if after shutdown the red LED still glows. So you need a power device that cuts power after shutdown. But no script can change the behaviour without the hardware parts.

But deep sleep is a very cheap alternative to those power devices. You may try it out ;) Just connect any switch to GPIO3 and ground (it's pin 5 and 6 on the Pie header) only this GPIO enables a repowering after shutdown ;)

@qnsht Assuming you have mapped correctly your controller, open the RetroArch RGUI while in game, then change your gamepad type to analog - see https://retropie.org.uk/docs/Playstation-1/#analog-controller-type.

Thank you very much. I appreciate your offer pjft, I will let you know if I run into any difficulties :)

Thanks, that's exactly what I ended up doing.

I had hesitated with UXS for a while because I never thought I could get it to work.. turns out it was just generating the xml in a directory/folder I wasn't expecting.

Thanks

@blakesha Start a new topic and post details / link to log.

I am not aware of any dependency problems.

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@mitu Thanks so much for that! I got it all working great! Now I just have to figure out how to get the system to work with my Logitech universal remote!

@boxall Right on !Making a backup is always a necessity. I have 5 cards with diff purposes and self made images, would be at a loss if I ever " tweaked" , then messed up and lost what I worked so hard on.

@mitu thank you very much that has done the trick thank you for your help

@jste84 If you are using "lr" emulators - your controllers are already configures for arcade play right now.

I have this problem when I start the basic installation of RetroPie-setup 4.4.1 It will have to install glideN64 myself it's good?

I have some problems with English, so it's pretty complicated when I do google searches. thank you.

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.