@Japhy - Hi!!! One of my users has discovered that Rhino.Inside (with Rhino8) is conflicting with the CTC tools plug-in in Revit 2025. He received several error messages. He was able to grab a screen of “Failed to find ‘opennurbs_private.manifest’ file in Revit folder…Do you want to install now?”. Clicking OK caused everything to crash. There was a second error message about Eto but he did not grab a screenshot of that one. Through some troubleshooting on his own he figured out that disabling the CTC plug-in solved the issue. I’m going to reach out to CTC as well, but he in particular needs to be able to run both. Is there anything you can do to help resolve this issue? Any guidance aside from disabling CTC? Thanks!
Hi Christina, Is their plugin compatible with .netcore8? (which Revit 2025 requires)
CTC devs can reach out to us at anytime for assistance, the delay is typically due to the dev having to make changes to work in a different runtime, rather than lack of knowing what to change.
Well…it appears they didn’t have the newest version of the CTC plug-in… so false alarm. Updating to their latest version seems to be running ok now. Sorry to bug you!
1 Like
No bother, anytime.
Hi @Japhy, After installing the latest official release for Rhino.Inside, the same warning is displayed for me on Revit startup. The only problem is that inside a dynamo script with a python script node, when I tried to edit the script, Revit crashes/freezes completely.
At first when other dynamo packages were present Revit crashed. After removing all third-party packages (including DynamoIronPython 2.7-3.1.2 and DynamoIronPython 3 which I had and the python node defaulted to the CPython3 engine) Revit and dynamo did not crash but were unresponsive.
I then tried removing all add-ins from Revit except for Rhino.Inside but that did not solve it. If I disable only the Rhino.Inside add-in the problem is fixed and all other packages/add-ins work.
Is there a crash report being generated?
We haven’t had any reports dynamo conflicts, this is most likely the additional python environments in Revit.
Is Python scripting working as expected in stand alone Rhino?
Here is how to reset the Python in Environment in Rhino
Delete C:\Users\<user>\.rhinocode\python3.9-34\site-envs\default-* environment folder, restart Rhino and install again. It might be a conflict with other packages installed before. If you see errors, send me the contents of RhinoCodeLogs please
Please delete the %HOMEPATH%\\.rhinocode and start Rhino
-
Run
ScriptEditorcommand and let it initialize languages -
Run
RhinoCodeLogs, save the logs into a text file
There is a Rhino crash dump .dmp file that is generated and deleted after I send the report from the Rhino crash report window which the forum doesn’t let me upload.
I checked the python nodes in grasshopper from Rhino.Inside and from standalone Rhino both of which work, but the python script node I was talking about is the one from inside dynamo. The crash happens even without starting the Rhino plugin from the ribbon button in Revit.
Just placing the python script node, closing dynamo and then trying to start Rhino.Inside also produces a crash.
@eirannejad any ideas on this one? Do our python versions need to match or can they run independently?