I know this post is a couple months old, but I've just set up moonlight today on my Retro-Pie setup, using the same controller, and ran into a similar (if not the same) issue... But I managed to come up with a solution which (I think) will hopefully help others.

Long story short, I replaced the line matching the controller's ID (030000005e040000dd02000003020000) in /usr/share/moonlight/gamecontrollerdb.txt with this:

030000005e040000dd02000003020000,Microsoft X-Box One pad (Firmware 2015),platform:Linux,x:b2,a:b0,b:b1,y:b3,back:b8,guide:b10,start:b9,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,dpup:h0.1,leftshoulder:b4,lefttrigger:b6,rightshoulder:b5,righttrigger:b7,leftstick:b11,rightstick:b12,leftx:a0,lefty:a1,rightx:a2,righty:a3,

When I start moonlight it outputs an error about the config not being correct now, but it actually works (button mappings matched what Steam/games wanted, with no manual config necessary within steam or games).

I came up with this mapping by running the SDL "controllermap" utility. I compiled it using the steps laid out here

Now it's very possible I did something wrong, but when I ran controllermap, all I got was a blank screen (apparently you're supposed to see prompts asking you to assign/map buttons, but I never saw this). The first time I ran it I just mashed buttons until it exited. What this accomplished was it allowed me to get an idea of what order it took the inputs (based on the order it output them in the configuration string that was output when controllermap exited. Then, using this order as a reference, I ran controllermap again I pressed the buttons/joysticks in the order seen in the configuration string. This time controllermap output the string I included above. Then, as I said, I replaced the existing mapping in moonlight's config file. Then I rebooted (probably unnecessary) and launched moonlight again, and my controller was working.

@ectoone

very strange , would of thought by now it would of been implemented. Sometimes like with the current consoles...I wonder what year I'm in ! lol

@BuZz I have sent you an email regarding the linked website/guide, and the removal of files from both the direct site and parent site, which would contravene the rules of this forum.

I hope you will have time to read.

Thanks :)

@mr-monkeyface Update RetroPie and packages from the RetroPie menu: https://retropie.org.uk/docs/Updating-RetroPie/

@edale

Also, like what Joel from Vinesauce says, never download stuff like "video.avi.exe" (or anything like it for that matter).

Thanks for that, I've tried the standalone and they work fine with no tinkering. I'm trying the high resolution one as default but it looks like I'll probably need to set alternatives for some roms, as they're a bit sluggish. Mario Kart 64 looks and plays really well though!

These docs may be relevant:

https://buildbot.libretro.com/docs/guides/optimal-vsync/ https://buildbot.libretro.com/docs/guides/input-joypad-drivers/ https://buildbot.libretro.com/docs/guides/overrides/

@dankcushions Would the wrong .dat file result in corrupting the game screen/sound? Or could it be that the game.hi file is being loaded in the wrong place

@swk I thought it says it right on the screen while you are doing it. It's also in the documentation that you should read.

hi @H3RBSKI

glad to see you're using Amiberry and I guess WHDLoad packages :) I'll do my best to assist but if you don't mind I'd like to keep things as clean as possible. Hence if we could continue on the following thread that would be great. This is where I gave details and working uae files for many different configurations and games.

Please let's continue here, if you don't mind => Amiberry thread

Then to answer your question, ensure youres_systems.cfg file (look under /home/pi/.emulationstation/) does contain a section about Amiga/Amiberry. Here's an excerpt from mine:

<system> <fullname>Amiga</fullname> <name>amiga</name> <path>/home/pi/RetroPie/roms/amiga</path> <extension>.uae</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ amiga %ROM%</command> <platform>amiga</platform> <theme>amiga</theme> </system>

Also make sure that in your emulators.cfg file (under /opt/retropie/configs/amiga/) the following lines are there:

amiberry = "/opt/retropie/emulators/amiberry/amiberry.sh auto %ROM%" amiberry-a500 = "/opt/retropie/emulators/amiberry/amiberry.sh rp-a500.uae %ROM%" amiberry-a1200 = "/opt/retropie/emulators/amiberry/amiberry.sh rp-a1200.uae %ROM%" default="amiberry"

After making sure both files are ok, reboot the system and Amiga should be there ready for you!

Any other questions please post them on the other thread.
Thanks and happy gaming!

@jonnykesh MMh ok, I guess I'll have to keep it on my system then. Thanks for the advices.

I came across your shader while messing around with settings last night, and I just want to say that you did a phenomenal job. This is the shader I have been looking for and didn't even realize I was looking for it. Finally I can turn off integer scaling and get rid of all that pixel wobble.

I highly advise everyone to give this shader a shot. If you like that "perfect pixel" look but can't stand the artifacts that come with it, this is the shader for you.

@mitu By following the docs in the link I mentioned.

@fenris RetroPie is not supported on any Raspberry PI distro out there - check the docs. For instance, DietPI does not have the graphics stack installed and therefore it's not suited for RetroPie.

I'd advise to start by trying the pre-built images on the RetroPie download page (which are based on Raspbian Jessie Lite image) and see how it performs.

NES games should work fine on a PI Zero-W, but for SNES I'm not so sure - others may chime in.

@jonnykesh so i've been fiddling with them a bit to figure out what the issue could be.

using

aspect_ratio_index = "22" custom_viewport_height = "960" custom_viewport_width = "1280"

just to get the window not to fill the whole screen the problem stays.

0_1507887835357_IMG_1403.JPG