ok, thanks

Much obliged, thanks

@columboscoat

Just don't let her hear you say that. She'll have all our nuclear launch codes in a few years time. ;)

Glad you got it working

i have a hunch about the issue, but i can't confirm it. i've logged it with retroarch here:
https://github.com/libretro/RetroArch/issues/4333

and maybe i'll buy a wiimote and sensor bar to test myself. do you know if a generic chinese wiimote will still work on the pi? i guess if they work on a wii they should be understood by the linux driver?

yeah the rpi 3's wifi was initially crappy when it was first launched, until the rpi foundation fixed something in the firmware or raspian. you'll probably find it's good from now on :)

Looks like you are doing it wrong. Try it a different way, one that works

Ok. Well, the SNES emulator should be able to run on a Pi3 easily enough. The best example I can give is Super Mario World Allstars + World. But generally, I imagine that the Pi3 should be able to run the SNES emulator without problems. I wonder if my RaspiATX card that controls the power is draining too much juice from the Pi3 thus reducing performance. Is that a possibility? I do have the switch that controls the pi from the board as an LED switch... ie it uses electricity as well.

@jwilson

Assuming that you were using the 0.78 dat file, it should have been fine. It's a total cop-out suggestion, but you may just want to download the "MAME 2003 Reference Set" and get the ROMs from there.

@BuZz Yep, things are working properly now. If I see any future problems I'll open a new thread. Thanks!

Type "emulationstation" without quotes. This should load ES (RetroPie). Go into the RetroPie config menu on the GUI. Choose RetroPie Setup > Configuration / tools > 002 autostart... choose 1 start ES at boot. Cancel back to GUI, and reboot...

Sorry, I think it's working just fine.

It's just that I thought that because I could access Retropie roms folder via LAN and see all the roms, that meant that they were on the SD card, but what I was actually doing was accesing the USB drive roms folder.

Sorry!

@columboscoat agreed. I would add, although I said above it should be fine (if it can do 2amps and keep voltage at 5.1v), I would still recommend a stronger PSU since you will probably be wanting to use controllers and other devices that require power.

We do not offer support for 3rd party modifications/distributions of RetroPie (As has been pointed out, RetroPie should not be included with commercial products, nor do we know the modifications that have taken place).

You will need to get support from the person/company who sold it to you - or alternatively download an official version of RetroPie from this site, and put it on an sdcard, and we will be able to try and help.

You also need to provide more details as mentioned - which may be clearer once you have installed RetroPie from the install instructions here which explain a lot of the system to you.

Interesting enough. I deleted both configs /opt/retropie/configs/all/retroarch.cfg & /opt/retropie/configs/nes/retroarch.cfg rebooted and reconfigured USB again and went straight to NES game and its working now. It was a last ditch effort and I noticed both had backup configs as well.

Nevermind, it appears the source I was using did not have the latest files.

Apologies, I thought I'd performed a fix that I actually didn't end up performing. I set mupen64plus_audio=0 at /opt/retropie/configs/all/autoconf.cfg, and load state now works. Received the fix from here: https://retropie.org.uk/forum/topic/3897/solved-pi3-retropie-4-0-2-some-n64-games-crash-when-trying-to-load-state-using-any-of-the-mupen64plus-video-plugins/5

Hi there,

Not tried RetroPie with the JustBoom boards yet, although our man Francesco (@GarageTechTweet on Twitter) is working on software tutorials as we speak so I've asked him to add this to the list!

In the meantime though, you should be able to add the following line to the file /boot/config.txt and it should enable the audio card:

dtoverlay=justboom-dac

You may also need to comment out the line following line by adding a # in front of it:

dtparam=audio=on

Let me know if that works?

Thanks

@hansolo77 said in Help Remapping non-LibRetro games/systems:

It sounds like xboxdrv is your favorite.

It is, but I do recognize that it's not a simple thing to jump into. After a cursory look at the different options when I was starting out, xboxdrv seemed to be the most versatile solution. The others seem to lack a valuable feature to me here or there, but they also seem a bit easier to setup and that can of course be a valuable trade-off to many people. I've even noticed a few features from other mappers that don't exist in xboxdrv.

Is it possible to use it just for 1 or 2 systems, or is it a complete replacement to the default xpad driver?

It can indeed be used with one or two systems. When used in conjunction with the xpad driver, the following line would need to be added.

--detach-kernel-driver

As I have never tried this myself, I'll leave the explaination to the xboxdrv manpage entry:

"Detaches the kernel driver that is currently associated with the given device. This is useful when you have the xpad module loaded and want to use xboxdrv without unloading it."

Can you give me some pointers/tips?

Again, I'll be honest. All this is not exactly easy. You may even find out that it's still not the right approach for your particular setup. However, if you find that it does work for you, it becomes pretty easy to configure these mappings over time.

When I started looking into this, there wasn't even an available guide, so I had to pour through the manpage and seek out help on other forums that made similar use of the software. As far as following the guide here on the wiki is concerned. I would recommend reading closely, asking questions and eat it one bite at a time. Any problems that will prevent it from working on your setup will present themselves in the first few steps, so you won't really waste any time.