Posts by BGBUK

Reminder: If you encounter any issues with Enscape or your subscription please reach out to our dedicated support team through the Help Center or by using the Feedback button as detailed here.

    I'm getting the same issue with my Reverb G2 and thought I'd report my findings here.


    I'm using an i9-9900x, 2080ti and 64GB DDR4. Win/SU/Enscape/WMR/Steam VR all installed on Samsung Evo 980 M.2 SSD. I've never had any bottlenecking so far - my largest model being perhaps only 150MB but often very high-poly and with many HR textures.


    The Reverb G2 seems to work fine under normal operation (using the WMR portal to view videos, using the browser or operating the desktop etc.) that's all good, and my system seems to cope with this easily.


    However, when I tried to view a current project in Enscape using the G2 I encountered awful stuttering, and noticed my GPU usage was up around 97% (CPU less than 20%). It was completely unusable.


    I checked the resolution settings in Steam VR -indeed the resolution was set waaaay over what the G2 is capable of. Reducing it to 2360x2360 (or something like that) per eye helped a LOT. Also, reducing render quality in Enscape from Ultra to High also helped quite a bit- I noticed no real difference between High and Medium however.


    So it seems the GPU is the bottleneck - I imagine it's the VRAM capacity rather than core count or speed that's the issue? It won't be PCIe lane bandwidth as you can see from the setup I'm using. I'm surprised, but not overly so. 12GB seems a lot but I often see the system utilising 32GB system memory so....


    Back to the Quest 2 it is!


    On a separate note- there is a really weird bug using the G2 - I have to switch back and forth between Walk and Fly modes to get both joysticks working. It's a small issue, but another reason why, for now, I will stick to the lower-resolution Quest 2 for use with Enscape.

    Demian Gutberlet OK Thanks- can you PM me your email address please? The WeTransfer link asks for it.


    Just to be clear - it doesn't matter whether it's a spotlight or a globe light- if it's placed inside the Asset component, it doesn't work. Am I missing something to do with the Asset lights themselves? I can't find any settings for them as such, they just appear to be geometry?


    Thanks.

    I thought I might chip in here as I've been using a Quest 2 with Enscape 3 for a few weeks now. Most of my projects are concept/spatial design for houses and commercial buildings/spaces. I've not tried the AirLink feature as yet. FYI I'm using a RTX 2080ti GPU.


    Quick overall judgement: If you've never experienced VR then the experience is generally positive and reasonably impressive, unless you suffer badly from motion sickness.


    In more detail: (concise points outlined in bold font)


    The interface is a little clunky, and will definitely require setting up well before meeting with a client. You have to have the Oculus app and Virtual Desktop installed on your computer to make it function at all, and use a compatible USB 3.0 cable (and port on your computer). Even when using a compatible cable (the occulus app has a cable test feature btw) it is not foolproof: sometimes the connection won't register, and hot-plugging is definitely not recommended. I seem to be getting waaay more WHEA errors since I started using the link cable.


    The process to get it running is outlined by LEGOsketcher above (thanks) but I'll go over it again here so anyone reading this can see how the process can differ.

    1) Open your sketchup model

    2) Open the Occulus app on the computer

    3) make sure Virtual Desktop is running on the computer, and that 'Allow remote connections' is ticked

    4) Connect the Quest 2 to the computer using a compatible cable

    5) Put the headset on, and if a message pops up to allow access to data, click deny using the controller

    6) Still wearing the headset, if a request to enable link mode doesn't pop up, click on settings and then click on 'enable link mode'

    7) A new VR space and menu will appear. Click on the Virtual Desktop icon (right hand side) and select the monitor which is showing sketchup

    8 )Start Enscape

    9) Click on the VR headset icon in Enscape


    Resolution and clarity:

    For me, the resolution isn't great. I think that is generally the case for the Quest 2. It might be 'good for VR', but it doesn't come close to a good 4k rendered still image- I can see the individual pixels and the field of vision isn't nearly wide enough for me to call it completely immersive. The lighting is OK - don't expect ray-traced smooth shadows and do expect some granularity. Also, some light-coloured but non-emissive materials have a sort of digital glow when up really close.That said, the VR experience even at that resolution is still impressive and I for one am adopting it into my presentation workflow.


    Modelling:

    As with the progression from sketchup-Enscape etc. viewing the model in VR will highlight any bad modelling/textures etc., and it really is important to use high-quality, low-poly assets (furniture, light fittings etc.) as well as making your model as detailed as possible to get the best experience. Think about how textures are represented on a victorian four-paneled door for instance: if the whole door uses the same texture, you will need to clearly define the edges of the panels using geometry and a contrasting texture to make these features visible and realistic.


    Client usability:

    As above, for a positive experience this will need to be all set up pre-meeting otherwise it could look pretty unprofessional. If the client/user has never experienced VR before (or perhaps even if they have) they may find navigating the space using the thumbsticks/joysticks disconcerting/nauseating so beware - I recommend having them seated to begin with. It helps MASSIVELY to have a large space and guardian (google if you're unfamiliar with this) set up, along with a much longer cable than you think is needed to accommodate the user turning around several times.


    Performance:

    My PC specs are below. I have had the GPU temp. up to around 80 degrees C on the highest resolution possible, which is OK. I don't have any stuttering, flickering, clipping etc. It's all good.


    Specs:

    SketchUp 2021

    Enscape 3.022 (as of this week)

    i9-9900X

    64GB DDR4

    RTX 2080ti

    Hi,


    I'm having an issue with the asset lighting in Enscape. I've illustrated the problem below.


    Basically when I use a globe or spotlight object in the global model (i.e. not within a component or group hierarchy) it works fine, however as soon as I put that light object within one of the Enscape asset lights (such as the brass wall light shown), the light object no longer works at all. It's not within the glass bulb etc.


    This basically renders the Enscape Asset lights completely useless if I want them 'on'. Can anyone help?

    Specs etc. below.


    SU version: 2021

    Enscape version: 3.02 +44009


    PC Windows 10

    i9-9900x

    rtx 2080ti

    64GB Ram