I have tried uninstalling karamba through package manager, installing karamba through the installer on the website, manually deleting Karamba in the plugins folder, reinstalling Rhino and Karamba so far. Nothing seems to fix the issue.
I would appreciate it if someone could help with this. Thanks!
I also had this problem. 3.1.50707 was automatically installed through the package manager but it seems the older version of Karamba (3.1.50414) does not get deleted when this new version is installed. Thus, in the AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Karamba3D folder I had two folders: 3.1.50414 and 3.1.50707 and I think this is what is causing the conflict that @matttam is talking about but the issue is with the Karamba installation or maybe it is a problem with Rhino package manager. Even when I downgrade Karamba in the package manager to 3.1.50414 the other folder for 3.1.50707 was not removed. I had to manually delete it and then it worked. @Wilson_Tarb look in the AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Karamba3D folder for any lingering Karamba installations and delete those.
I went through the steps in this page again, however I do not have any conflicting installations or files with the issue. Currently, it’s intermittent but I noticed that if I open a new grasshopper file, the issue does not seem to happen.
It seems to occur only if I open an old file. A rather strange problem.
Strangely, I do not have any lingering installations. I will see if there’s a way to replicate this issue as it’s rather intermittent for me right now.
This is the solution that worked for me with Karamba3D version 3.1.50707:
Uninstall Karamba3D via the Rhino Package Manager
Reinstall the latest version
Restart your computer
The problem seems to be rooted in the Rhino Package Manager YAK: When an old version of Karamba3D has been installed via YAK, and a new version is later installed - either manually or automatically (if the “Automaticaly update packages…”-option is enabled) - both versions remain in the package folder located at “%appdata%\Roaming\McNeel\Rhinoceros\packages\8.0” (for Rhino8).
In my case, I was using Rhino 8 with .NET Core v8, testing Karamba3D 3.1.50707 as the new version and 3.1.50414 as the old one. With both versions present in the package folder, Karamba3D would alternately load the new version with errors about every second launch of Rhino. The error messages pointed to the wrong karambafeb.dll being referenced.
After manually removing the older version from the package folder and fully restarting the computer (just restarting Rhino wasn’t enough), Karamba3D 3.1.50707 loaded reliably and without errors.
I plan to include a warning in the next service release of Karamba3D that alerts users when outdated DLLs are being referenced. This should help prevent the confusing error messages currently being encountered.
I was holding off on replying if this fixed it or not as I was trying to see if I could reproduce the issue even after doing this.
I think I figured out what is causing the issue. After doing the fix, Karamba in Rhino 8 runs with no problems. HOWEVER, if Rhino 7 is installed and grasshopper is launched before Rhino 8’s Grasshopper, Karamba in Rhino 8 will throw the same error again, even after Rhino 7 is closed.
Sadly, I am not enough of a tech person to offer a remedy for this solution, but this seems to be reproducing the error consistently enough.
Dear @Dan_Ki,
I’ve just uploaded Karamba3D version 3.1.50730, which should resolve the issue. Please give it a try.
Due to YAK-related constraints (see here), this specific version supports only .NET 4.8 and .NET 8.0.
— Clemens