-
Notifications
You must be signed in to change notification settings - Fork 4
Troubleshooting
Max edited this page Aug 7, 2021
·
8 revisions
- Make sure you have Rhino 6.34 or higher.
- Also, Hive needs to be running from a Windows OS. Should you have a Mac, you need to run Rhino and Hive via a virtual machine, such as “Parallels” or “VMWare”.
- If you’re running on a Windows OS and the installation did not work, try the following: Navigate to your Rhino Grasshopper components folder by entering “Grasshopper folder”, followed by “components” into your Rhino command line and the correct folder will open up. If you find "Hive.Core" and "Hive.IO" files in that folder, the installation was successful. If you still can't use the Hive components, however, check on each of these .gha and .dll files with a right-click if they are locked. Make sure to add a tick on the tick-box “trust file” (or similar). If it still does not work, please contact us via e-mail ([email protected]).
Reinstalling Hive might solve some issues, so always a good place to start!
You may get an warning such as "GH library components were developed against a newer minor version of Grasshopper SDK" when running in Rhino 6.
- Upgrade Rhino 6 to the latest version (6.34 as of writing) as hive will be compiled against this version of the grasshopper SDK.
- Use Rhino 7
The dome used for rapid solar calculations may appear all obstructed even though that is obviously not the case in the model.
- Make sure that the point that the sky dome is pointing towards is placed outside of the building. Otherwise may interpret that point is inside and therefore fully obstructed.
When opening the building input form (hizard), the grasshopper script will re-run upon closing, which can be annoying when one wants to only look at parameters and check them frequently.
- Unfortunately no real solution at the moment, we are working on it!
- Workaround is to disable the HiveInputs component for now and only enable it when you want to simulate.
Let us know! Create an issue and use the "Bug report" template on github and describe with images:
- hive release version, rhino version
- expected result
- actual result
- steps performed