@cyber92 What does 'not working' mean ? What files did you copy and what game are you trying ?

Make sure the .bin filename is correct and corresponds to the name in the .cue file. Linux is case sensitive so make sure it's the same name both for the on-disk .bin file and the file declared in the .cue - see https://retropie.org.uk/docs/PC-Engine/#pc-engine-cd for an example.

@cyber92 Create a new topic, but I suggest searching the forums first for a similar problem and reading the PS1 page in the docs - https://retropie.org.uk/docs/Playstation-1/.

@myquyen1996 https://github.com/RetroPie/RetroPie-Setup/wiki/Stratagus

@sam Setting up RetroPie on a real RPi is easy if you follow the instructions (which you've presumably already looked at when you installed on Ubuntu), and the forums are full of extremely useful information (sometimes better than the documentation :P)

Have realistic expectations tho; while the vast majority of platforms are emulated pretty much flawlessly and PS1 emulation is mostly very good if you overclock your Pi a bit, N64 and Dreamcast are really at the very limit of what can be achieved on the Pi3.

If you're cool with that, and maybe asking a question or two here if/when you get stuck, then in my opinion there's no reason not to get an RPi3.

@rjotter Generally folks here don't like to help those who are using a pre-made SD image as the best source of help tends to the person who setup that image because who knows what they did with all the configs and setup.

BUT... you may need to look into using the xboxdrv?
https://github.com/RetroPie/RetroPie-Setup/wiki/Universal-Controller-Calibration-&-Mapping-Using-xboxdrv

I experimented with it at one point but never got it to solve my input issues. Turns out there were simpler issues at hand.

There is also this: http://blog.petrockblock.com/forums/search/?bbp_search=steam

I wonder if I was able to make a list of the games I need the USA region art for that maybe someone could make me a zip?

@mitu So I'm guessing I need to do a whole new install of retropie and emulation station then?
Thats what I was trying to avoid :(

@mitu perfect, thank you for the reply. I will check out the link and see what I can figure out. The audio devices don't need pins.

Thank you

Did you read the documentation?

@quicksilver perfect thanks.

@Alturis I didn't even think of that! My bad.
The case is 7.6 x 4.51 x 2.95 inches.

If this helps you, then I looked at the review on this site. There are other adapters there, but I'm not sure about them.
https://www.bestadvisor.com/bluetooth-adapters

Here are some handy links found

https://www.raspberrypi.org/forums/viewtopic.php?t=25933 https://raspberrypi.stackexchange.com/questions/46153/detect-hdmi-and-start-gui/46158#46158 (the guide from the Raspberry Pi site) https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

You can start playing with the command and see if you can switch manually between resolutions, on the fly. If this works, then you can incorporate it in a script to be run at boot.

Well after bashing my head against a desk for an hour or so I finally gave up and posted the above, then figured out almost immediately what the problem was.

Appears at some point within FBA i had set up a core override that must have had resolution settings set up,

Deleted the override file and FBA immediately started behaving itself

Update

For anyone else trying this, I tried many different combinations of drivers and commands/scenarios. Including cycling through all the pairing modes. The best I seemed to get it was by pairing it into "Android B" mode, and from emulation station I was able to get it to recognize as a keyboard, but it only recognized a single button. Strange.

Did you setup your retroarch inputs correctly?
Otherwise you can hardcode your buttons in the retroarch script from your emulators.
The Playstation issue could be that the game doesn't work with a analog controller.

@maxbeanz Not without either a change to our dispmanx SDL, or a change to the fuse code. Not sure where the fault is. Or by switching off the dispmanx driver via retropie-setup (which could cause tearing due to vsync differences but will work fine.).

Ok the correct way is:

Turn on setting mode
Do a reset
Go to Setting up the soft dip > Slot 1 Metal Slug> Turn on blood
Navigate back and select exit
It should display DIP SW 1 OFF!!! or so
Then turn off setting mode in rgui

Edit: It should create a .fs file in the romdir.