Thanks Chris! Resolved the issue
Thanks, It worked.
Before this, although I was going through all of the installation guid steps, I was receiving this error:
Solution exception: Failed to import honeybee: No module named honeybee.hbsurface
This one worked for me
Hi Chris, this works fine for me. Thanks very much!
thanks
it worked perfectly,
just one question, I’m missing some icons like radiation rose how to find them?
Hi @chris,
I needed to do this in two computers because it didn’t work normally in any of them and the process works in both cases.
But in my computer once I try to runrecipe in the example for the Daylight factor (after installing radiation and openstudio) the window of the queenbee open an closes without giving any result of the analisys.
Do you have any idea what could be happening?
Thank you Chris 
It works for me too.
Radiation Rose is not yet in the LBT plugin. It should hopefully be there in the next stable release.
1 Like
Thanks for clarification, anyway I downloaded the legacy version.
Keep the great work
Thank you for your workaround, however I do not agree with:
I find that hard to believe. APPDATA is like a default environment variable in Windows. If I enter %APPDATA% in the address bar of Windows Explorer, it goes to C:\Users[USERNAME]\AppData\Roaming
If I type echo %APPDATA% in the command prompt it returns C:\Users[USERNAME]\AppData\Roaming
I tried to install the new Ladybug Tools 1.1.0 on two laptops and one desktop computer and all failed. I think something is wrong in the installer.
Hum, installer worked fine for me after I got admin rights to my computer. It was impossible to install before and what Chris showed seems to be exactly the workaround. What is the issue you are getting into when installing?
In all my cases, having admin rights on my personal laptops and desktop, I first had to add C:\Users\[USERNAME]\ladybug_tools\python\Lib\site-packages in Rhino Python options to get set_python_path.bat running properly and to get Ladybug Tools components working in Grasshopper.
In my cases Ladybug Tools is not automatically added to the Rhino Python Path. I had to add it manually.
FYI, I think we have identified why so many people have had to manually specify the python path. It seems that Rhino doesn’t create the settings file that the installer tries to edit if someone has never dropped a GHPython component on their Grasshopper canvas before.
We have added some code into the development version of the LBT plugin that creates this settings file if it does not exist. So, when we release LBT Grasshopper 1.2.0, people should not have to use this manual workaround anymore.
1 Like
This thread helped out lot, finally got Ladybug running! Now its doing this thing where it keep trying to update to new components. I’ve deleted the dot_net folder and it wanted to restart Rhino/Grasshopper again after that and it’s still showing up like this. Do I ignore it now or is something wrong?
Hi Chris, thanks a lot for the information.
For some reason, there are still warnings/errors when installing the LBT, any idea?
Thanks a lot, Chris.
Regards,
Chris
Yes, @IvanD ,
You can just ignore it. We haven’t updated the .gha file since the first time we created it so you are not missing out on anything. But, when we eventually update the component, you would have to delete the dot net folder, restart Rhino/GH and re-run the versioner to get the new file. This is just the only way to update the .gha files given how they work in Grasshopper. But we’ll put a note in release notes if we ever update the dot net package.
@gqia002 ,
It looks like a firewall is blocking the installation of packages from PyPI (the Python Package manager). I would either get your IT to add an exception for PyPI or just have your IT buy a single-click installer from us, which will probably save everyone a load of time.
1 Like