After tinkering for over 2 hours last night, I couldn't get VirtualHere to play nice with my Shield Pro and Windows 11 PC. I've bought the license, of course. (And have tried to refund it, because of this, haha).
The following happens on my Shield Pro:
- The 8BitDo USB adapter seems to connect to either the VirtualHere server or the Shield Pro itself. Sometimes, I can navigate the menus with my controller. That shouldn't be possible, right? As a test, I've connected the same gear to my Pixel 4a, and I can only use the online gamepad testers in browsers then (on PC) to see my controller respond.
- Moonlight was also being a hassle last night, but on my phone I seem to have figured it out. Would love to hear from you guys if this is correct: whenever I enable one of the two controller drivers, Moonlight asks for control of the USB device. I should say no, right? Or just disable the two drivers? The last one seems best, since my Pixel 4a has input in the game then, via my PC. I know this, because the rumble via Moonlight is laggy and way too strong. By connecting via my PC, it's exactly how I want it to be.
- I put the server on my Pixel 4a on "Keep awake" as a test. Is this an important setting? On my Shield Pro, input never works or stops working quickly. Is it because the server gets disabled or goes in a power saving mode without that specific option?
After work, I'll try the following, and please tell me if anything is wrong what that path: install VirtualHere on my Shield Pro again, tick the boot option and "Keep awake". Afterwards, add the license again to my PC, since I've reset the settings again. Click auto-use on my 8BitDo there. (The program is already in the startup folder, so should be ready to go whenever, right?). Then everything should already be good to go right? Connect my controller, see my input appear on a gamepad tester website. Afterwards, disable all controller drivers on Moonlight, and it should still function thanks to VirtualHere. Am I missing something? I think that's how I got it to work on my Pixel 4a.