Hi @alaasaba, the log file is from a different run. Everything looks correct in the log file. Are you using the latest version of the Rhino plugin? It might be similar to this one:
The other case that we have seen this error is when the C drive is full, and you run out of storage.
I’ve reviewed the post you shared and made sure that I’ve checked all the needed steps to resolve the issue: plugins are updated, the software is up-to-date, and the C drive has sufficient space. However, the error persists.
I must admit, I made an oversight regarding the log file—I realized it was from a previous run. My apologies for the confusion on my part.
So, the failed pollination run doesn’t seem to generate a new log file either, making me unsure about how to proceed further.
Could you guide me on what else I might need to check or troubleshoot?
So far, it seems that only LEED-related recipes fail the moment I start the simulation. At least the energy-related recipes appear to run without any issues.
Please let me know if there’s anything specific I should check or adjust to resolve this.
So it fails in the very beginning of the simulation? Does it happen with version 0.3.8 of the recipe? Here is a short video showing how to quickly change the version of the recipe.
Hi all,
I’m having the exact same issue here. This time with LEED Daylight Option 1, though. I’ve attached my log file for reference. Only difference perhaps is that it happens at the end of the simulation for me.
Kind regards,
Marc logs.log (100.7 KB)
You have to update the core libraries to run version 0.1.4 of the recipe. Using LB Versioner in Grasshopper should do it. If you are not able to do that, then you can still use version 0.1.1 – the results between the two should be same.
Thank you for your quick reply. Using LB Versioner seemed to do the trick, thank you. I updated my Pollination install using the newest version of the installer and used version 0.1.4 already, but wasn’t aware that the Pollination component also utilizes the LB Versioner component. I thought that was just for the LBT GHPython-based components.
Thanks again!