Summary: It took me to recompute the solution 5 times to get where Human in V7 takes me instantly and ALWAYS (I have never experienced issue of this kind).
I have been reporting this issue first days Import Content was available, seems nothing has changed over the years, only some vague answers āit works for usā.
This is the exact reason I halted upgrade V7 to V8 for a whole company. Donāt make me do it for V9.
Please treat is seriously. My previous post about offset bug got completely ignored.
PS I restarted the script and recomputed it ca. 10 times, still one mf wonāt work
Are you able to share this script here or upload it anonymously here@Piotr? System info would also be excellent in helping me repro and ticket this bug
This is huge: GH script + 2 Excel files + 850 Rhino files - shrinking to some usable fragment would cost me a day or so.
I will try to make a zip package of the whole solution and send it to you. Please give me some time.
I could reduce 850 to 50 required to run the script without hiccup, but what if the problem lies in the size of the library? You will have to figure this out.
PS system info has nothing to do it. It happens on my two machines which were built 8 years apart, and run on a different systems.
Iāve been there before. I have a very large definition too which imports dozens of files in Grasshopper. In my case the Import Model Block component fails randomly and usually my quick fix is to copy paste the component and then it works again. I have tried to create a reduced sample file but the import never failed on a small file here.
I asked about this internally and tried reproducing. One thing that is important to note is that Rhino 8/9 runs in dotnetcore by default which is a bit different and may have issues. Youāll want to be running in dotnet framework for that script as itās using COM interop forExcel. SetDotNetRuntime is the command you need.
Changing the runtime does not make a problem go away. It is as bad as before or even worse as only 3 / 11 are loaded.
Besides, are you going to ask each user to fiddle with this setting to make the component work? I strongly advise to rewrite it, or find Andy and ask him how he did it, put some money on the table and take his solution.
Iām trying to repro your bug, find it and get it fixes, Iām suggesting things that may help you resolve your problem for now in case a bug fix takes time. If you see no difference between netcore and netfx that is useful information for us.
I have tried different scenarios: with Excel closed or opened. I tried launching the script and loading the blocks with another True trigger. Nothing makes change.
Usually, pressing recompute multiple times makes them all work, but, sometimes, the one that worked before recomputing turns red after. There is no visible logic to it.
One thing is constant - the Import Content with only one article (always the same) to load never fails.
@CallumSykes the import content component is proving to be highly unreliable. A grasshopper script I was working on just crashed and when I reopened it, the import content component no longer imports and just gives a āFile could not be readā error message. I have no idea what is wrong and how to diagnose the error. It genuinely seems to be working by some randomness as you can see from this screenshot:
I have uploaded relevant stuff on this link. Please let me know what can be done, this component is highly pivotal for our workflows and these constant problems are starting to become a real pain.
This is being looked into for 9, but I notice you are on 8, Iāve created you a separate ticket as I believe it is a separate issue that needs addressing.
This time I noticed that it happened after I asked my colleague to make changes in the .3dm on her system and save the file. I reconnected the Boolean Toggle to the Import Content that is on the bottom and it gave an error. The error did not go away even after restarting the file.
I had to put a new Import Content and not expose the Import Boolean and click on the default Import Button and then it finally workedā¦
