@top-specci a pi 2 image will work on a 3b+ as long as it's an image based on raspbian stretch. If it's an older retropie version then it will not work on the 3b+.

Simple comment. I had the same issue but my lowerBound had to be fix to value 490. It's important to check the value when your stick go back in place. My left stick showed a value of 491 when It came back from left to center. Now, Everything's working fine

I suggest to use joy.cpl to find It.

https://www.pjrc.com/teensy/td_joystick.html

Yes, it looks like a bug in the emulator (mame2003) - though it says it saves/loads the state, this is not correct.
What you can do is use lr-fbneo for this game, the ROM is compatible and save states are supported and work.

Then unfortunately my DS3 works in PCSX as classic controller, no matter how type of device I'll set. :( Many thanks for answers, all issues, but this one, your advices helped me to resolve, even a lack of scrapping covers. :)

@mitu I will try that when I have time

Retroflag cases aren't compatible with the RPI4B but I would like to hear of someone who managed to make it work. I'm also interested if someone has integrated an RTC hat to fit in one of these cases.

@jimmyjudd Hi Jimmy, do you know how to do manual splash installs? If so, could you point me in the right direction?

Thanks.

I did that and apparently that's all I needed!

@mitu Thanks a lot!!! I changed the hostname and all cores are installed correctly

My workaround is changing it to "2000" and counting when on that screen. (shrug)

Try editing the mappings file directly, swapping the x or y axis or adding the inverted variable if needed.
Last i checked they were here

/home/$USER/.config/reicast/
or samba here
samba:\\ipaddress\configs\dreamcast\mappings\

@sdabbs
I don't know sorry. Try using pip to check and upgrade py modules.

pip list pip upgrade xxx.xxx

@misterbo42 said in Black screen after few minutes of gaming:

I don’t know where I can find a log of these errors but if someone can tell me I would look at it.

The runtime log is usually in /dev/shm/runcommand.log. You can also try running dmesg from the command line after this happens to see if any warning/errors are shown in the system log.

Can you give more details - as asked in https://retropie.org.uk/forum/topic/3/read-this-first ? Which emulator, what RetroPie version (don't say latest), how did you install it, etc.

Does it happen for all games or just for a particular game/system ? Did you overclock your PI ?

Amazing! This did the job!

I believe that is a Windows only device

@v-roshpi Contact the seller ? You can download RetroPie from our site, and try and get that to work but you will need to contact them for configuration unless you know what it's using to interface etc

@TANKARD @mitu

Custom configs for CRT using the built-in composite out

You can also tweak the runahead settings for 8bit/16bit consoles to further improve the input lag and use wired controllers.

You can check using the jstest utility if the buttons are registering correctly in Linux, outside or RetroPie. Attach a keyboard and exit Emulationstation (F4), then run from the command line:

jstest /dev/input/js0

It will show you the gamepad buttons/joysticks and you can press them one by one to see if the input values change on the screen. You can exit the test by pressing Ctrl + C.

If there is no reaction when pressing a button, either the wiring is faulty or the controller.
You can also try connecting the encoder to a PC and test it there also.

@BuZz my bad. I’ll update my post or create a new one with the relevant information.

Thanks, this was the file I'm looking for ...