3.5 is extremely unstable and very difficult to use

Please cast your votes in our two ongoing feedback polls here and here!

    While I fully understand the frustration this situation has caused so far I wanted to share that for now (when experiencing the detailed issues here in this thread) we reccomend using Enscape 3.4.4 instead of 3.5.x. This is not meant to be an excuse, but unfortunately resolving these ongoing problems (in regards to using layers, freezes/slowdowns/crashes) proved to be more technically challenging than initially anticipated.


    Our developers are of course working on these problems (and no further example projects are required), but for now there is no specific estimation yet as to when all fixes will be implemented. I'll share further updates once I'm able to, and will notify everyone in this thread once they are about to be added with an upcoming service pack or preview.


    I am aware this may not be the answer you're looking for, but I still wanted to provide some additional clarity.

    Agreed, this is a serious problem. Our office uses both Rhino and Revit 2024, we are forced to choose one program or the other. Its unacceptable as Enscape is marketed for use with multiple CAD software and computers.

    It's difficult to understand how this issue persists after several months. I gather that Rhino integration is a very low priority for Chaos/Enscape.


    It's equally surprising that someone would have to go to this forum to know that there is, in fact, a very serious issue with the current release and that the company itself isn't recommending that it be installed.


    It's all very unprofessional, imo.

    Quote from Demian Gutberlet

    While I fully understand the frustration this situation has caused so far I wanted to share that for now (when experiencing the detailed issues here in this thread) we reccomend using Enscape 3.4.4 instead of 3.5.x. This is not meant to be an excuse, but unfortunately resolving these ongoing problems (in regards to using layers, freezes/slowdowns/crashes) proved to be more technically challenging than initially anticipated.


    Our developers are of course working on these problems (and no further example projects are required), but for now there is no specific estimation yet as to when all fixes will be implemented. I'll share further updates once I'm able to, and will notify everyone in this thread once they are about to be added with an upcoming service pack or preview.


    I am aware this may not be the answer you're looking for, but I still wanted to provide some additional clarity.

    If that's the case, can you please remove Rhino from the "Supported solutions" list below 3.5.x version, as well as other introdution implying that this version is workable in Rhino, since it's not the real case, until the issue is fully resolved?

    ^Totally agree. This is false advertisement.

    I have to tell several colleagues to revert back to 3.4.4 due to the update prompt. People in the office were contacting IT / upgrading drivers / discussing upgrading laptop without knowing 3.5 version of Enscape is actually unworkable.


    Very disappointed to be honest.

    • New
    Quote from Demian Gutberlet

    Our developers are of course working on these problems, but for now there is no specific estimation yet as to when all fixes will be implemented. I'll share further updates once I'm able to, and will notify everyone in this thread once they are about to be added with an upcoming service pack or preview.

    To further add to this last part of my previous post, we're now inching closer to implementing the fixes we were working on.


    Some of which should also find their way into the upcoming service pack Enscape 3.5.4 coming out around the middle of next week particularly in regards to Rhino crashing alongside when the default layer is hidden (which can take a while) and Enscape is closed during that process.


    The long update times when making use of layers will still persist in especially larger scenes, but we're of course in the process of adding a fix for this as well. I'll share another update once I have more specific details available.

    • New
    Quote from Demian Gutberlet

    To further add to this last part of my previous post, we're now inching closer to implementing the fixes we were working on.


    Some of which should also find their way into the upcoming service pack Enscape 3.5.4 coming out around the middle of next week particularly in regards to Rhino crashing alongside when the default layer is hidden (which can take a while) and Enscape is closed during that process.


    The long update times when making use of layers will still persist in especially larger scenes, but we're of course in the process of adding a fix for this as well. I'll share another update once I have more specific details available.

    Unfortunately that last part regarding the long update times is the killer...

    • New
    Quote from ctmascari

    Agreed, this is a serious problem. Our office uses both Rhino and Revit 2024, we are forced to choose one program or the other. Its unacceptable as Enscape is marketed for use with multiple CAD software and computers.

    Demian Gutberlet - second on this. Every year with Revit updates it seems there is some bug or another that forces us to choose our poison. Ideally, we could install different Enscape versions for different host packages. Or would it at least be possible to issue a hotfix for the last "good" version of Enscape? So we could use 3.4.x with Revit 2024 and avoid the Rhino issues?

    Quote from Demian Gutberlet

    Some of which should also find their way into the upcoming service pack Enscape 3.5.4 coming out around the middle of next week

    Will 3.5.4 fix the Revit standalone .exe export bug? *edit - I saw in another post this will be fixed, thank you....