Last year, I created a Grasshopper definition in Rhino 7 using VA2 components to extract data from VA spaces, and everything worked perfectly.
However, after opening the same definition in Rhino 8 with VA3 components, I encountered a strange issue. When I click “Update Property” on the Grasshopper components, the “cable” connecting the components turns orange, indicating an error. To resolve this, I have to manually recompute the definition each time.
Has anyone experienced a similar problem or knows how to fix this?
Is the issue in the visualARQ Pipeline not updating the space? If you disconnect the pipeline, manually set one space in the Space component, and then change your properties does it still glitch on you?
Another thing to check, it looks like you are selecting a particular index from a list and then doing a Match Text for a pattern called “areaFinestre”. You may want to cut out that List Item component and jump straight to the Match Text. For instance, my number 24 is called “frameFinish” and 25 is “hardware”, so the rest of the script runs null because it can’t match the text.
Hi @Alessandro_Barbisan got your file, thanks! We will investigate if we can avoid having to recompute (manually) the definition after pushing the Update Property button.
Hi @fsalla
I have noticed that even after the latest update, the definition I created is still not functioning properly. Specifically, I need to recompute it manually in order for it to work.
I would like to understand whether this issue is inherent to the definition itself or if it is related to a specific component.
Thank you in advance.
