Enscape causing crashing in Rhino Inside

REMINDER! If you encounter any issues with Enscape (e.g. crashes, installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Support button as detailed HERE! Thank you for your understanding.
  • This is a cross-post from the McNeel discourse forum, explaining an issue which we believe we have traced to Enscape.


    When RhinoInside is used to open a particular rhino file (within the context of a Rhino Inside Revit session), it causes Revit to crash. The only solution currently is disabling Enscape in Rhino 7.

    Info from that post..

    Revit version is: 2021.1.3
    Enscape version (revit) is: 3.1.2 +55592, build date 9/7/2021 08:10 UTC

    Rhino version is: R7 SR12 (7.12.21313.6341, 2021-11-09)
    Enscape version (rhino) is: 0.0.21250.810

    Please let me know if there is other information which would be helpful to have.

  • Rick Marx

    Approved the thread.
  • Hi Matthew Breau

    To help us better understand this issue, could you also please send us the log files found in "%tmp%\Enscape\Logs".

    You can just place all the files that are contained in this folder into a .zip file and send them to me via a DM.

  • Hi Ben Peake

    We are indeed aware of the issue now, we are still investigating this.

    It is good to know that this issue does not happen for you when rolling back to our 3.0.2 version however.

    Matthew Breau if this is an option for you, could you try if rolling back to our 3.0.2 version resolves this for now for you as well?

  • Yes, I'll add my (our) voice to this issue. There are a few things that clash with Enscape on our system at the moment. If we want to 1. export IFC using the IFC addin in revit 2. use rhino.inside - then we have to disable enscape or Revit will immediately implode. haven't investigated a lot into it; we have an addin that can enable/ disable addins so users selectively disable enscape when they want to execute these tasks

  • Phil Read  Rick Marx Just wanted to follow up and see if folks are still reporting this problem, or if you've been able to confirm there is a reliable fix..

    For a bit of context, I'm at a new firm now (Beyer Blinder Belle), and BBB uses Enscape pretty heavily, but we're looking to roll out Rhino Inside asap. Current workflow is to have users disable Enscape in Rhino and then close Rhino, before launching Revit and then launching Rhino-Inside. When they are done with Rhino Inside, they have to then re-enable Enscape in Rhino.

    Would be great if that was no longer required...

  • Hi Matthew Breau , Ben Peake , ian.atkins and Phil Read

    Thank you for your patience regarding this topic, and apologies for our late reply.

    Currently, we do not support Rhino inside Revit.

    The error message occurs because when Rhino is started from within Revit, it tries to initialize Enscape in the same process again which is expected to fail.

    After pressing "OK" in the error message, Enscape should work as expected (in Revit, not in Rhino).

    Our policy is to fix bugs for Enscape in Revit that are caused by that, but the error message is expected and there are currently no plans to support Enscape in Rhino when started from within Revit.

    This error didn't occur in our 3.0.2 version, but without having tested it, it might have caused even more issues during usage of Enscape in Revit.

    Additionally, if you don't want to use Enscape in Rhino at all, you could install Enscape only for Revit. Then the error message shouldn't appear.

    You can forward your feedback directly with our product management team here however. Simply click the "Submit Idea" button at the top right, and enter your feature request there.

    In the Portal, you can also see which features are currently being developed, and vote on features we are currently considering. For a more detailed overview, check out this post in our Forum.

  • Hey Rick, no worries/ appreciate you circling back.

    Just to clarify... When loading Rhino Inside, there is a dialog saying Enscape failed to load, which is ok. However, the true problem comes after this this message. When a user tries to open a Rhino model within Rhino inside, it crashes Revit and Rhino without warning or explanation, even if Enscape is not actively running in Revit (and "Failed to load" in Rhino).

    We've advised our staff to do a clean uninstall and re-install of Rhino 7 and Enscape 3.3, and advised them to always save and sync their models before launching Rhino Inside. Hopefully that solves the issue fully. If not, then we will provide guidance to users that they must disable Enscape in Rhino then close Rhino before launching Rhino Inside (so it does not even *try* to load Enscape). That would not be ideal, but it is what it is. If this ends up being the only surefire fix, maybe the Rhino guys can add a button that allows users to specify which plugins load in Rhino Inside or something along those lines.

  • Hi Matthew Breau

    Hoping that will already resolve the issue for you indeed.

    Informing with the McNeel team regarding this or possibilities is also a good idea indeed, perhaps this can be solved that way as well.

    Would be interested to their reply should you contact them.