Hello @wim
Indeed, I consistently utilize the DotNetFramework for my runtime environment, primarily due to my extensive use of Rhino.Inside Revit. It seems I’m indefinitely stuck to it!
Update:
I got Honeybee Annual Daylight Hours + ASE recipes to work by doing the below:
1- completely uninstall Ladybug Tools installed from Food4Rhino, delete all the libraries, dependencies, radiance, open studio.
2- install pollination for grasshopper. (I like the new installer way more)
3- Load the plugin from rhino manager by pointing to the rhp placed under the rhino 7 packages.
4- restart. working for now (except with the stamp on the icons which I don’t care about that much).
Now It is more powerful with Rhino 8 , better display modes, and the new Grasshopper objects makes it easier to reference, update and bake rhino objects within grasshopper,
Ah, now I think I know why you got that error and I actually don’t think that it’s related to Rhino 8. It’s because the latest Pollination installer is using Python 3.10 but you had an older Food4Rhino installation that you’ve been updating with the LB Versioner, which was still using Python 3.7. In other words, I think it’s the same issue that this user experienced on Mac (where we have no single-click installer):
You’ll see that you get the same error message. I think the fix I pushed yesterday should also address your original case. But using the Pollination single-click installer is also a sure way to always fix it.
And, as for this:
I think we’ll hopefully find a solution to get rid of this before Rhino 8’s official release. We’re working with Ehsan on a solution now.
@chris
I witnessed this issue few months ago (before the pollination install), I think it is related to the new Cpython editor that installs python 3.9 alongside ironpython. not sure what is the root cause of this conflict.
anyways I really appreciate your team’s work on building ladybug as .rhp package than the previous assortment of tools, it makes it easier for everyone to install and move on.
cheers,
@eirannejad and I just figured out what this issue is and it results from the fact that loading the new Python capabilities of Rhino 8 overwrites the PYTHONHOME environment variable, which messes up all of the LBT components that use the native Python subprocess module to call the Python that we ship with Ladybug Tools. So, before the Rhino 8 Python libraries are loaded, it all works but, afterwards it is broken.
Thanks to @eirannejad , I know how to fix it now and I’ll begin pushing some fixes in the next few days. It may take a bit of time to track down all of the cases where we use subprocess. I’ll post back here once all of the places I know of are fixed.
I finished integrating all of the fixes into the latest development version of the LBT plugin, which is available with the LB Versioner. So there’s no more OLD tag in Rhino 8 and all of the cases where we use subprocess to call an external Python library succeed.
I’m just waiting on a few updates to our single-click Pollination installer and then I’ll make an official post that includes an updated installer on Food4Rhino
Step 1: go to C:\users<YOURNAME>.rhinocode
Step 2: delete the folder called something like rhpython39
Step 3: download and install Ladybug tools 1.7 from food4rhino
Step 4: run the versioner and restart rhino
i’m still getting this issue
Reinstalled a billion times, about to go into a meltdown since I upgraded to v8 from 6 JUST to try to fix my issue I had prior…
I don’t think there is a Butterfly 1.7. This topic discusses Ladybug Tools + Honeybee + Dragonfly.
do me a favor and let me know
1- Place a component from Ladybug (not Butterfly)
let me what version is reading on the bottom of the component
The latest development version of the LBT Plugin that you can get with the LB Versioner works in Rhino 8 but the LBT 1.7 stable release does not work in Rhino 8. I’ll push a new installer to Food4Rhino in the next week or so that is fully compatible with Rhino 8.
Butterfly was last released in 2019 and has not been maintained since then. As you see on Food4Rhino, it was only ever tested in Rhino 5 and 6. Granted, I think you can likely get Butterfly to work in Rhino 8 if you copy this folder:
Sorry to bring this up. But I couldn’t figure out how to succesfully installing Ladybug Tools on Rhino 8?
I also checked this post below:
But wasn’t sure if there is a solution yet.
I tried with the Ladybug Tools 1.7.0 on food4rhino, still facing the Fatal Python error: init_fs_encoding issue. So I have no access to the versioner inside grasshopper. Because there is no ladybug tools existing inside grasshopper toolbar.
@tay.0 No, I need it for my other plug-ins, sorry. I was looking for a way so Ladybug Tools and python 3.9 can exist the same time. Or do you mean remove it temporarily and paste it back afther installing ladybug tools?
