VisualARQ 3 - Version 3.8 RC4 released

VisualARQ News
, , , ,
1

Hi,

VisualARQ 3.8 - 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.8 is scheduled for official release on :spiral_calendar: Wednesday, February 4th, 2026

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

Here is the list of changes:

Fixed Errors (2)
  • Grasshopper: Components:
    • 15469: Crash after referencing a building in Grasshopper
  • Object: Plan View:
    • 15439: Guides in hidden layers are showing in Plan Views

Download links:

Previous versions:

Enjoy!

2 Likes
VA3 - Guides are visible on Plan view, even when shouldn't
(bug) Plan view crash
2

With every release, I’m hoping to read about improvements to georeferencing. I normally model close to the origin, but am typically expected to provide ifc models in a Gauss-Krüger or Lambert coordinate system, where coordinates are hundreds or even thousands of kilometers from the origin. In my opinion, it would make sense to set this location in IfcProject or IfcSite.

When setting ModelBasePoint to something like 3500000,5000000 in the Rhino model, this offset gets exported correctly by VisualArq in IfcProject (so all geometry should be translated by this amount, which is what I want). But then at the same time, VisualArq applies the inverse to IfcSite. As a result, my design will appear exactly where I modeled it (close to the origin) instead of on the intended location.

As combining models from different design parties is one of the main reasons to work with ifc files, I am quite puzzled that I would have to manually edit ifc files in a text editor in order to get the georeferencing right. Is there perhaps some other possible workflow that I am missing? Is there a way to switch off the inverse transformation that is applied to IfcSite?

1 Like
3

Hi @pistepilvi excuse the late reply.
VisualARQ still doesn’t take into account the ModelBasePoint when you export a model to IFC. It takes the World Origin of Coordinates instead. We plan to fix this in one of the upcoming updates.

Why don’t you use the EarthAnchorPoint command to georeference your model?. Changing the ModelBasePoint into long distances may cause having models with the geometry too far from each other and get display and model precision issues.