Foxbit

> [@FoxbitDreamtail](https://github.com/FoxbitDreamtail) is this still an issue with the latest Box64? I havn't tried it in a long while, I will try it and get back to you.

so, I discovered a new issue but it isn't an issue with Box86/64... it has to do with ProtonUp-Qt expecting Python 3.10 and getting Python 3.11... is there a quick...

USB-Wired Mode does work, however it's a bit of a hassle to set up, First, you have to change the IP of the device you want to use to 127.0.0.1,...

Funny thing. At one point something I did looked like it worked but in reality it just didn't. So basically I tried to, you know, do the responsible thing and...

> Must be your settings then. I was using ALVR wired with the best possible picture quality and latency comparable to VD at 90Hz. Quest 3, near 3K resolution, 750mbps....

> it connects fine if wifi is on on the headset and it actually seems to go wired in that case and doesn't do a fluke connection over wifi. it...

good news! as of the `v21.0.0-dev01+nightly.2024.11.23` build, usb works... although a wifi connection is required for the first-time connection, then it is smooth full-res vr over usb!

> @FoxbitDreamtail have you tried with the integrated support (toggle in the Devices tab)? The other methods will be deprecated after the next stable release sorry, I misunderstood how the...

> Is this still relevant? I know the issue itself got fixed by integrated adb support, but this should also break remote (i.e. separate network) streaming configurations, which we still...

> Obviously, the point is that they might still not be able to discover each other due to limitations from the vpn/bridging solution. So you might have to still manually...