When I start Revit and click on any 3D view, Revit opens the view an displays everything.
But when I start Revit, then Start Rhino Inside (Latest Stable version), then Grasshopper and then open any 3D View I get the following Error Message “An error occurred drawing the contents of this view. The view will be closed.”
If I start Revit and open a 3D View and then start the whole Rhino Inside, everything seems to work for a few minutes and then Revit Crashes randomly.
The only common factor here seems to be Rhino Inside.
So, 2 years later and I am doing a project in Revit 2025. This error still occurs when using the latest version of Rhino inside (daily built)
I have been working with RIR for the past 2 years in Revit 2022 and I never had the Error come up. Now with Revit 2025 I am getting this error again. Is there a known fix for this yet?
Hi @joel.van.herwaarden and @Japhy, I have the same issue in multiple Revit versions (2022 and 2024). When trying to display the grasshopper geometries in a 2D or 3D view the view crashes.
Also note that this error is coming from Revit and has a number of possible explanations and fixes, with a large old project i would look at families, materials and graphics settings.
I have turned off the preview by default. I discovered that is messes with Revit if Geometries are far from the origin, so that cannot be the issue.
@Japhy The audit does not do anything. But turning off my Hardware acceleration does seem to help. When starting RIR I do get an error for the Enscape plugin in Rhino 8 (see image below)
For me this error does come up consistently when using RIR in combination with Revit 2023 and above. I have no problems with 2022 with Enscape and Rhino 8
Are you running Enscape in Rhino as well as in Revit at the same time? Note that when an addin loads in Revit 2025 its going to be in a different .Net than previous versions. This works well in Rhino 8 on earlier versions of Revit because it runs in .Netframework 4.8, which i believe is what Enscape is built on.
I uninstalled Enscape and the problem is still there (Revit 2024).
More info about the problem: the crash doesn’t happens immediately, it happens when trying to orbit or pan in the view. If you don’t move the camera but you try to select an object to see their properties, the crash happens when trying to display the object properties. It is clear that the problem happens when re-rendering the view.
If I remember other similar crashes in the past, I think it has to do with the scale of the objects or the distance from the origin. I will try to reproduce the error in a blank file.
@Japhy, I think I found something interesting.
I opened a blank Revit model and a blank Rhino/Grasshopper and everything worked fine. I tried some generic geometries small and large and also far away from the origin and everything worked fine. Without closing Revit/RhinoInside, I opened the usual model that used to crash and it worked fine, no crashing.
Then I closed everything and reopened the usual chasing model and it crashed. In the same session, I tried to open a blank grasshopper model to test some random geometries and I the following message appeared “Rhino model has no units” (see screenshit below), which is the first time I see this message in 17 years I am using Rhino. Rhino always starts asking for the model units, but RhinoInside never asked and it seems that this is the error.
To conclude, I clicked on “Use Millimeters like Revit” and the problem persists.
