@edmaul69 actually i ruled that possibility out, but it seems your guess was partly correct. My RPi2 only need 2A, but i forgot that DAC+ sitting on the PI. So when i removed it i no longer had the issue of ghost input. So thanks for that! I still have some controller issues regarding moonlight, but this is maybe the wrong place to solve them.
Thank you again

@joaobhering If you disable moonlight, do you still get the crash ? Please fill in the info requested in https://retropie.org.uk/forum/topic/3/read-this-first - especially the emulator and game where you get the crash.

@mitu thanks, im try it later)

@zerojay that's a cool idea, I hadn't thought of that angle.

I'm focused on making a single script that does everything i need and adding support for several of the more popular themes.

@mnmagri

I'm not sure how far you got when setting up Moonlight but you need to find your controller's ID number and the correct corresponding button numbers by using jstest /dev/input/js0

Then you add this information into /usr/share/moonlight/gamecontrollerdb.txt

This is because Moonlight decided to use an SDL gamecontrollerdb.txt format to be able to make common game controllers work out-of-the-box. Here's the official template file:
https://github.com/irtimmer/moonlight-embedded/blob/master/gamecontrollerdb.txt

Here is the information for my wireless Xbox 360 controller. Warning: my d-pad settings are not correct and I've been meaning to fix this but I'm too lazy to do it right now!. They differ a little depending if you're using the Xpad driver or the Xboxdrv driver.

Xpad version:

030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,x:b2,y:b3,leftshoulder:b4,rightshoulder:b5,lefttrigger:b6,righttrigger:b7,back:b8,start:b9,guide:b10,leftstick:b11,rightstick:b12,dpleft:b13,dpright:b14,dpup:b15,dpdown:b16,leftx:a0,lefty:a1,rightx:a2,righty:a3,platform:Linux,

Xboxdrv version:

030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux,

More information here (Xbox 360 Wireless Receiver mapping chart):
https://github.com/irtimmer/moonlight-embedded/issues/514#issuecomment-310163270

Hey Poltro,

I just created the script to make things easier to install and setup Moonlight-Embedded. I have just updated this script today BTW to include a new menu based structure for an even easier solution. In regards to the controller mapping, this is now all stored in a txt file within the Moonlight program. It's called gamecontrollerdb.txt and contains the mapping for over 100 different gamepads. Here's what I could see in that file:

xwc,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,

AND

030000005e0400009102000007010000,X360 Wireless Controller,a:b0,b:b1,y:b3,x:b2,start:b7,guide:b8,back:b6,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:b13,dpleft:b11,dpdown:b14,dpright:b12,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,platform:Linux,

If Right Trigger is Start, try changing righttrigger:a5 to righttrigger:b7 and start:b7 to start:a5

Let me know if that fixes it here and also, let everyone know what model your controller is and the model of the receiver as that may offer some clues as to why your mapping is different :)

Latest Video is here btw :

lt.jpg" alt=" " class=" img-fluid img-markdown" />

Well, issue solved. It seems that moonlight was bringing full desktop streaming to rpi, giving those lags. It was too fast so i didn't noticed. Solved by using a .bat file on Windows to force autoplay and no gui:

@ECHO OFF "C:\Program Files (x86)\PCSX2 1.4.0\pcsx2.exe" "D:\Jogos\PS2\gta_vicecity_ps2.iso" --nogui --fullscreen

At the Geforce Experience Tool, click at configurations(little cog at upper right corner), SHIELD menu, Add(Adicionar, Brazilian Portuguese) and point to this bat file and you are good to go. In my case, i have just edited the pcsx2 gamestream entry.

0_1503714691676_shield.PNG

Now, games are running smooth.

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.

I'm running into a similar issue as well. Through searching through the moonlight github it seems the move to SDL2 has caused some issues with RetroPie. The developer of Moonlight has stated that they wont bother with fixing the problem as it comes from the way RetroPie handles controllers using SDL2 framework. Something around how the buttons are mapped and what the system sees. I'd love more help trying to track this down as well.

I've only recently updated my system to the new moonlight-embedded package yet I am having the same error, different controller ID but the same error. I've followed the steps you outlined and cleared the controller configuration but still no dice. Each time I launch moonlight, it finds the controller, yet never loads the correct configuration. Only falls back to the default configuration at the top, which isn't correct. Any help?

I set my desktop to 640x480 and now there is black bars on the left and right. Possibly because ntsc is 720x480? This is better though as the image isn't squished anymore.

EDIT: That did it. 720x480 with a render resolution of 640x480 gives me a full 4:3 picture in moonlight. Cheers.

https://github.com/moonlight-stream/moonlight-docs/wiki/Setup-Guide#using-moonlight-to-stream-your-entire-desktop

Ok so I hooked the pi up to a wired connection this morning. I continued my testing with Fable and was able to play this morning for about an hour with no problems even with Netflix going in another room.

Later tonight I'm going to change the moonlight launcher script I wrote to see how it runs at a full 60fps rather than the 30fps I started testing at.

Over all I'm very impressed with it.