iggy

Sorry for the late reply....I've only had to add the DS4 controllers just once in the DS4 windows application and they stick (even through host PC reboots). ( I automatically launch virtual here and DS4 Windows apps when PC boots). The controller order is pretty much the same.... sometimes I have to reboot the PC but it's not often. The PC recognizes controller slot 1 as my Nvidia remote (xinput device), slot 2 is my first DS4 controller (xinput device), and slot 3 is my second DS4 controller (xinput device. This is the Bluetooth adapter I'm using: https://www.amazon.com/Plugable-Bluetooth-Adapter-Raspberry-Compatible/dp/B009ZIILLI/ref=mp_s_a_1_1_sspa?crid=1JG5P2G4UUJ6D&keywords=plugable+usb+bluetooth+4.0+low+energy+micro+adapter&qid=1554387314&s=gateway&sprefix=pluggabble+usb+&sr=8-1-spons&psc=1 Hope that helps

Unfortunately, to get your wiimote set up to act like a real wiimote in Dolphin, you will need the help of the VirtualHere software. You can still download the software and connect just one USB device (in this case, the dolphin bar).....any more USB connections and you will need to get a license....you don't need to use the Easy Find feature...instead use the reverse connections option in VirtualHere that's installed on your Shield and map to your PC via IP address (as long as you PC doesn't change IP you should be good to go). Let me know if you run into any problems and I can replicate my set up for you. The software does go on sale from time to time....I found it invaluable in my Shield setup and different peripherals I use with Launchbox. Hope that helps!

NP.....when you troubleshoot, try to connect your Shield to your PC and don't connect your controller to your Bluetooth. Then use usbdeview/device manager to see what you have listed under XBox360 Controller for Windows in device manager. Like I mentioned before, you will see one using NVVHCI.....this shouldn't take up a usbslot (at least that I saw in usbdeview). Hope you are able to get it figured out!

How Windows handles the controller GUIDs are a little chaotic sometimes. My initial suggestion is to try a reboot of your PC to see if your controller defaults to Player 1. If I let my controller's bluetooth time out, and I reconnect it again, for some reason the USB slot increases (player 1 become player 2 and player 2 becomes player 3, etc)...its pretty random...in my case, all I need to do is a reboot of my PC to set everything back originally. If that doesn't work, you can use a nifty program called usbdeview to help assist in your troubleshooting and potentially remove old devices. BTW, what emulators are detecting your controller as player 2? In my set up, I actually use a bluetooth adapter and connect a DS4 controller to it instead of connecting to the Shield's bluetooth. Steam is not installed on my Shield or PC....I just rely on nVidia's gamestream service to stream my desktop. When I connect to my Windows PC without a controller and open up device manager, I see a Xbox360 Controller for Windows thats mapped to the Shield (has location NVVHCI Enumerator within its properties....dont disable/uninstall this or your Shield may not connected back up to your PC). When I connect my DS4 controller via bluetooth, I see another instance of Xbox360 Controller for Windows thats mapped to SCP Virtual (its the virtualhere driver). As far as renaming the rxgamepadinput.dll, I renamed not only this file, but the rxgamepadremapping.dll and rxnvgamepad.dll. There are two locations where these files reside (Program Files and Program Files x86). I believe this just disables the nVidia controller from connecting in your stream session I believe. You will need to reboot after renaming the file(s). Hope this helps!

Hi There, So when you connect your XBox Controller to the nVidia Shield and connect to your windows PC, the windows PC should see it as a Xbox360 Controller for Windows. On your Windows PC, are you just sharing out just Bigbox to your nVidia shield? If so, I have had a hard time trying to get some emulators to recognize the controller buttons when launched from Bigbox if Bigbox is the only application shared to your nVidia Shield. Not sure why that was. It was a big issue for me with setting up Taito Type X. So my recommendation is try option 1...if option 1 doesn't work try option 2 will definitely work. Option 1: What I did that initially solved my problem was share out remote desktop (mstsc.exe) instead of just Bigbox. I then have an AutoHotKey script that launches Bigbox automatically when your gamestream session connects. Your Windows PC should pick up your controller as a XBox 360 Controller for Windows in Device Manager. Option 2: However; with the method above, I needed my set up to be a little more versatile....ie for Dolphin, I wanted to use wiimotes as real wiimotes in the emulator (using a Mayflash bar) instead of emulated ones. So what I ultimately have in my setup is this: There is a nifty program that you can install on your nVidia shield and Windows PC called VirtualHere. So with this program, your USB devices that are connected to the nVidia Shield are virtually connected to your Windows PC like they were actually plugged into the PC. If you connect a Bluetooth transceiver to your nVidia Shield, it will show up as if the device is plugged into your Windows PC and you set up your device connections on the Windows PC and not the Shield. If you connect, say a Mayflash bar to your nVidia Shield, it will show up on your Windows PC as if you connected the Mayflash bar physically to your PC. With this set up, Windows will definitely recognize your controller as a Xbox 360 Controller for Windows within Device Manager. Let me know if you have questions on setting this up and I can walk you through this set up.

I have mine set up using a nifty program for USB emulation program called VirtualHere. This program emulates the dolphin bar like it was actually connected to your host PC (I actually went ahead and purchased a full version of the program as I have other use cases; however, you should be able to use the non-full version but I think there were some limitations....can't remember off the top of my head what they were). Using VirtualHere allowed me to use the wiimotes as real remotes within Dolphin. Here are the steps for setting this up: - Plug the dolphin bar into an available usb port on your Shield (dont turn it on just yet) - Install VirtualHere USB Server on your Shield and the VirtualHere client on your host PC - Link up the VirtualHere USB Server on your Shield to the VirtualHere client on the host PC (use the Reverse client option within VirtualHere on the Shield to input the IP address of your host PC...you can't use the Easyfind feature if VirtualHere is not the full version). You may need to enable reverse connections on VirtualHere client on host PC (right click on USB hubs in the software, click on Specify Hubs...click on Advance tab) - Launch your gamestream session (I set up mstsc.exe to my host PC as my executable within gamestream) - Launch Dolphin on your host PC and set your wiimotes up as Real Wii Remotes within the controller settings....also check continuous scanning. Close Dolphin - Turn on your dolphin bar and set to mode 4. You should see drivers installing on your host PC - Sync your wiimotes to your dolphin bar - The next time you launch Dolphin and if your wiimotes are turned on, they should vibrate - Try launching a game and see if controls work etc. Lemme know if you run into any problems. Enjoy!