Posts by Alexander Devaykin

    I have the same issue with this preview version as well. When I first press the render button I see the "Starting Enscape..." modal window with 5%, and then it exits. This happens even on a blank Sketchup document.

    I am using Sketchup 2018 and an RTX 2070. When I disable "NVIDIA RTX Ray Tracing" it works.

    Thank you for trying out the preview! Please make sure to send feedback with the logs so we could have a precise look at what happened!

    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 ;)

    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?

    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=

    For 2.7.1 append ?runtimeVersion=

    Hope it helps.

    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.

    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.