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.

Nevermind.

Is there any you'd recommend? Modmypi.com where I usually buy my Pi stuff only seems to have up to 2.5A.

@Raverrevolution

Did you find a solution for your problem?
I got nearly the same issue: My retropie is built into a controller-case which can be "docked" to a monitor-cabinet with usb audio.
But if I take the controller (including the pi) out of the dock, I want it to play all the sounds over hdmi.

greets bruce

i think i found the solution after a long time of troubleshooting

I forced picodrive emulator and as extra i set the resolution at 640x480 DPK-2 or something instead of default.
no more glitches in the textures!

I'm wondering if there is a way to swap between each shader at runtime. In this way we could match them on the fly..

@BuZz
Worked like a charm!
Thank you

@BuZz Thanks for the tip. I'll post this over there to see if anything positive can come of it. At least replacing a single-board computer is MUCH cheaper than a PC.

Seems I had a problem with permissions, when following the github wiki I was using the mount command with SUDO, and ofcourse the owner/group was root so the user pi couldn't read the mounted dir, the fix was to include the UID and GID for PI in the options during the mount command

sudo mount -t cifs -o domain=workgroup,username=<USERNAME>,password=<PASSWORD>,nounix,noserverino,defaults,users,uid=<LINUX_USERID>,gid=<LINUX_GROUPID> //<HOSTNAME>/ROMSSHARE /home/pi/RetroPie/roms

both LINUX_USERID and LINUX_GROUPID were 1000 in my case.

Hope this helps someone from wasting as much time as I have on this problem.

Ignore that - I misunderstood (And the PS3 controller does work ok in Ubuntu 16.04 unlike I said above - I just had to configure it by holding the playstation button it seemed).

You mean it's fine in ES and games, just no good in the retropie-setup menu ?

It works - it's just it doesn't use the same mapping. Left analog moves, and select will choose an option. This will be resolved at some point in the future, but the menus were never originally designed for navigating via joypad - it was added later via joystick to keyboard mapping. Since it;s mostly configuration and you are on a PC, it's not a big deal to use a keyboard to configure if you don't like the ps3 mapping.

I figured out the sound problem but I still don't know how to boot to ES