Just a heads-up: removing xpad might break the controller in emulationstation and elsewhere. In my case, the triggers weren't being properly parsed, and as such they couldn't be properly mapped. Hence, I wasn't able to simply remove said driver. That being said, the original solution by @tuxophil DOES work properly, and as such I would still recommend it. Keep in mind, though, that the command at step "8" requires a declaration about which controller you want to map. As such, a correct command might be ./controllermap 0 >> ~/my360.txt, if your X360 gamepad is in slot 0. Running just ./controllermap will show which controllers are connected, so use your gamepad's slot from that list.

I meant to send a PR myself, but looks like the Github's web interface didn't go through with it. I've amended their Wiki page with the command line options and sent a small PR to fix the sample .conf from the repository.

No, there isn't one included in RetroPie, only the 'embedded' variant is included.
You can install one of the releases for Moonlight-Qt since it provides packages for Linux which should work on Ubuntu/Debian.

@mitu
Guess I'll just live without packages, thanks man.

Edit:
I got it to work, I managed to install Kodi and steamlink!

You were right it was something with the DNS settings, I changed it to 8.8.8.8 using this guide through terminal and it just immediately worked.

In RetroPie, the moonlight-embedded variant is used and it's installable only for ARM boards (Raspberry Pi in general). While it has more features, the -qt variant might not offer many advantages for Pi users.

Did you test it on a Pi ? Does it work better than the -embedded version ?

@mitu

OK, finally figured it out!

https://stackoverflow.com/questions/25149143/linux-kernel-consoleblank-argument-ignored

Needed to add export QT_QPA_PRESERVE_CONSOLE_STATE=1 to the autostart file. It seems the consoleblank=0 gets overriden by Qt applications. Seems like a bit of an undesirable behaviour but glad it works now.

Solution: Posting this in case someone else runs into this problem.
Apparently the simple explanation is that Moonlight can only read one configuration file. So the solution was

copy the controller config strings of both controllers into one single .map file. in the global.conf set both controllers to use the same .map file (where all controller mappings are stored)

So my global.conf now looks like this:

# global config file for moonlight input = /dev/input/event0 mapping = /home/pi/msigc302.map input = /dev/input/event1 mapping = /home/pi/msigc302.map quitappafter = true

I have opened an issue at github and they solved the problem. It was an issue in a mapping file. Update is online and it fixwa the problem.

@tygron

I can't help you with th ip issue but I can help you with the audio. I took me hours to figure it out. Add this to the moonlight config file:

audio = local

Then the audio will come out of the raspberry pis audio jack.

@mitu I had a look at the configuration/tool menu and found an option over there to generate the steam list of games. Thank you so much!

I would definitely like to see this option come to EmulationStation, since I have several items I would want to move out of ports into their own separate items on the carousel.

@Zangdaarr said in Retro Moonlight setup is now fixed: Stream your desktop games using retropie:

Retro Moonlight

Does this solve anything that RetroPie's built in scriptmodule doesn't already (https://retropie.org.uk/forum/topic/19872/moonlight-request-for-comments-and-testing)?

This would explain a lot. Since it seems only a software issue, let's hope for the near future.

Thank you very much!

Got it resolved by editing /etc/modprobe.d/xpad.conf and changing triggers_to_buttons to 0

@mcorcoran
I wonder if it has something to do with GFE version because you're having to use "-unsupported". Do you have the newest version of the GeForce Experience installed on your Windows PC?

Also, you might have just typed it wrong in the post but "-localaudio" is just one word without spaces. I remember one time I was having trouble with resolutions and I discovered I was spelling "width" wrong.

Another thing you can try is putting the "-width 720 -height 480" before the "-unsupported" in that command. If you could get it working without "-unsupported" by updating GFE, that would probably be better.

Last, you might also experiment with the refresh rates by adding either "-fps 60" or "-fps 30". What refresh rate is your Windows PC when you manually set it to 720x480? That would be the refresh rate you should try first.

Has anyone had any issues with audio?

My audio seems to work on launch of steamlink. Then stops suddenly during a game.

It seems to mute the volume during the game. Easy enough to put back on the laptop... But can't seem to do it in game? Can anyone help?

Small supplement:

I updated steam-link with the experimental packages. Before, I added the PR from @psyke83 in scriptmodules/ports/steamlink.sh.

Now, I was able to play the dolphin-emulator mith my xbox-360 controller:

I opened steam on the host-pc I started steam-link in retropie I switched on Settings/Streaming/Advanced Options/Start Streaming desktop and then I started Now I was able to configure the controls within dolphin. I also made a combined hotkey to exit dolphin (In my case the Start and SELECT Button). Switched off Confirm On Stop and Render To Main Window on within the dolphin-emulator Switched off Settings/Streaming/Advanced Options/Start Streaming desktop Restarted steam-link and it worked

I also installed steam-devices on the Raspberry Pi too, but I don't know if it makes any differences. If I want to play a game with a keyboard, I have to plug off the controller before starting steam-link.