Hey all - I have an old version of T-splines installed on my Rhino 4. It still works there but comes up with an error every time I start Rhino 5.0, saying "Error Loading - T-Splines." The details specify "Unable to load TSplines_64.rhp plug-in: plug-in not compiled for this version of Rhino."
I cannot figure out how to tell Rhino not to try to load this plugin; TSplinesUi is already disabled in the plug-in manager and the error comes up anyway.
Any ideas how to get around this?
Tags:
Permalink Reply by John Brock on March 15, 2012 at 4:02pm Go into Tools - Options - Plug-ins. Find it and remove the Enables check.
John Brock
Rhinoceros
Seattle
USA
Permalink Reply by Andrew Heumann on March 15, 2012 at 4:45pm
Permalink Reply by John Brock on April 3, 2012 at 11:09am There are two T-Spline plug-ins on the list. You must only have load protected one of them.
JB
Permalink Reply by Andrew Heumann on April 3, 2012 at 11:53am Thanks John, but I only have one T-Splines plug in in my plug-in manager. Filtering by "Plug-ins that do not ship with rhino" shows only Grasshopper, TSplinesUi, V-Ray, and Weaverbird.
The window that comes up every time I start rhino says "Done installing plug-ins" at the top, as though it is trying to automatically install the plug-in but failing. How does Rhino decide which plug-ins to automatically install? I assume it checks the Rhino 4.0 and 5.0 plug-in directories, but t-splines lives in neither of these places.
Permalink Reply by John Brock on April 3, 2012 at 11:58am It looks like the list isn't accurate. Change to All and I think you'll it.
Permalink Reply by Andrew Heumann on April 3, 2012 at 12:07pm
Permalink Reply by John Brock on April 3, 2012 at 3:45pm I don't see it either. It will probably require some System Registry 'surgery'. Before you go that far, contact TSplines and as them. I'm sure they have hit this quesiton before.
JB
Permalink Reply by Andrew Heumann on April 3, 2012 at 4:00pm Thanks a bunch - the registry was the ticket.
HKEY_LOCAL_MACHINE/SOFTWARE/McNeel/Rhinoceros/5.0x64/Plug-ins had two entries corresponding to the two mystery t-splines plug-ins that it kept trying to load. Deleting them solved the problem.
© 2013 Created by McNeel Admin.
