Posts by Alexander Devaykin

    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.

    Hi Patty - Willow

    Did you try to launch Enscape with that model and see what happens?

    The biggest VRAM consumers are textures and Enscape itself (frame buffer, acceleration structures, shadow maps and so on). Geometry usually does not take much space. Views, sheets, etc. do not have any significant effect on the Enscape memory consumption at all.

    To use as little memory as possible for Enscape itself, you should try to switch to "Draft" quality mode prior to starting Enscape with that model. Also keep Enscape window small - if you have a 4k display and have Enscape fullscreen - you have lost a few gigabytes of VRAM already.

    Textures are scaled down with respect to the world size they occupy, where possible. Even if you have hundreds of textures in the project it will be somewhat hard to waste more that 1-2 gigabytes for textures.

    What will really be bad is startup time. Exporting and processing all the geometry and scaling textures may take much time. But you still could try and see what will happen.

    Good luck!

    Hello Ollyt

    I'm having the same issues, I cant seem to get it back to working tho, every time I render the just get the black screen. After you close it down I can not get enscape window to open again. Have to close down and open the fole up again and give it another shot.

    We cannot tell much from this symptom alone. Please send the logs - black screen can be a result of a dozen of issues. Very probably it is GPU memory related, however.

    The following can help if it is memory related:

    1. Capture in a lower resolution. If works perfectly every time - you are out of memory because of the capture resolution.

    2. If you have an RTX GPU - make sure you have the latest driver and try disabling RTX.

    3. Change rendering quality to "Draft" - it will also reduce memory consumption and will disable several rendering passes which could have issues.

    These options may become a workaround for the urgent case. For better diagnostics - please send us the logs.

    There is an incompatibility between 2.8 preview version project format and web runtime, which means that web standalones created with 2.8 wll work only when 2.8 stable release will be published and web runtime will be updated to that version.