Wiimote + Dolphinbar should work with RetroArch emulator cores as of the latest releases of RetroPie and RetroArch.

You can look at the instruction section in my project page over on hackaday

https://hackaday.io/project/21553-pi0cket-tiny

The screen I used is a 128*128 screen so yours may be different. There is also the guide in my signature for ili9341 screens, you will see the similarities between the instructions, and get some idea of the wiring

@mitu Coincidentally, I tried stretch with his mame build last week and it ran like dogcrap. I tried a neogeo game and ran at 30% speed.

Facing the same issue with "select" not working. Don't know what "drastic" is, so cannot comment on this.

There seems to be a "fix", but I am not sure whether this is part of 4.3 yet? Anyone has a more recent image and can try? Are their nightly or weekly builds for Retropie?

https://github.com/RetroPie/SDL-mirror/pull/4

Yep, same problem here. Just updated mupen64plus from binaries, no changes. Crashes everyone when trying to load a state... Saving states works though, can see the files in the folder being created, also they have the current timestamp.
Using mupen64plus-gles2n64 btw.
€dit: Loading the savegame seems to work when i'm editing /opt/retropie/configs/all/autoconf.cfg , changing
mupen64plus_audio = "1"
to
mupen64plus_audio = "0"
This though leads to no sound anymore, loading the savegame with the same key combination though works then...

Nevermind. It looks like I'm on Stretch, not Jessie. I guess I'll have to re-install Raspbian yet again...

@herb_fargus

I also can't edit the main spreadsheet for N64:

https://docs.google.com/spreadsheets/d/1Wjzbu90l6eCEW1w6ar9NtfyDBQrSPILQL5MbRSpYSzw/edit#gid=592084905

One issue with giving everyone access to it though is there will always be that one guy who will grief and just delete the entire thing. Of course you can undo what someone else does but it's a pain.

Also, I was just curious. Does Retropie have a Discord?

@linuxpaul it is not our practise to modify system settings. We leave that to the competent (or incompetent) user to mess up ;)

I ended up finding a solution. A fresh image seemed to have solved all the issues. Not entirely sure why, but I think it may have something to do with the way my GPIO pins were set for the Borkin button.

Hate having to start over, but it's nice to be up and operating again!

ok.. i was mainly curious if this was a standard, or decent way of doing things or not... seems a little wonky, but also works. since I do clear cabinets, it can all be seen :)

0_1514490853552_IMG_2445.JPG

Righto - I've gone ahead with a work-around solution. I mapped ESC to both "enable hotkey" and "exit retroarch" so that a single button-press will do both. I don't need the hotkey to do coin-drop, so it's win-win.

Guess I ought to solder some buttons on for those coin drops as well as TAB, huh? Anyhow, case closed!

@gengar103 said in Pi 3 - no HDMI display:

What can be done to get this LCD panel, which worked fine under 3.8.1, to work under 4.3?

Try editing /boot/config.txt and add this hdmi_force_hotplug=1

@AllFather I don't know if it is still an issue but I know Amazon had a very notorious reputation for allowing fake sd cards through. Also , with a USB 3.0 adapter and matching port, the writing to the card should take almost no time at all. Even on a 2.0 port and older card I know a 32gb image will write in 30 min or less. If it is a good card, perhaps it's a corrupted download or extraction?

I know last time I had an issue I re-downloaded the image , was forced to manually deleted the partitions on the card, and created news ones. I only use Samsung Evo cards anymore and they have been beyond phenomenal and the price point is perfect.

@kitchmix Please provide the information it asks for. There is more than one Amiga emulator for example.

@rbaker kool thanks

@mitu I set it up in menu - Start>config controller> hold a to config

If you are used to an OS such as Winodws or Mac, then Linux is a pretty steep learning curve. It took me a few days of reading and getting it wrong and reinstalling Raspbian more than once to work out what was happening. I installed RetroPie from the manual install script a couple of times as well. You won't damage your PI but maybe get frustrated and banging your head against the table trying to work out what won't work and why

There is quite a bit of manual installation even after getting RetroPie up and running. Linux is a good OS but needs a fair bit of user assistance to get it running how YOU want it to run, especially in allowing access to various parts that you normally wouldn't be able to access to give you more control over it

Once it is running, RetroPie is a breeze to use and very simple to add to as and when YOU want to including adding or removing ROMs or emulator systems, unlike Windows that constantly badgers you for yet another security/software update (especially Windows 10 that has taken ALL the control away from the user when updates are needs .... or that Microsoft believe is needed)

Did you read this guide, it helps a LOT

https://github.com/retropie/retropie-setup/wiki/First-Installation

Wait nvm figured out how to edit the key config
/opt/retropie/emulators/pifba
then select fba2x.cfg to edit
Change it too for SNES controller
A_1=1
B_1=2
X_1=0
Y_1=3
L_1=4
R_1=5
START_1=9
SELECT_1=8
#Joystick axis
JA_LR=0
JA_UD=1