@Retribution Please add more details about your setup, as requested in https://retropie.org.uk/forum/topic/3/read-this-first. What method are you using to run your ROMs from the disc ?

@blujumanji when I recently loaded a new retropie image I was really confused because I had the same bios files on my older image and suddenly with the new image the PSX ROMS wouldn’t load. Oddly once I updated the lr-pscx-rearmed emulator from binary it suddenly worked with no other changes. I had thought that wouldn’t be necessary to update because I had just downloaded the “brand new” retropie 4.4 image and the PSX emulator is part of the image so I figured it would be “up to date.” But apparently that is not the case. So maybe try putting both bios folders in again and updating the emulator (go to retropie setup, manage packages, I think lr- psx rearmed is under either main or optional, and then update, update from binary) and see if that works.

@chubsta You should give Skyscraper a try - it's part of the RetroPie script, just like Steven Selph's scraper - https://retropie.org.uk/docs/Scraper/#lars-muldjords-skyscraper.

@MajorDangerNine Thanks - I'll check it out.

@StuMcBill Well, if it's a controller problem (the 8Bitdo) and the timeout comes from it, try pairing it with a different 'mode' (it supports Android/PC/Switch/Mac ?). There was a topic a while ago from people testing various modes and the problems each one has.
I'd try using a different mode to pair the controller (PC/Switch) - remove the current pairing mode and try re-pair while starting the controller in a different connection mode.

Anyone! I’m really desperate to fix this.

I also have the same condition with the Pi 3B+ and NESPi+ case running most recent RetroPie 4.4 release. It seems to happen with all wireless dongles connected in to the NESPi case ports (wireless Keyboard, and Xbox 360 adapter for sure). I found a couple different threads in the forum about it and I believe they found the reason, https://github.com/raspberrypi/linux/issues/2408, and I believe they were working on a fix, but I have not seen the true fix anywhere.
(If anyone has it and a step-by-step, I'd be grateful)

**I did find a temporary workaround though, without having to revert to previous Pi versions-
Use another USB hub (like a laptop 4-port) to connect to the NESPi case, and then connect your devices in to that. It appears to cancel out whatever mismatch there is between the pi and NESPi USB hub.

It's a bit unsightful but it prevents a lot of re-imaging and reversion to a previous release. Hopefully a solution will be embedded in to the next release as the NESPi case is great!

*I have been successful using either an Insignia 4 port USB2.0 Hub (N5-PCH5420) and also with a Sabrent 4 port USB3.0 Hub (HB-MNBW). Not sure if a powered USB hub will do the same but worth a try before frustrating yourself to no avail looking for a solution.

My devices connected were a Microsoft Xbox 360 Wireless adapter, and Logitech K400r wireless USB keyboard.

Good luck out there..

@noobsaibot It depends, you still haven't provided any info about your system.

@dudleydes Thx!

@hazeldig said in Problem with SSF2.ZIP (works from RA, not from ES):

I noticed that FBA 2012 runs SSF2.ZIP flawlessly, but opening it from the EmulationStation on my Pi 3B+

Stating the fact : using fba2012 on a rpi3b+ is stupidity born of lazyness.

@dankcushions sorry, I thought the rules said to include a link to a tutorial if I followed one, the one I followed for setting up the initial keyboard layout was just from that video. The real issue is that I believe there is some configuration issue that I cannot figure out. I have read the docs and tried to find the answer. I suspect that what is happening is that the initial "keyboard configuration" is what is being used to navigate the menúes for all of the consoles (mame, atari, snes) and it is not until I am actually I the game that the system specific configuration takes over.

If this is the case, then I believe that my setting the "hot key" (I am not really sure what this key is supposed to do) to the same utton as the "start" key, in the initial keyboard configuration, is what was preventing me from getting into the different arcade systems (except mame). However, I went into the global config file and changed and changed the "hotkey" value to a different button, but selecting the "start" button still does not get me into the atari emulator.

@pfoff The error is a very generic one and it's unlikely it's something related to SDL, looks like there's a problem with your system. Check dmesg for any related errors - especially hardware ones.
With only 2Gb or RAM, you'd better off using the 32bit version of the OS, you won't gain very much with a 64 bit system. Also, on PC all packages are built from source, so there's no need to re-compile manually any package.

Tested the srm save on my end as well and can confirm it works so it is definitely something wrong with the save states causing an issue in the game. Sucks losing the option to use save states but at least I can play through the game again.

Thank you all for your help.

edit: still happening after I open the retroarch menu to toggle cheats or something, have some ideas I will test and post my findings later

@Everett1954 I was able to get about half the Creativision games working with Advmess. However, I wasn't happy with the results because I couldn't get Planet Defender to work. I wound up manually installing the creatiVision Emulator (Linux Source dated 24 April 2016) (source file: creatiVision-1604240src.7z) from this website: https://sourceforge.net/projects/creativisionemulator/ This emulator uses SDL.

Having unzipped the files into a new build folder, I compiled it with cmake /home/pi/build(using GNU 4.9.2 on my Pi) and make. Once the executable creatiVision file was created, I then set up a layout etc.

All of the games seem to work and appear to work at full speed.

Your mileage might vary. I did this more than a year ago on Jessie, and I'm using Attract Mode, rather than emulationstation, and I also use xboxdrv for controls.

Also my emulators.cfg looks like this:

default = "creatiVision" creatiVision = "/opt/retropie/emulators/creativision/creatiVision -r %ROM% -b /home/pi/RetroPie/roms/crvision2/bioscv.rom -f"

Note the reference to the bios file bioscv.rom.

You may need to adapt the emulators.cfg for emulationstation, but I can't help you there.

@Heartless I'm not overly familiar with their development, and someone correct me if I'm wrong, but I believe the latest version of either runs worse on the Raspberry Pi.

@mitu Alright! Then I will wait until the Scraper problem is fixed. The autostart is already implemented in the retropie programm. Just need to go to the retropie setup and set the autostart option to enable.

My Retropie is now starting automatically. When I quit Retropie, I have my normal Ubuntu Desktop.

Anyways, thanks for the help! I am done for now.

@chubsta Welcome.

It sounds like you'll be able to handle things well.

Message me back if you have any issues. My updates to the setup guide have been somewhat haphazard, but I'm pretty sure everything is right.

I got it to work using 'screen'

sudo apt-get install screen

$ screen -d -m emulationstation

I actually just did something similiar which worked perfectly. I just took an in game video clip with my phone. I installed the Pixel environment. I uploaded it to youtube. Then used youtube2mp3 to convert it to an mp4. I downloaded it to the pi via Pixel. renamed it to the game name-video.mp4. Placed it in the images folder. Then i rebooted and selected the game and edited the meta data with the file path under video. Then saved and exited. Works perfectly. Now i can do that on the other 3 games i do not have videos for and the ones that wont play and i should be golden.