Oculus Quest working wirelessly with Virtual Desktop! - Two (minor) hiccups to iron out - 1 hiccup SOLVED

  • My goal is to have the Quest work on client locations with Enscape.

    Currently I use an HTC Vive Pro with wireless adaptor. To setup at a client location I have to take my Desktop PC (with Gigabit transmitter for wireless VR), the Vive, the basestations, stands, extension cords etc. Then go through room calibration. The quality is great and for longer (paid) sessions this a good solution. However for some quick demo’s it is just too much hassle.

    The nice thing about the Quest is that is does not need basestations like the Vive. This means I can take my laptop and Quest in one backpack. No stands, extension cords etc. Also the room calibration is very fast.

    I tried ALVR but it was not very smooth and it detected only one controller. Today I tried Virtual Desktop (sideloaded) running from my laptop and the performance is good enough for quick demo’s. It shows both controllers. So this seems a viable option.

    2 issues to ‘solve’.

    1. The trigger button shows the teleport arc but it does not actually teleport. With the HTC Vive pressing the trigger halfway will show the arc after which a full press will do the teleport. I tried to change binding in SteamVR but without succes. Any suggestions would be appreciated.

    2. My current setup uses the home WIFI and has the laptop connected to the router with a UTP cable. I would like to take a trustworthy WIFI connection with me and not be dependent on the client WIFI facilities. Is it possible to connect a WIFI router to the laptop with UTP and then use the WIFI signal for the Quest? Or maybe there are other options. I am no an ICT expert. Any tips would be appreciated.

    @Enscape. Ideally I would like to have a dedicated Quest app which runs from the glasses directly without the need for a fast laptop. Could be a sideloaded version so that you don’t have to go through the Oculus store limitations. I think the glasses are capable enough to handle the detail level of the web standalone. The ability to show roomscale VR on client locations using the Quest would really be a game changer. Can you please look into this? BTW I am aware of the cabled solution Oculus will launch in November but a wireless solution is so much better.

  • That is cool to hear. We are always looking to extending the standalone experience, maybe adding WebVR to the web standalone or building a standalone viewer that may be able to run on android. But for the time being we have nothing interactive that will support the Quest natively.

    You can work with panoramas and combing them together into an "interactive" presentation using one of the many panorama viewers. Here is a blog-post from a while back. This should work with the the Quest, there are a few apps, but I have not tried them yet. The nice thing with panoramas is, you get high end visuals viewable on low end hardware, like your phone.

    For the WiFi, you should be able to buy a rather cheap access point (AP) and connect that to the laptop. You can connect the laptop to the AP and the Quest to the AP's WiFi. You can set that up "at home" and it should just work out of the box at the client's site, since from the laptop's, AP's and Quests point of view they where just powered down and nothing changed. The only problem is that windows does not like to connect to two networks and your laptop will not have any internet wile connected to the AP. (It's possible to configure two networks but it's not trivial and should not be necessary in your case, just unplug the AP if you need it.) The second issue Android devices, like the Quest, don't like WiFi's without any connection to the internet, so you may need to be insistent and remove any networks that do have connection to the internet. (I once had a WiFi camera remote that forced this situation.)

    For the teleport issue. This is unfortunate that the key mapping or trigger is not properly forwarded. I read about the issue with Virtual Desktop and that is why I favor the Rift S, since that is basically the same technology, just tethered to the PC. But there is also the workaround that you can use, either use views to teleport the spectator to predetermined locations or you can double click on the PC screen to teleport the spectator to the given location.

  • annevanzwol

    Changed the title of the thread from “Oculus Quest working wirelessly with Virtual Desktop! - Two (minor) hiccups to iron out” to “Oculus Quest working wirelessly with Virtual Desktop! - Two (minor) hiccups to iron out - 1 hiccup SOLVED”.
  • Happy to report I was able to solve the wifi setup for client locations.

    In first instance I connected a 5Ghz wifi router to the laptop (wired) and then connected the Quest to the wifi signal. This resulted in a good connection between the Quest and the laptop. Unfortunately (as Sean Farrell mentioned above) Virtual Desktop needs an internet connection to startup. After that the connection is only local (confirmed by the creator of VD). This means a cabled internet connection must be available at the client location which is not always the case.

    Today I tested a 5Ghz wifi repeater with an UTP connection. The setup is simple. Laptop wired to the repeater and Quest connected to the 5Ghz outgoing wifi signal. The incoming 2.4Ghz wifi is the hotspot on my iPhone. VD starts up and after that a local fast connection between the laptop and the Quest. Now I can run Enscape in VR on my Quest at client locations (wirelessly) :)

    Now only to solve the key binding issue.

  • Yeah, there is a huge thirst for decent mobile VR. This is why clients pay up to 1000$ PER PROJECT on InsiteVR to get mobile VR.

    If there would be more competition in this space, it would be healthier and way useful for the industry.

    The mobile VR industry is ready for a shakeup.