Hey Michael!
I didn't have a use for this software for a while as I was at the time trying to use a DS4 controller directly without adapter which didn't work.
Now I got a different (more traditional you could say) use case for the app, mouse and keyboard, and it works GREAT when it works -it's just AMAZING compared to the smoothing filled mess without VirtualHere- I just have one issue:
My devices show up just fine in Steam Link under the VirtualHere option and everything works great.. until I exit the app and open it a second time.. Nothing shows up in that menu section, as if the peripherals weren't connected. The only workaround I've found after troubleshooting is force stopping VirtualHere and clearing it's data.. After doing that they show up in Steam Link right away on the next start (without starting VirtualHere or anything).. So what gives? As far as I can tell it is independent of the server on PC, as I can see the same behavior without server running on PC (without actually connecting obviously, just that the devices show up in Steam Link on first start after clear and not on following startups).
Cheers!
.
Steam link and virtualhere are meant to run together and stop together so if you stop virtualhere outside of steam it might not work correctly. Is there a reason you stop virtualhere and not steam as well or is that what you are doing?
Actually that (force close
Actually that (force close and clear) was my troubleshooting step which gets VirtualHere working with Steam Link again.. I followed the Steam community FAQ and android server faq steps here, which instruct to allow access and remember, but not open virtualhere automatically... So I think I’m doing things as per instructions. But if I close out Steam Link (as in just hitting home button on remote), when I run Steam Link again VirtualHere sections reports no devices connected. This is when I *don’t* stop VirtualHere manually or even come near the VirtualHere.. if I’m understanding correctly I’m not supposed to be really running VirtualHere, it should all work automagically..
Now that I thought of it (at this very moment), could having network debugging enabled have something to do with it? I leave it on for adb..
workaround... not
I thought I almost found a workaround (since I couldn’t straight up fix things by reinstalling Steam Link app as well), by re-adding the hub with static IP in the PC client, and for good measure doing adding PC ip to Shield in virtualhere as reverse client..
The connection actually sticks / is detected every time now even though the Steam Link interface states no devices.. Sadly, a problem with this workaround I discovered is that if the Shield is restarted, although the hub is detected and connected, it shows up as unlicensed. So I have to go through the original workaround and make sure it shows up in Steam Link on the first startup for it to pick up my license.
(forgot to mention that
(forgot to mention that disabling network debugging didn’t affect anything)
.
OK thanks for all the info. I think its worth trying this outside of steam entirely and ill give you an android key so you can do this...