@Denko please fill out https://retropie.org.uk/forum/topic/3/read-this-first

Welcome to Retropie and to this forum.

Thanks for sharing your solution. It would be nice if you'd edit your opening post and add [Solved] before its title.

Backup the ROMs and BIOS folders, the \\retropie\configs\ folder - the emulationstation folder contains your collections and ES settings/own themes`. Here's a topic discussing this in detail - https://retropie.org.uk/forum/topic/16866/.

The Bluetooth stack stores the all peripheral pairing information in the filesystem (in /var/lib/bluetooth/), so the problem is definitely on the side of your controller, which likely stores the pairing in some kind of battery-backed volatile storage.

My advice: ensure that you don't allow your controllers' batteries to drain completely. Make sure to install the sixaxis package, as this will install install a service that automatically turns off your controller after being idle for 10 minutes (or any user-set time). Without that, your controller will remain paired indefinitely until either the battery is completely dead or you turn off your Pi.

See here (and avoid using the ps3controller driver, as it's only needed for more obscure third-party clones).

@mitu one success for us. The edition on that .cfg worked. One interesting thing I've noticed is: every value was 11 more than normal.
If my select button value is 10, on that .cfg he was 21.
If my B button value is 4, there was 15.

On a side note, I've used @Clyde "mc" tip and man, it saved at least 1h of my time.

Again, guys. Thanks for your time, for your effort, for your attention and for caring and sharing your knowledge with us.
I request now my promotion to Private 1st Class Noob.

Well I am starting to think that this USB audio chip I have is simply not compatible with the Raspberry Pi Zero W. My reasoning:

1 - USB Circuit works fine with Windows Desktop and with Raspberry Pi 2.
2 - USB Circuit not detected through USB Hub on my original Pi Zero W.
3 - Loaded Retropie 4.5.1 on spare SD card and plugged it into spare Pi Zero W. Without modifying config and overlays to run DPI I was able to get wifi working without any trouble.
4 - Using SSH logged into the Pi and then plugged the USB audio circuit directly into USB on Pi Zero W.

USB audio still not detected.

I think I am going to have to look for a different chip.

I do find it curious that it works on a Pi 2 but not a Pi Zero.

Thanks everyone for the help. I will check back in when I have a different chip.

Thanks!
KB

@nemo93 said in [Tutorial] "Almost" perfect amiga emulation - UAE4ARM and WHDLoad images [Amiga]:

All,

I've found an even better method, even simpler. Please have a look at this post:

https://retropie.org.uk/forum/topic/12656/agency-amiberry-whdload-holy-grail

Thanks! This method is simpler and faster but the best thing is all packages being versioned.

@ibonihs You could try increasing the cycles to 20000, 25000 etc.

If this doesn't work then could you post the contents of your config file dosbox-SVN.conf at a site like pastebin.com?

@Clyde thanks for the reply, the 'position 1' I was referring to was the part on jstest where it shows the result for the joystick movement, so basically when I press up I get a result showing 0:-32767.

I think I have it sorted now by downloading the Daphne version from this thread...

sorted!

Yeah. I guess you're right.

Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@oleguer said in Cant load MTV Celebrity Deathmatch on Pcsx-rearmed:

I "read" the game cant load becuase have in the name "deathmatch" Really?? xDD

No, it's not because of the game name. The crash means the ROM is either invalid or not supported by the emulator.

Check if your disc image is correct - the .cue file should contain a reference to the .bin file, from your log it looks like the .cue file might be incorrect ?

That being said, there are a few PS1 games that are not working on pcsx_rearmed - I think this particular game might fall into that category, see this topic.

@ian-rosenberg Don't bump topics for no reason, it's rude.
If you can't figure out how to do things, try to find and example - did you look at the Adafruit's code ?

@mitu I got it... I updated DosBox and it's working good now. Thanks for your input! I always appreciate how fast you reply to these issues.

@elduderino62 You can also check your joystick's buttons and axes with jstest in Retropie. See the Docs on how to use it. You get to the terminal by pressing F4 in Emulation station. From there, you return to ES with the command exit.

Perfect. I never would have found it.

I set the to fast forward parameters to null. It's working as I would like now.

Thanks!

@RonsterMonster There is no official image. At the moment, you can clone the repo, but it's different from what ETA Prime did.

Install raspbian lite. Install Git. Then type: git clone --branch fkms_rpi4 --depth=1 https://github.com/RetroPie/RetroPie-Setup.git
Enable the GL (Fake KMS) driver in raspi-config

If you're not familiar with a manual install, go here: https://github.com/RetroPie/RetroPie-Setup/wiki/Manual-Installation

I'd really hope for test images soon. Basically all the libretro emulators work. The rest are hit or miss.

@mitu Yeah, I saw that as well. But there is a ccd file with the same name besides it and that it does support. So shouldn't it work anyways?