Posts by Caddman13

    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.

    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.


    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.

    1. Render scene with and without foreground trees and cars and other Enscape items.
    2. Open in Photo editing tool and place scene with foreground trees and cars and other Enscape items on top of rendering without foreground trees and cars and other Enscape items.
    3. Decrease opacity of scene with foreground trees and cars and other Enscape items.
    4. Save as new image

    This is what we ended up doing. Would be a nice feature to have this ability in the rendering software. I just not a big fan of jumping from software to software. Seems counterproductive.

    Caddman13 , any user who experiences this issue may kindly send us a Feedback Report, especially if they run into a fatal error, the log files should give us more info as to why this occurs. Thank you in advance.

    I have asked that the users do this. I have one who is trying now and it too crashes with an error. They sent a separate email to support. Could you share the location of the log files? I can send those to you. Thanks

    Have had several users report to me that when they use the Enscape Material Editor Revit will create a fatal error and close the program. All other commands in Enscape work as expected.

    Revit 2020 and 2021 projects, Enscape 3.2.0+65063.

    Anyone else running into this issue? Thanks


    I have a material in Revit 2020 and it shows in the Realistic model fine. When I render with Enscape it doesn't look anything like it. I have recreated the floor in Revit changed the elevation of the floor with the material and nothing seems to get it to work in Enscape. I have other views that render fine with the same floor and material. What am I missing?

    See images

    This is from Revit

    This is Enscape

    Thanks for the help.