Every time I open Rhino, the message appears that my file knows 3 unknown things.
I am attaching a screenshot + my template file
VA templet.3dm (6.8 MB)
Hi @11170 you may see this message when you open a file in Rhino with VisualARQ data before VisualARQ has been loaded. Try to load VisualARQ before opening this file (just by running any VisualARQ command, like “vaWall”). You shold not see that message again.
In any case, I recommend you to update VisualARQ to the 3.8 version, which includes a solution for this problem (mostly when you open Rhino with double click on that file).
Hello,
i double click to open my file and i still get error.
file was saved last time with previous version.
Hi @ng5_Alex, thank you. We will revise this behavior.
Possible solution (in case it helps someone else):
In my case, the error was caused by disabled VisualARQ components in Grasshopper.
I had some VisualARQ (GhVa) components in Grasshopper that were disabled, but the Rhino file still contained objects created by those definitions. When Rhino opened the file, it tried to load those GhVa plugin objects, which triggered the warning message.
After enabling the VisualARQ components again (or removing them) and recomputing the Grasshopper definition, the problem disappeared.
So if you encounter this error, check whether your Grasshopper definition contains disabled VisualARQ components that have created objects in the Rhino document.
Hi @Asiak, thanks for your message.
We are still revising how to fix this issue. But in order to prevent it, just need to ensure VisualARQ is loaded before opening Grasshopper (no need to disable it). To do so, instead of opening a file by double-click, open Rhino, load VisualARQ, (by typing any command) ( * ), and then open the file.
( * ) This step might not be necessary.
Hola,
Lo que quería decir es que tenía algunos componentes de VA desactivados en mi definición de GH porque estaba haciendo pruebas. Al eliminar esos componentes desactivados de la definición y recrear el style que estaba utilizando, el error desapareció.
Un saludo y gracias por tu genial trabajo.
Hello,
What I meant is that I had some VA components disabled in my GH definition because I was doing some tests. After removing those disabled components from the definition and recreating the style I was using, the error disappeared.
Best regards, and thank you for your great work.
1 Like