Plan of cutostom object is not represented properly in 2.13 internal version.
Vaupdate doesn’t work to fix this error. It makes every beam gone.
Thanks.
Hi @archist97, that’s weird. I experience the issue you say in VA 2.12.6 (wrong beam representation and beams gone after updating them), but not in the 2.13 internal version.
In my case, I think the beams disappear because I don’t have some GH add-ons you have used to create those beam styles. Could you attach the GH file you have used to generate them?
On the other hand, I see a different error in VA 2.13 version. The beams are represented a bit extended as they appear in 3D. I’ll report that to developers.
Hi. Francesc
Interesting. The GH definition is is already attached in the first posting. I don’t use any third-party plug-ins except VA component. I am using Rhino 7.25
Thanks.
@archist97 after I set the “Extension” and the “Extension limit” parameters to 0 for those beams, I don’t see this error anymore.
So this is what the model looks like now in VA 2.13 in my PC.
Which exact version of VisualARQ 2.13 do you have installed?
Francesc was referring about Grasshopper add-ons. When I opened your file in my Rhino, Grasshopper complained that I’m missing some of them: Pufferfish, Treesloth, etc.
I think I found the problem: If you open the file without VisualARQ being loaded, when Grasshopper loads the definitions, VisualARQ is not yet loaded, and you may get this error message: