Enscape 3.0 Major Bugs w/Vectorworks

    I've been using Enscape for Vectorworks since launch of Beta version about a year ago. Generally speaking it is great program and love the constantly evolving features and live link to VR headset.


    Unfortunately, the latest 3.0 release for Vectorworks has been a major disaster. Here are some of the issues I encounter, that happen every time I launch the Enscape render window:

    1. Disappearing buttons

    2. Buttons that stretch or warp or are non-functional

    3. Regular crashes when rendering stills, forcing restart of both Vectorworks and Enscape

    4. Items hidden in VW still remain visible, so Enscape render window has to be closed and re-launched for them to appear correctly

    5. Animated clouds no longer animated when adjusting time of day

    6. Overall unusable/broken interface


    Have others experienced this? I am about ready to throw in the towel if these bugs are not addressed very soon. Very disappointing and disruptive to previously reliable workflow. Glad I waited until after deadline to update Enscape to latest version.

    CRhodes especially when it comes to the crashes and issues overall it's rather important to receive a dedicated feedback report with your logs. Please kindly send one in and include a link to this thread for reference in the submission form before sending - I'm sorry you have to experience this, but we're eager to find a solution to these problems. Thank you in advance!

    Me too! :(

    Hi Damian!

    I'm having a lot of crash, but there's no the same reason: looking for a symbol, or texture, hiding layers or class, running a macro (to display a set of layer o class...) in other words: I have no answers to say.

    I'm thinking to install back the 2.9.1 release...


    Ciao


    L.:)

    Toscano , no worries though, no matter when it crashes, it would still be great to get a feedback report, please. :) This way we can let you know why it's crashing! And, we can find the cause behind it of course to resolve it as quickly as possible.

    Quote from Demian Gutberlet

    Toscano , no worries though, no matter when it crashes, it would still be great to get a feedback report, please. :) This way we can let you know why it's crashing! And, we can find the cause behind it of course to resolve it as quickly as possible.

    Hi Demian!

    Often is not possible to send the report, because I've to reboot my PC.

    Anyway, some days ago, I've had a dialog to send the report and I did it. (Lautaro)

    Thank you again.


    L.


    PS. I think, it is time to release some patch or, please, tell me if I have to re-install 2.9.1

    In that case, I think I'll loose some asset coming with 3.0.0. Is that correct even I dowloaded them?

    I am also experiencing the same problems, have submitted countless logs, been given same workarounds as given before, that do not work and a deadline fast approaching! Rapidly becoming disillusioned with Enscape.

    Error code 9, GPU 1


    GetGraphicsResetStatus() returned 33363


    Error code 10, GPU 1

    Enscape has detected that an operation takes longer than expected


    Here are some of the other issues I encounter, that happen every time I launch the Enscape render window:

    1. Disappearing buttons

    2. Buttons that stretch or warp or are non-functional

    3. Regular crashes when rendering stills, forcing restart of both Vectorworks and Enscape

    4. Items hidden in VW still remain visible, so Enscape render window has to be closed and re-launched for them to appear correctly

    5. Overall unusable/broken interface


    RESPONSE FROM ENSCAPE


    Thanks for getting in touch with us here at Enscape!



    We believe this is an OUT OF MEMORY issue that is caused by a bug that does not consider the amount of VRAM taken by the geometry in a project. The developers are aware of this issue and are trying to resolve this is as soon as possible.



    Workarounds in the meantime include:

    • Reducing the Resolution down to FullHD and the Rendering Quality to High. DONE
    • If your GPU is not RTX, then try disabling the RTX option found in the General Settings -> Performance options. N/A
    • If you are using Revit, you can employ the use of Section Boxes to reduce the amount of geometry that requires rendering, as well as to try using the 'Purge Unused' option in Revit. I'M VECTORWORKS
    • It could also be worth reviewing the textures in the project to see if these can be reduced or optimized in any way. DONE
    • Lastly, rebooting the machine before using Enscape will clear the VRAM, freeing up resources for Enscape on the GPU.

    IT CONSTANTLY CRASHES, SO BEING REBOOTED ALL THE TIME, STILL NOT WORKING


    If the issue still persists for you despite employing the above solutions, then please submit some fresh logfiles via the Enscape Feedback button.

    I have now submitted so many logs, where do I go from here, will going back to previous version fix this, PLEASE i just need to know how to fix this.
    ?





    I'm sorry to hear about that Franmj , can you send me your e-mail via a DM then I can check the ticket as well.


    Regarding the issues not related to just the crashing, have you tried what TKAstudio wrote just above your first post in this thread? :) Just to make sure.

    Franmj , I saw you already send me a DM now, thanks.


    Furthermore, you may simply ask your system admin to help you with what TKAstudio referred to - In Windows (and other operating systems) you have both Admin and non-Admin accounts. He mentioned that this issue only occurred with an Administrator account (Admin accounts usually have full rights to do everything on that particular system, why this causes such issues with Enscape is not known yet), so it should be worth trying using a non-Admin account.


    Do you have someone available in your company to assist you with this? As mentioned, a system administrator for example?