VA3 BETA: Moving VA Style Object makes it disappear

As shown in the video. Moving the VA Style Object makes it disappear, however, saving and reopening the Rhino file solves the problem… I don’t know yet how to reproduce this problem every time, but it’s not new to the Visual ARQ 3, it was also present in the previous version.
If I could choose, I would rather like this bug to disappear instead of my objects.

Are you aware of this problem? I don’t remember if I reported it in the past.

This also happens to my Grasshopper styles in VisualARQ 2 once in a while, mostly with annotations and furniture styles. Reloading the style file recovers them. Not an acceptable solution, but maybe it helps with finding the bug.

Hi @Czaja,

This is definitely not normal. Personally, I have never seen this error with Grasshopper styles.

My first guess is that the definition uses some component (native or from some plugin) that interferes with the operation of VisualARQ objects.

Could you send me to visualarq@asuni.com a 3DM and the GH definition of one of these styles?

Thanks,

Enric

I’ve sent you the file. I hope we can get rid of this bug soon. Unfortunately, I don’t see any pattern yet so I can’t say how to reproduce it.

Can confirm - also having this issue…

@enric - any updates?

Cheers

@Robert_Xie is this happening with a “Grasshopper style” object? can you share a sample model?
Which VisualARQ version are you using?

I’ve run into the same issue on the current version using grasshopper styles. It seems to happen randomly. All the visualarq objects of that style disappear. But if I have multiple styles from using the same grasshopper script, only one style disappears.
Sometimes I can reload the grasshopper script within the style dialog and it comes back, sometimes I close and reopen the file for a fix.
Here is a file with a grasshopper slab. It has an incorporated turn down, which seems to be a little buggy. Probably because of the solid union component. Regardless, I’ve also seen it completely disappear on me similar to what is mentioned above.
240618_TurnDownSlab.3dm (3.2 MB)

Hi @arcus, This is what I see when I open your file.

I haven’t been able to make the slabs disappear. I’ve just noticed that some slabs are hollow and others don’t. But I guess this depends on the GH file and the shape of the slab boundary.

Yea I think the boolean command in grasshopper doesn’t always work. It especially seems to break when adding or removing boundary curves. There may be a better way to structure the file.
Here is the gh file
Slab-ConcTurnDown.gh (27.8 KB)

Regardless, I have noticed that these slabs, along with other grasshopper based styles, will sometimes disappear, similar to Jakub’s issue. But I also don’t know why or how to consistently reproduce the issue.

I have the same issue even in a simple demo file with just one table. Hope it helps to find the bug.

And here my System information:
Rhino 8 SR8 2024-6-11 (Rhino 8, 8.8.24163.12481, Git hash:master @ ded4d86ca901dbeaf13ee84f79b3e91b22da4880)
License type: Studentenlizenz, build 2024-06-11
License details: Cloud Zoo

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 48GB)
.NET 7.0.0

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce GTX 1080 Ti (NVidia) Memory: 11GB, Driver date: 6-8-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 536.23
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 6-8-2023
Driver Version: 31.0.15.3623
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB

Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Lands.rhp “Lands Design”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Users\Leonard\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\Lumion LiveSync for Rhino (839d6175-32d1-4ffe-a0a4-b7fb43cf0ff5)\2021.3.25.899\Lumion\Rhino 7.0\LumionPlugin.rhp “Lumion LiveSync for Rhino”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
C:\Users\Leonard\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\BoltGen_py (283dd9db-bcac-ab3c-9b9a-6f41eaf6160f)\1.0.6642.13019\BoltGen_py.rhp “BoltGen_py” 1.0.0.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.8.24163.12481
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

VAQ 3 beta - Rhino 8 - table disappear.3dm (92.7 KB)

Same here! Grasshopper styles tend to randomly disappear. Solution is always different: Reloading the file, reloading the Grashopper script, or sometimes VaUpdate command, if I somehow manage to select the invisible object.

I experienced it on Annotations, Windows and Furniture styles.

It is such a pitty, despite this I am in love with Grashopper styles. But this bug makes them unusable. I gave up on creating my own library of Grashopper styles in VA3 Beta, because it disappeared more often than it worked…

Hi @MichalKrizo @leonardruven @arcus… I wish I could help you on this, but I’m unable to reproduce this problem.

Do your GH files of these GH styles use third-party add-ons? Are they loaded when you play with these objects?

If you save the 3dm file after reloading the gh definitions used by the gh styles, and refreshing the involved objects in the model, and open it again, does the problem persists?

Same here, I added va stock bed to the plan and after moving it disapears. I can select this by vaSelFurniture command but it dosent show nowhere.

@kristjan.tolk if you refresh all the involved objects (vaUpdate), so they show up again, save the 3dm file, and open it again, does the problem persist?

Do you have any third-party Rhino plug-in or Grasshopper add-on installed on your system?

Enric

D5 is the only plugin i have installed.

VaUpdate helped, thanks!

Its very random how sometimes by copying from one level to another whole model disapears.

@enric @fsalla

VisualARQ 3.2.0.19334
Rhino 8.14.24332

System Info

Rhino 8 SR14 2024-11-27 (Rhino 8, 8.14.24332.15001, Git hash:master @ 88c7b9834e34675b017e14ad488ef774e444793d)
License type: Educational, build 2024-11-27
License details: Cloud Zoo

Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 64GB)
.NET 7.0.11

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA RTX A3000 12GB Laptop GPU (NVidia) Memory: 11GB, Driver date: 6-10-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 538.78
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA RTX A3000 12GB Laptop GPU (NVidia) Memory: 11GB, Driver date: 6-10-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 538.78
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port

Secondary graphics devices.
Intel(R) UHD Graphics (Intel) Memory: 2GB, Driver date: 8-19-2024 (M-D-Y).
> Integrated graphics device with 4 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: Off
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 6-10-2024
Driver Version: 31.0.15.3878
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11520 MB

Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\RhinoToGrasshopper\RhinoToGrasshopper.rhp “RhinoToGrasshopper” 1.0.0.0
C:\Users\Czaja\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Synapse\0.4.0\SynapseRCP.rhp “SynapseRCP” 0.4.0.0
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Users\Czaja\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\Bella (813de3fb-18eb-405f-bfcd-b0b4d3da91fb)\24.2.0.0\bella_rhino.rhp “Bella” 24.2.0.0
C:\Users\Czaja\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\Crash\1.4.2-beta\Crash.rhp “Crash” 1.4.0.0
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
C:\Users\Czaja\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\Crayon (39629248-4fa6-47b8-83c7-745a7efea259)\1.2.0.0\Crayon\Crayon.rhp “Crayon” 1.0.0.0
C:\Users\Czaja\source\repos\EtoDockableApp\EtoDockableApp\bin\Debug\net48\EtoDockableApp.rhp “EtoDockableApp” 1.0.0.0
C:\Users\Czaja\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\SubstanceImporter\2.0.7\Substance.Win.rhp “SubstanceImporter” 2.0.7.0
C:\Program Files\Rhino 8\Plug-ins\Karamba\License\Karamba3D_LicensePlugin_Rhino8.rhp “Karamba3DLicense”

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.14.24332.15001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”


I have discovered a way to reproduce this nasty BUG. I hope that it is the cause of the problems reported earlier, and that you will be able to reproduce it and get rid of it once and for all.
I am not 100% up to date with what is known about the problems with GH Styles, but since they are still there, maybe this one will be new to you. All steps are visible in the video.

The problem occurs when we want to change the Curve input, but we interrupt this operation by pressing Escape on the keyboard. Despite the Curve input being By Object, not only does the edited object disappear, but it also affects another object from the same style, which also disappears when we move it.

Troubles start at 01:00

PS
I can still select VA Elements via SelAll but they are invisible, even after trying to give them new Curves and refreshing (Update Selected Objects) they do not show up in the Viewport but they do show up in the Rhino Command Prompt.

Hi @Czaja thanks for the video! I can’t still reproduce this error, even though I tried to follow exactly the same steps as in your video. Until we don’t reproduce it, we won’t be able to figure out what’s happening, unfortunately.