I'm not familiar with any electronics terms, so all I can say that I did connect the blue wire to the top connector and the white wire to the middle one (of the three connectors facing right on the picture). All I know is that this works. :)

@royal-lizalfos you've provided no useful information in order for people to troubleshoot your issue.

Read the read me first page and fill it out in order for people to help solve your problem

@buzz The main reason I wasn't using the official image is so that I can use the box for multiple purposes--I can launch mate desktop with startx or launch retropie after I've logged in. I'm building a palmtop/portable emulator. If it's pretty easy to set up the official image to do so, maybe I will just use the image--sure beats installing and compiling all the packages.

@mitu 0_1517607033957_upwrk.png

@glitchyboyhunter I didn't give you any 'codes', just pointed you to the file where Emulationstation might log any errors.
You just need to get the file from the Pi - you use a PC if you have one connected. You need to open the \\retropie\configs\all\emulationstation folder in Windows Explorer and you'll file the file I pointed out earlier in that folder. Upload the contents to pastebin.com and get the link here in the forum so we can better log at the log.

EDIT: Make sure that Emulationstation is not configured with Parse Gamelists only set to On (https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#why-does-shut-down-and-reboot-take-ages), otherwise any new game/rom added will not be shown. If you do, then turn it off, then restart Emulationstation.

@dankcushions Could I maybe have to delete the driver for the keyboard and re-add it? If so do you know where the config is for the keyboard?

many thanks by the way. There was a guy on youtube taking about you Floob and he had nothing but the best to say about you JS

;)

@dankcushions said in Weird issues regarding retropie-setup and mupen64plus.:

@r4l

get rid of the overclock. any stability/freezing problems = get rid of the overclock

i don't know why you're editing files. mupen64plus should get automatically configured when you configure your controller in ES. if you're using a proper n64 controller you may need to do some manual tweaks after that to get the c-buttons working nicely, but i would take one step at a time.

Do you know how buttons are mapped in mupen64plus? They are automatically configured, often times the WRONG way. You have to turn off hotkeys in autoconf.cfg and make controllers fully manual in mupen64plus.cfg. Then you have to set the right button mappings in InputAutoCfg.ini. Basically I set up the controls in ES, then I fix them in InputAutoCfg.ini because if I don't, they are totally wrong.

As for the overclock, I am using a Mackertop 5.25v 3a PSU. Even at 1.4GHz, the system is totally stable. Everything else works fine, except N64. I guess I could try going to 1.3GHz and seeing what happens, but I don't think that's the problem.

UPDATE: Added a power conditioner between the outlet and the RPi3. This morning marks the longest running setup so far. Even if it has only been a few hours. Not ready to celebrate just yet... but what a wild ride this has been.

@kevinshope You could disable the onboard Wifi from the rpi-config utility, reboot and then re-configure to make sure that it's the Wifi dongle that's getting used all the time.

Hi,

I had RetroPie running on Mint for a short time and I didn't need to mess with the fullscreen options. All I did was add a startup delay of 3 seconds to the RetroPie entry. This stopped the issue. I would leave it as fullscreen and try that? I think this happens because if ES starts before X is running it doesn't launch. Not sure though but a slight delay should resolve.

@billyh Try it first. I have two PS3 controllers (original) and RPi3 and it works good for me. Played for like 2 hours straight with my brother without any issues.

There is other issue with PS3 controller though - if I let it idle for a few minutes, the daemon (service) responsible for connecting with the controller hangs and I canßt get it back to working condition (I may be able through command line or SSH, haven't tried though). From what I read this issue gets resolved by using USB BT dongle...

@hbornstein You need to read the instructions. If it is not working - your emulator / rom pairing is incorrect as stated above.

@rdelaura Did you re-configure your input in Emulationstation after you paired them ?

I have found a solution. simply install 4.0 rather than 4.3 and update the setup software on the pi after first boot

For anyone else that is having this issue i have discovered the solution.
install retropie 4.0 rather than 4.3 and simply update the setup software from on the pi rather than when mounting the micro sd card.

@mitu Thanks so much! Everything is working now!

I did a little edit. Seems to be an issue with the 8bitdo FC30 Arcade Stick in bluetooth mode - but not in USB mode.

@spudsmctoole mame4all is not a libretro emulator.

Sorry for necropost, but it is on-topic.

I suppose you are running RetroPie on RaspberryPi. If you do, you should be able to overcome the issue by using symbolic link (command named "ln" with parameter -s). You enter the folder with the savegame in command line via ie: "cd /home/pi/RetroPie/roms/psx" and then you make the symbolic link via ie: "ln -s gt2_(simulation).srm gt2_(arcade).srm" The first one should be the already existing file and the second one should be the name of the link. After that the gt2_(arcade).srm points to the gt2_(simulation).srm and that means whatever disc you load both of them would actually load the same file.

Before trying, make backup of the .srm file!

@dudleydes windows 95 is hard as hell to get working at all on the pi and games are slow as crap and virtual drive doesnt work. Dont think 98 can run at all on the pi.