Enscape 3.0 and Revit Worksharing

Please note: Should you experience issues with Enscape or your subscription, and in case of any urgent inquiries/questions (e.g. regarding our upcoming licensing changes) please reach out to our dedicated support team via the Help Center or Support button as detailed here.
  • I am running into a bug that crashes Revit. Looking in the log files, it seems that there is an element ownership issue causing the crash.

    • Official Post

    MichaelRensing , welcome to our Forum! I'm sorry to hear about that - can you additionally send in a feedback report then:
    https://enscape3d.com/communit…sing-the-feedback-button/

    For context, you can simply include the link to this thread in the submission form before sending us the report.

    Thank you in advance, that will be very helpful for troubleshooting the cause behind this.

  • Hi!


    I've just run into this aswell - albeit (thankfully / touch-wood) without a crash...



    switching a live enscape session between two-point/ortho/perspective whilst in a workshared model invokes workset borrowing/ownership conflicts -



    querying the ElementID of the error/warning highlights the 'Data Storage Elements' workset is being used by Enscape in some manner - differently (now) to how (if at all) it did in the past.

    Yes, one can "cancel" the workset prompt, see the camera change in Enscape, and proceed (without placing the request) but before we start to see crashes, or find this becomes even more of a nuisance (on bigger projects with longer sync' times) - and noting the age of the OP, could I ask this be looked at (again) soon-ish please.


    Thanks


    (Enscape 3.1.0.51825 on Revit 2021 21.1.21.45)

    • Official Post

    Thanks for the Feedback snowyweston . In the first instance, would you be so kind as to also send in a Feedback report? Just to make sure we have that available in case we require it for further troubleshooting anyway.


    Before sending in the report, please kindly also mention my name and especially a link to this thread in the submission form so that it reaches me directly, and/or so that my colleagues have an easier time understanding the context.


    I appreciate it, thank you again in advance.

    • Official Post

    We have been running into this as well. is there a fix coming in the foreseeable future?

    Welcome to our Forum.


    After further analysis, this is a behavior that we'll tackle with release 3.3, or a preview beforehand. If you experience crashes though, instead of just an error message, please also send us a Feedback report as detailed here.

  • Welcome to our Forum.


    After further analysis, this is a behavior that we'll tackle with release 3.3, or a preview beforehand. If you experience crashes though, instead of just an error message, please also send us a Feedback report as detailed here.


    Hi Demian,

    Sorry to revive an old thread. Curious to know whether this issue is resolved with the release of 3.3? I cannot see anything explicitly stated in the Enscape changelog.

  • We also run into this, but it's just one of many cases where worksharing and Enscape are not working well together.


    I believe the root cause is that Enscape stores all its data on a single location (in a custom Data Schema) instead of splitting it up in smaller chunks that can be edited by multiple users simultaneously. As soon as a user makes a change to one of Enscape's settings, it automatically checks out the entire system.


    Other issues we're seeing: getting stuck in endless "user X has requested you to sync" loops, crashes, loosing settings (for example the "linked visual preset" constantly resets if we have more than one user working in a model).


    Enscape is the only render engine that should (in theory) easily allow us to work with more than one person on a single model inside Revit (different from for example Lumion or Twinmotion where as far as I am aware, that is not possible). It's so unfortunate to see this advantage is starting to fade (the issues described here were introduced 5 versions ago with 3.0) .


    At one point we will have no choice but to give up hope that this will ever gets fixed, at which point we will have to consider Enscape on equal footing with Lumion and Twinmotion when it comes to worksharing. A real shame.

  • Hi Pieter,

    By reading on what are Data Storage Elements, apparently that is the point. The developers can tap into this API to create bubbles instead of spreading the borrowing across multiple parts of Revit. At least this is my understanding of it.


    Have a go at 3.4. The issues are still there, but on our testing but no more crashes for far. If you do test this, let me know of your findings.

  • Demian Gutberlet any e.t.a. on this? I have multiple teams working towards deadlines atm and they are all struggling with this. I'm not talking about adding an extra 5% to total time spend on visualization but rather double or even triple. This issue has existed since Enscape 3.0 and 3.4.3 (that had a limited scope fix for this) has not resolved it for us. And of course 3.5 also has the same issues.

  • In my opinion there's been a lack of focus since 3.0. New features barely get improved, bad bugs stay around for years without getting addressed, features seem to be less aligned to popular user requests...