Revit Crashes as soon as I open Grasshopper

Rhino.Inside Revit
,
1

I have the latest Revit, RiR, and Rhino installed. I can open RiR ok, (the button that initiates the “bridge” between Rhino and Revit), but as soon as I try and open Grasshopper, Revit crashes. Haven’t found a fix for it. I have the Revit crash report, but I can’t find any crash report for RiR or Grasshopper.

2

Hi Liam,

To troubleshoot try opening Grasshopper via the Rhino command line with GrasshopperLoadOneByOne command and say No to 3rd party plugins. The first dozen or so ship with Rhino. I suspect you have a plugin compatibility issue, what version of Revit are you running exactly?

image
image493×534 63.1 KB

3

Hi Japhy,

Thank you for the help. I started Grasshopper using OnebyOne and did not load any non-native plugins. Grasshopper loaded fine without crasing. Is there a way to easily figure out which plugin it is, or do I have to go through one by one? (I have probably 10 plugins)

image
image459×405 9.93 KB

4

Hi Liam -

Typically, you need to go through these one by one. If you have a list of plug-ins, perhaps the RiR folks around here can tell you immediately which one is a likely target…
-wim

5

So, I just discovered something very weird. If I click on the grasshopper button in Revit, Revit crashes.

image
image677×106 10.6 KB

If I open Rhino first (via RiR), and then open grasshopper through the command line in Rhino, grasshopper loads, but no window opens (and nothing crashes). The loading window for grasshopper stays up.

image
image1385×681 207 KB

If I run the grasshopper command again from Rhino, grasshopper opens with no issues (that I can tell).
I did not use the GrasshopperOnebyOne command, just regular Grasshopper.

6

The load one by one is just to see is that is a factor.

Its easier to either move the gh plugins to a temp folder or use the package manager to do your process of elimination.

7

Ok, I was able to isolate the issue to the Wires Renderer plugin. Latest release is 1.4.5. I tried 1.4.4 and still had the same issue. Decided to skip a few releases and go back to 1.4.0. That worked and I no longer seem to have an issue.