Grasshopper Style Input Parameters Issue

I am experimenting with using VisualARQ Dynamic Blocks for naval architecture. Currently, I’m working with a concept that takes a planar path curve and a deck surface as geometry input parameters, along with a bunch of numeric parameters, to generate a curved bench that extends to the deck. I think it makes the most sense to make this a VA object by creating a Wall grasshopper style, considering that the input is a plan curve that I want to be able to manipulate.

So, I go to the GH wall style wizard, select the GH doc, and proceed through the steps. But, I am having some issues with the input parameter for the deck surface. This is the behavior I’m experiencing:

  • (GH) Geometry Param → (VA) Doesn’t show up in Param list at all
  • (GH) Surface Param → (VA) Shows up in Param list with type “Unknown”, Can’t any pick object
  • (GH) BRep Param → (VA) Shows up in Param list correctly, allows picking, but won’t allow picking the surface, but I can pick a closed BRep.

The VA docs suggest that the Surface and Geometry Params should both be a valid input params for a Grasshopper Style. Further, I would think that the single surface would be able to be cast to a BRep, so it is unclear to me why I can’t select the surface.

Can anyone offer some insight about how these input params are meant to work?

Here are the documents I’m working with:
VisualARQ Bench.gh (45.9 KB)
VisualARQ Experimentation.3dm (220.7 KB)

System info

Rhino 8 SR22 2025-8-5 (Rhino 8, 8.22.25217.12451, Git hash:master @ 96429e6361004c775cd83973f2148f3943b5e512)
License type: Commercial, build 2025-08-05
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 32GB)
.NET 8.0.14

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA RTX A2000 (NVidia) Memory: 6GB, Driver date: 8-21-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 581.15
> 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
GPU Tessellation is: On
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: 8-21-2025
Driver Version: 32.0.15.8115
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 6138 MB

Rhino plugins that do not ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\VisualARQ.rhp “VisualARQ”
C:\Program Files\Rhino 8\Plug-ins\Tibidabo\Tibidabo.rhp “Tibidabo”
C:\Users\domen\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\Speckle.Connectors.Rhino8 (2153799A-0CEC-40DE-BC3A-01E5055222FF)\Speckle.Connectors.Rhino8.rhp “Speckle” 3.8.0.0

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

Hi @Domenic_Gallo you a right. There’s an error here. It looks like the Surface and the Geometry Params as input parameters are not correctly detected when creating Grasshopper Styles. We will revise this behavior and fix it in future versions/updates.

1 Like

Hi @Domenic_Gallo I let you know that we have just published VisualARQ 3.7 RC1, which lets you select an open polysurface as input parameter for your Grasshopper Style.