Hello, Oculus Quest 2 still doesn't work in this version in Virtual Desktop, the screen moves in this version along the headset but I see no picture through the glasses. It was working fine in 2.9, and started to break in 3.0
Hi archimage
bugfix will be in the next preview version.
Hello! How is it possible in the plugin for VISUALIZATION, do not improve the materials, the quality of the render and do not introduce the possibility of animation, this is HOW ????? And spend time redrawing the logo and interface (((In my opinion, this is disrespectful towards users !!!!!
Hello! We are constantly working on improvements of image quality, stability, performance and application usability. We are aware of the demand on better reflections, animation and other long awaited features. But some things just can't be easily implemented in a short period of time, no matter how much we want it - sometimes a big amount of work on the infrastructure is needed to make future improvements and new features possible. Moreover, we have more than one development team each focusing on different parts of the product - rendering engine programmers are not implementing UI or CAD integration. So be sure that we are not sitting without doing anything while other teams are working hard and other departments are doing rebranding 
As low poly as my real life beer glass 
When moving around in my model the movement seems to stutter continuously. Can be very annoying.
I am using Enscape in Revit
PC - Intel i9 10900KF / 64GB Ram / Nvidia RTX 3080 - Driver 461.40
Please also send us feedback with logs. Please also mention it's about stutter and you were asked to send feedback here 
Hi Guys,
Just downloaded the 3.0 release and I was wondering can anyone tell me why I had nice sharp glass reflections from my hdri on 2.9 but in 3.0 they are blurry?
Hi! Please give us a screenshot if possible.
Does this mean loading and editing textures will be a lot faster now? Right now, it takes quite a long time to import textures and do any type of size transformations etc.
Hi! it means that loading multiple textures at once (e.g. on a fresh start from a project with lots of textured objecs) will be faster.
Quick update: I am able to open enscape now on models without any artificial light. But once I add even a single component with a light, the program crashes.
The crash happens indeed somewhere deep inside AMD driver in our lighting pass. We have seen it on a few feedback logs from other users with the new generation GPUs from AMD at least with Rhino and Revit. Unfortanutely we could not get any of those GPUs to have a deep look ourselves yet.
hmmm i got RX 6800 too
but i am using it with sketchup 2018 and no crashing when enscape starting ...
i am running 2.9.0+32504 version
Do you have artificial lights in projects you work on?
in 3.0 no changes .. still not working in sync-mode
Bugfix will be in the next preview in about one week.
skhayward it would be greate if yuu could give us a link to a standalone that is affected. You can send it me via a PM. Thanks!
Hi skhayward
Sorry to hear that. We will have a look.
To workaround it, you can append runtime version string to the standalone URL to run it with an older version. This may not work with projects exported with newer version. I.e., standalone exported with 2.9 will very probably not work with 2.8 runtime.
For 2.8.1 append ?runtimeVersion=2.8.1.5-g1c9bb2a-27660-r1767
For 2.7.1 append ?runtimeVersion=2.7.1.68-g75e92e4-20078-r1264
Hope it helps.
The rocks rock!
Hi irmak and welcome to our forum!
Funny means there are two images? In this case you have selected a stereo mode in General Settings window -> Devices.
Hello Frans van Keulen
This is a known limitation that cannot be fixed due to how standalone is created now on the client PC where Enscape runs. There are plans to change the way standalones work in the furure. No ETA, however.
Could you share the skybox image or give a link to the web standalone where this skybox is not showing up? Sounds like a bug to me.
I have problems with the web viewer because it does not handle my background panoramas.
Hi Harry ,
Could you please give a bit more details about what exactly does not work? Are you talking about skybox not working for some reason in web viewer?
emcminn it was a multithreading issue. Geometry data could have been modified in one thread, while the other one was processing this data. This bug was for a long time there already, it's just occasion that with 2.8 it started to be a problem, due to some other changes and tweaks. As it usually happens with undefined behavior bugs which are hard to identify and reproduce.
Is a 1.1GB Sketchup model too big for Enscape on a 2080 Ti?
It depends on what takes up that space. With 1 GB of pure geometry data you will very probably have some issues. Not memory related though.
When I launch Enscape is gets to about 60% and then I notice the CPU maxes out and then crashes both Enscape and Sketchup. I did send the latest crash/log files the last time this happened.
We have received it, thank you! According to the logs Enscape detects it is frozen and shuts down. It may be a false positive, because the project seems to be pretty big and some operations may really take longer than expected. We collect such cases to find a good solution. Thank you for providing your case again! It would be great to have the project too to have a repro case to work with, if possible. Contact me via PM if you can share it.
A temporary workaround for you would be to switch to the draft quality mode - freeze is detected while preparing data structures for global illumination rendering.
Hello pmx
I've created a bug report for your case, looks rather strange. We will have a look and get back to you when we will know more.
This sounds like physics simulation for walking slows down because of the big amount of geometry. This is expected with the growing number of objects we analyze for collision detection. The same applies for the screenshot/panorama rendering. Even if it does not slow down that much for a single screenshot, for stereo panorama multiply the slowdown by 64.
DeKoetsier it very probably due to the amount of geometry on the scene - Enscape simply needs some time to converge to the stable result while doing each panorama slice.
Easy way to check if this time is expected is to make a normal screenshot in 2048x2048 resolution and measure how long it takes. Than multiply this time by 64 - the number of screenshots needed for stereo panorama, and it should roughly match the time you measured for complete stereo panorama.