New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wind Factor Component version 4.2 is throwing error in Annual wind study template #9
Comments
Could you please check if any inputs are |
@kastnerp I had checked the script again thoroughly but the issue persists.. This issue also persists in outdoor comfort template. I was checking the indoor template too. It is also throwing error. Last release was working nicely, this release (ver 4.2) is breaking lot of eddy components. Even pressure template is not opening in grasshopper. For your info, i am using latest version pf rhino 8 https://drive.google.com/file/d/1YstEemTdg0jECmd5NqKiN1Jty3iP95Bi/view?usp=sharing |
I can confirm the problem. Seems like R8, once again, introduced breaking changes regarding how the UI behaves. I will recompile the latest version for R7 in the meantime. |
That would be great. @kastnerp , so for now the current version will not work with R8? |
First off, I just published The unit tests all passed, so it likely has to do with how the UI interfaces with the component logic. I will have to investigate further. |
Ok. Till then have to install Rhino 7 again. Will test in Rhino 7 and let you know if I encounter any issue! |
Hi, Do we have any update for Rhino 8? |
Hello @kastnerp I'm sorry to disturb you. I'm running version 0.4.2.1 of the component in Rhino 7 and still encountering the same error. May I ask what the reason might be? |
This should be fixed now. Will be uploading |
I updated the template for annual wind analysis to 4.2ver and the simulation ran successfully. I could visualize the wind vectors for all directions. But when I am trying to run wind factor component throws error as " Object reference not set to instance of the object". Kindly assist in solving this
The text was updated successfully, but these errors were encountered: