VisualARQ 3 - Version 3.10 RC4 released

VisualARQ News
, , , ,
1

Hi,

VisualARQ 3.10 - Release Candidate 4 is now available for download.

:information_source:  NOTE: This is a release candidate (RC), meaning it is not the final version but has undergone internal testing and is considered stable enough for end-user testing. VisualARQ 3.10 is scheduled for official release on :spiral_calendar: Wednesday, June 3th, 2026

This release fixes most of the problems and crashes reported by users. Please report any problems or suggestions here or email us at visualarq@asuni.com.

List of changes since RC3:

Improvements (1)
  • Object: Tag:
    • 15625: Display Object Layer name in tags
Fixed Errors (15)
  • Attributes:
    • 15504: Wrong Section Boundary color in print preview
  • Crash:
    • 15486: Rhino crashes when deleting a slab
  • Display:
    • 14147: Control points are not visible nor selectable when are occluded by other objects in Hidden display mode
  • Grasshopper: Components:
    • 15522: No Roof Preview
  • Grasshopper: Style:
    • 15598: Hatch Explode Error in Grasshopper When using it in a Grasshopper Style
  • Help:
    • 15195: Link to VisualARQ Forum redirects to the wrong site
  • IFC:
    • 15746: Missing holes in slabs when importing an IFC file with the V4 engine > Parametric objects
    • 15745: Hidden objects are exported to IFC with the _Export command
    • 15722: Wall has no opening when exported to IFC using V4 engine
    • 15719: It takes a long time to export an IFC file
    • 12124: Transparent materials are not exported correctly to IFC with V4 Engine
  • Object:
    • 15713: VisualARQ objects disappear after the Autosave
    • 15547: Snap doesn’t ignore the occluded objects
  • Object: Curtain Wall:
    • 15773: Door doesn’t generate properly the opening in a curtain wall
  • Object: Views:
    • 15717: Make Section Hatch Color the Print color in View overrides

Download links:

Previous version:

Enjoy!

2

I am trying out visualARQ3. Every time I open a Rhino file, Grasshopper is preloaded, which makes the process of opening files slow. I guess this might be a function of visualARQ3 starting the GH part. Is it possible to change this to load during the process of starting Grasshopper? That way, it won’t affect the speed of opening files in Rhino. Thank you~

3

Hi @_zachary VisualARQ uses Grasshopper in the background to generate some of their parametric objects, and for that reason it loads it when you load the program. This is necessary otherwise you might open VisualARQ files with objects that would not show up in the model.

And it has worked this way since VisualARQ 2. Of course, the more Grasshopper Add-ons you have installed, the slower Grasshopper will load.

We can investigate if it is possible to load Grasshopper only when necessary (when detecting or inserting objects driven by Grasshopper definitions).

4

It would be ideal if the GH function of VisualARQ could be automatically activated when launching Grasshopper from Rhino. This is exactly what I need. Thank you very much!