Will 0.7.0 cause compatibility issues with WebVR/Three.js? — Oculus
Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

Will 0.7.0 cause compatibility issues with WebVR/Three.js?

Hi all,

I'm working on a WebVR application using Three.js (among others). To see my application I have to set up the Rift in Extended mode.

How is this going to work with Oculus PC SDK 0.7.0 with the removal of the Extended Mode?
Is upgrading to version 0.7.0 going to cause issues in my WebVR/Three.js application?

Thanks!

Comments

  • cyberealitycybereality Posts: 26,156 Oculus Staff
    With 0.7 moving forward, all apps will need to support Direct Mode. Extended Mode will not be an option. Sorry.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • brianpeirisbrianpeiris Posts: 17
    NerveGear
    This was discussed on the /r/oculus and /r/webvr subreddits. There is no indication that 0.7, or Direct Mode in general, will be a problem for WebVR. The Chrome builds have already supported Direct Mode for a while now. I don't think you need to be concerned, just wait for the browser devs to catch up.
Sign In or Register to comment.