@mitu Ah - thanks for this. Doesnt look like it is going to implemented any time soon

for me happens the same. what did you made to solve it?

Ok thanks for the reply. I will do that. Thanks

Press Start to open the Emulationstation menu, then use the Input Configuration entry to re-configure your controller.

@mitu oh well, mupen64plus performance is very poor on my pi zero (even overclocked) so I suspect lr-mupen64plus will be even worse so its probably not worth my time to dig to much deeper with it :)

@timmay No idea about that. I love the default theme and have only ever tried a few others before going back to the default one. It has everything I want.

It depends on the keyboard but it is generally the key \ or one of the ones close to Enter.

What settings do you have in the Sound section in Emulationstation ?

Hi,

this is what I've done over Raspbian

git clone --branch fkms_rpi4 --depth=1 --single-branch https://github.com/RetroPie/RetroPie-Setup.git
cd RetroPie-Setup
sudo ./retropie_setup.sh
Perform basic install
After Installation, exit and to start Emulationstation

Note that if you installed the Desktop version of Raspbian you can't launch Emulationstation from it. You have to quit the desktop or set your pi to start under console instead of GUI ( you can set this from raspi-config )

My issue was that the WinSCP wouldn't give me permission to change anything. But that video helped me to gain permission.

I'm still working on my main issue in getting Reicast to work properly. I had the same exactly issue as the ISeeTana and same hardware just the most recent Retropie version. I believe that everybody who has a new version of retropie will experience this issue with Dreamcast. It doesn't seem like it is anything our our end causing the problem.

I will be getting a pre-loadedSD card in the mail today and will check to see if Reicast works properly and the input controls work too.

My apologies, next time I post I'll be sure to put in all that information.

However, on this particular problem, I realized what the issue was... I hate to admit this, but in trying to switch from composite input to RGB, I was selecting the wrong input on my PVM. I actually cannot believe that I was that stupid, hahaha... that was several hours of troubleshooting down the drain because I apparently couldn't be bothered to double-check that I was on the right input!

In any case, thanks for your reply, but I managed to figure my stupidity out on my own!

@grant2258 I have followed this video, but I can't get it to work properly. Maybe it is a version issue (I use a CH-616). When I connect the COIN and COUNTER to the encoder, the voltage is always running. It seems like the contact of the coin module is not potential free. So when I try to use it in retropie, it constanly thinks I am throwing coins in it. Did anyone get this running properly?

@Shira See https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/#configure-fstab-to-automatically-mount-usb-drive for more information about permanent mounts via /etc/fstab.

@mitu oh ok. I will have a look at that when i get a moment.
Thanks

@dankcushions said in Issue with some psx games:

but your log is for tomb raider?

My read is that 'all games from MGS till the end' are not working, hence it's not just a single game.
Otherwise, yes, it looks like a bad disc dump or corrupted file. Try with simple .cue/.bin images that you can validate against redump.org's database.

Looks like the performance is pretty poor, even without sound. What emulators are you running and what resolution are you using ?
Can you run with verbose logging enabled (switch it on in the Runcommand launch menu) and then post the log from /dev/shm/runcommand.log ?

sudo apt-get install ubuntu-desktop

Resolved the issue, and PS2 appears in the EmulationStation frontend.
.bash_history doesn't show any evidence of the desktop environment being removed - by way of shell command.

I got it working!
I previously disabled the runcommand launch menu, so I re-enabled it.
Then, choosing the lowest resolution provided by @quicksilver, it works!

Thank you guys!!

I don't have any issues with Dosbox using the dev branch on a PI4 - did you set any special resolution for it through the Runcommand launch menu ? I just installed it from scratch and it's using the default configuration file installed by the scriptmodule.

Same thing with dosbox-sdl2 - it's working just after installed with the default configuration.