New version of Enscape doesn't work with Oculus

  • Why does this happen? We had to revert back to Enscape-3.1.2+55592 to get our Oculus to work in VR mode. All the newer versions make you jump through a ton of hoops and install unnecessary software. How does this happen? All of our other VR software options work fine in their new versions, but Enscape. Enscape-3.1.2+55592, I plug in the VR headset and launch the Oculus software and poof, it is working great.

  • Why does this happen? We had to revert back to Enscape-3.1.2+55592 to get our Oculus to work in VR mode. All the newer versions make you jump through a ton of hoops and install unnecessary software. How does this happen? All of our other VR software options work fine in their new versions, but Enscape. Enscape-3.1.2+55592, I plug in the VR headset and launch the Oculus software and poof, it is working great.

    Can you please let me know which Oculus device you are using exactly?


    Also, with current releases (and Oculus headsets) you will have to additionally install Steam + SteamVR, but that shouldn't be a detriment to the performance - After setting everything up once, it also shouldn't take much longer than you're used to. While we currently rely on that system we still want to improve the ease of use in the future as well (Since the Quest 2 for example isn't officially supported yet).


    But in any case, even using the two additional software solutions (which are intertwined as well) shouldn't interfere with your workflow.

  • We are using the Oculus Quest and the Oculus Quest 2. Both preform great with the older version of Enscape, but with the newer versions not so much. We are using the Rift cable to the computer.


    Steam and Steam VR are not something a lot of companies allow to be installed. Plus have the accounts for them to manage. What would change and why make things so difficult? Really like the Enscape experience but sending the VR files to clients and having to explain to them Install steam, wait also install SteamVR is just way too much to explain and expect of a client to do. Someone or something changed the way Enscape made things easy and user friendly over the last few versions.


    Twinmotion, Lumion are two others we use and Steam and SteamVR are not needed and jump right into VR mode. Twinmotion's EXE file is almost as easy as Enscapes use to be. They don't package everything into one compact file. So explaining to clients to unzip into a folder is sometimes a bit confusing for some.


    Thanks

  • Hi there - I too am desperately looking for a simple solution here.

    We have a Rift that has worked well enough over the years, but they are phased out.

    Our client wants to buy a rig - soup-to-nuts, computer and everything. But agreed, we can't be managing all of this STEAM business.

    What is the most sure-fire set up right now? I worry the Quest Pro + new computer with 3080 graphics card is going to be a big investment for so much complication. I've yet to hear of anyone on the forum (or internet) successfully and easily using a Quest Pro with Enscape, period.

    Any thoughts?

  • We are using the Oculus Quest and the Oculus Quest 2. Both preform great with the older version of Enscape, but with the newer versions not so much. Steam and Steam VR are not something a lot of companies allow to be installed.... but sending the VR files to clients and having to explain to them Install steam, wait also install SteamVR is just way too much to explain and expect of a client to do....


    Twinmotion, Lumion are two others we use and Steam and SteamVR are not needed and jump right into VR mode. Twinmotion's EXE file is almost as easy as Enscapes use to be. They don't package everything into one compact file. So explaining to clients to unzip into a folder is sometimes a bit confusing for some.

    I've not tried Twinmotion/Lumion VR lately, but if you are using them with Oculus, then you have the Oculus software installed, correct? So there is still another layer of software and account management involved, it's just not Steam. Within the Oculus ecosystem, Enscape works with Oculus Rift S, with no Steam required. But it still requires the Oculus software. The issue with the Quest + Enscape is that you need both Steam and Oculus, but I'm not sure how/why there would be a difference between Enscape 3.1 and 3.4 in that regard.


    We pretty much ditched the Oculus when they started requiring a Facebook login. Now that is a problem in a business environment. Or telling a client they have to log into Facebook to use VR? Fortunately, Oculus has backtracked to just needing a Meta account but the whole Facebook connection still leaves a bad taste. Any client that has a VR headset will be familiar with Steam and/or Oculus, there should be no explaining needed.

    Our client wants to buy a rig - soup-to-nuts, computer and everything. But agreed, we can't be managing all of this STEAM business.

    What is the most sure-fire set up right now?

    The most hassle-free solution and easiest setup would be a lightly used Rift S on eBay. The Quest/Quest Pro is a pain to deal with the Link cable setup and reliability imho. I also found colors to be oddly washed out/low contrast on the Pro with Enscape. Which is a shame because it looks stellar otherwise.


    The next most hassle-free would be the Valve Index. Yes it will need Steam, but that's all. There has to be -something- running the drivers behind the scenes. Other options (Vive, Windows Mixed Reality) require their own software running in addition to Steam, like the Quest situation w/Enscape.


    And yes, getting Steam installed in a corporate environment can be a hassle since it falls under the "gaming" umbrella. It is frustrating that no one lets you just install a driver package without their whole interface/overlay, but that's the state of things currently.

  • IME gave up on Vive and Mixed Reality for the reasons listed above. Too many software layers. Too much tweaking. If the computer went to sleep I had to reboot to get them to work again.


    Rift series was a joy. Only needed Oculus software. No Steam, etc. plus more software for the headset.


    Rift was stable and simple.


    I hope Oculus only requires it's own software in the future to use w Enscape. No Steam, etc...

  • Caddman13 , I appreciate the response.


    I wanted to hereby also inform everyone here that our latest preview which is gonna be released very soon will remove the requirement for Steam + SteamVR when using the Quest or Quest 2 - You will be able to only have the Oculus app running and make use of Enscape. This will just be added into our preview so far, but you may still want to give it a shot.


    Otherwise we'll of course also include this in our full release of 3.5. I'll add another update here once the preview is out.

  • This is great to hear!

    Have you tried with Quest Pro vs Quest 2

    I am trying to gauge what (if any) benefits there are to Quest Pro over Quest 2.

    I was disappointed in the original Quest as we didn't really understand that it would only be useful as a VR photosphere viewer. That navigation of a VR model was not possible. But it served it's purpose.

    With Quest 2 (tethered) can you navigate a model, like you can with a Rift / Rift S?

    Thanks again for finding a way past the Steam + Steam VR. Sounds like it's almost ready for Clients to pick up.

  • Architecture Outfit , while we haven't had the chance to try Enscape with the Quest Pro, especially since we do not offer complete official support for any Quest device yet, it should still work but we cannot make any definite promises. The Quest 2 on the other hand has already lots of reviews here in this Forum alone and seems to be working just as it should.


    Further to answer your second question, with both Quest 1/2 (potentially the Pro too) as long as it's tethered to your main machine that supports Enscape either wired or wireless you can navigate the scene fully using the controllers as well.


    I hope that helps!

  • The latest preview 12 of Enscape has just been released:

    Enscape 3.5 Preview 12


    Excerpt of interest among other additions in Preview 12:

    "VR Improvements


    We’ve improved our VR implementation for a smoother head-tracking experience and removed the SteamVR requirement for Oculus (Quest) usage."


    Let us know in case you run into any issues or of course if you wish to share any feedback with us.

  • Technically speaking - since it's running the same software, and using the computer for processing - is there any reason the Quest Pro would be better than the Quest 2? I guess it comes down to screen resolution if refresh rate and processing is all handled by the computer/GPU?

    The Quest Pro is arguably more comfortable and offers the better screen solution. I'd advice looking into some comparisons to see which one may suit you better, but since everything is indeed handled on the computer, be aware that you may also require an even faster machine to fully utilize the Pro model compared to the Quest 2. Still, you should also always be able to adjust both/or either the resolution and refresh rate to save some performance.

  • Caddman13 , I appreciate the response.


    I wanted to hereby also inform everyone here that our latest preview which is gonna be released very soon will remove the requirement for Steam + SteamVR when using the Quest or Quest 2 - You will be able to only have the Oculus app running and make use of Enscape. This will just be added into our preview so far, but you may still want to give it a shot.


    Otherwise we'll of course also include this in our full release of 3.5. I'll add another update here once the preview is out.

    Thank you. I am able to use both our VR headsets with the preview version with just the Oculus software and Enscape. This will make everything so much easier. I really appreciate the time and help getting this worked out.