I apologize if this is documented somewhere and I'm just missing it, but I'm having some troubles getting VH working nicely with a wireless xbox one controller through gamestream and the steam link app on the nvidia shield.
1. I installed the virtualhere server on the shield.
2. I plugged in the controller wireless dongle into the shield and paired it with the controller (and accepted the prompts that requested VH access to the usb device)
3. I ran the VH client (downloaded from this website) on my desktop.
4. From the windows 10 controller test screen, verified that windows was receiving controller inputs from the xbox. I was able to see all axes moving, and exercised all buttons. So far so good!
5a. Started a game (ffxv) through steam link. The game starts up but the controller inputs seem to be completely ignored. Exited the game using the shield controller
5b. Started steam link from the shield app menu. From within steam link, I selected the virtualhere configuration option and selected the pass through option for XBOX ACC (or whatever the device was called). I then connected to my computer using steam link, and again none of the controller buttons did anything. I was unable to navigate any menus with the xbox controller, nor was I able to see the xbox one controller from the controller configurator in steam.
Am I missing a step somewhere? The shield controller works fine(-ish, the analogue sticks are garbage and drifty, hence my trying to use other options), and if I plug an old wired xbox 360 controller directly into the shield without virtualhere that works fine in all use cases. For some reason though, even though I've verified that controller inputs are being passed through to windows, the wireless/VH controller does not seem to work in gamestream games or steam link.
Thanks!
.
Actually it sounds like virtualhere is passing through the xbox controller fine if windows "joystick.cpl" shows it working ok. That means it must be something in the steam client that is messing it up. Can you just use remote desktop instead and run the game that way and bypass steam?
Whoops, it looks like I
Whoops, it looks like I included a typo (I blame posting while tired). In step 5a, FFXV was started through GAMESTREAM, not steam link.
I'll give the virtual desktop a shot when I get home later, but do you have any insight as to why gamestream might also be temperamental here?
Of note, I also tried starting Borderlands 2 directly on the computer using steam last night, and was unable to get any inputs from the controller connected through virtualhere in that. If I plug in an xbox 360 controller directly to the computer controller inputs work fine, and the xbox one controller also works fine if I plug the wireless dongle directly into the PC.
update
virtual desktop (adding mstsc to gamestream" appears to work without issue, so I guess this means that steam is malfunctioning (I guess ffxv is impacted even when launched via gamestream since I installed it via steam?)
How would you recommend troubleshooting the issue with steam not detecting the controller? Unfortunately that's like 99.9% of my use case here.
.
Im not sure sorry, the only thing i generally recommend is to switch to the steam beta client and then send valve feedback about that bug and hopefully they fix it..