@Japhy Hi, i also got the same problem and was able to solve it by repairing, using .NET and restarting Rhino 8.
is this some bug in Rhino 8?
@Japhy Hi, i also got the same problem and was able to solve it by repairing, using .NET and restarting Rhino 8.
is this some bug in Rhino 8?
Hi Hassan -
Rhino 8 has been updated to run under .NET Core instead of the depreciated .NET 4.8. If you run a plug-in that has not been updated and relies on a function inside of .NET 4.8, that plug-in will fail. We have provided the switch so that users that need such plug-in can continue (some)() work while the plug-in gets updated. You’ll need to contact the author of the plug-in to request them to do this update.
() As time goes on, you might need a different plug-in that relies on a newer version of .NET. At that point, you won’t be able to use both plug-ins at the same time but need to use the switch and restart Rhino to switch between plug-ins.
-wim
Hi Wim,
Thanks for the detailed explanation.