Hello there !
Rhino Inside Revit problem, Rhino 8, happened on 2024, 2023, 2022
Happened as soon as I tried to pen Grasshopper.
Attached is the log report
RhinoDotNetCrash.txt (2.6 KB)
RhinoDotNetCrash.txt (2.6 KB)
Hi Thomas,
What version of Rhino.Inside.Revit are you running?
Did you install any new Rhino, Gh or Revit addons recently?
RhinoInside.Revit_1.21.8913.17015
Nothing major, just an update of Pyrevit, works fine with Rhino 7
Just installed the latest pyrevit, with no apparent conflicts.
Lets troubleshoot by starting grasshopper via the Rhino command line with GrasshopperLoadOneByOne, saying No to 3rd party GH plugins.
The bug is gone in 2024 but still there in 2023
I used the command onebyone, it worked, it therefore is one of the plugins. Is there am easy way to isolate the problematic one ? I have an idea of the guilty party, I’ll try
RhinoDotNetCrash.txt (2.6 KB)
The mscorlib.dll is a general error and points towards a .net issue.
This is most likely a GH plugin referencing an unsupported .net version (Revit pre 2025 runs in .NET Framework 4.8 so points toward Rhino 8 specific plugin referencing .NetCore)
Okay, super strange, the bug is still happening on Revit 2023 and lower.
But…if I launch grasshopper through command in the Rhino interface instead of just pressing the button on the ribbon, it works …
Go figure, it might be more complicated than we thought.
Also, why does it work in 2024 and not in 2023 if they use the same .net library
If all things (revit addins) are the same, good point.
Are all the crashes showing Fault Module Name: mscorlib.dll in the reliability monitor details?
There could be additional helpful details available in the Event Viewer on specifics of the .net crash as well.
Doing that solved the problem (Maybe)
But changing this setting didn’t stick when I reopened GRasshopper, another bug report ?