I’ve seen this happen when Weaverbird has been installed using a different method prior to installing it with the package manager. Here are a few steps to make sure that there aren’t any other copies of Weaverbird being loaded.
- Open “Add or remove programs” (or type “appwiz.cpl” at the Windows Start menu and hit enter) and make sure that Weaverbird is not installed. If it is, uninstall it and restart your machine.
- Open Rhino and run the
_GrasshopperDeveloperSettingscommand and make sure that there aren’t any entries for Weaverbird. If there are, remove them by deleting the text on the relevant line(s) and hitting OK. - Open File Explorer and navigate to %appdata%\Grasshopper. Check in both the “Libraries” directory and, if it exists, the “6\Libraries” directory that there are no Weaverbird files (in particular Weaverbird.Gh.CommonSdk.gha). Make sure to check subdirectories too.
Now, start Grasshopper and, once loaded, check to see if Weaverbird’s panel appears. If not, restart Rhino and run the _GrasshopperLoadOneByOne command. This command will load each Grasshopper plug-in one-by-one, displaying the full path. The correct path for the plug-in, when installed via the package manager, is shown below.
