I have my own grasshopper script for VAwindows and VAdoors and i have a problem where when i open up a file with my own VAwindows and VAdoors they dont read the wall hosts thickness even if they are set to do this.
Heres what it looks like when i close my file:
Then, when i open the file all windows and doors will take on the custom wall width only found within the grasshopper script(in this case 400mm) which is not the actual wall width in the rhino file.
When you open your file, and the window position is wrong, try to run the vaUpdate command on it (instead of editing the window style). Does that fix the window position?
Does the problem persist if you save the file and open it again?
How are you opening that file? Double click on the Rhino file? from the Rhino Open command? dragging the file in the Rhino interface?..
The VaUpdate command doesnt help/work.
If i reload the grashopper definition and finish editing the window, thus making it update to register the wall host thickness, and then save, and then close, and then open by double clicking the file it defaults to not reading the host wall thickness again.
If i open an empty rhino8 file and from there open the test file that i sent it works! it registers the host wall thickness.
If i drag the file unto the rhino viewport and choose open - it also works!
I made it a habit to first open rhino and then open the rhino file that contains visualarq items, because with double clicking besides the above error i am getting warnings for missing plugins etc.
@Jens_Jacob_Melhus_J1@ng5_Alex thanks for your feedback regarding this issue. It’s clear that the issue occurs when a file opens in Rhino before VisualARQ has loaded. This seems to happen when you double-click a Rhino file. We’ll review this and include a fix in an upcoming update. I’ll let you know when it’s ready.
