VisualARQ users

To all,

I see there’s some activity on this forum for VisualARQ. I didn’t have any response from my last post to encourage new architectural users, apart from HQ. So I thought I’d revise my question for broader users as below, any comments will be most appreciated:-

New question - I was wondering if anyone now using VisualARQ can offer any comments to how they’re finding it, i.e. comments on use. Perhaps over any other CAD software they use or in combination.

Old question - I was wondering if anyone with experience coming from an Architectural CAD background in 2D or 3D & now using VA+R can offer any comments, i.e. advantages’ or disadvantages etc.

Over & out,
Clayton.

Hi,

I have many years of VectorWorks experience and went through a two weeks Revit course.

Joined an architect that needed me to import one of his buildings modeled in Rhino to VectorWorks to assemble them together into a BIM model. This worked reasonably well but we still had two models to be constantly updated back and forth.

Switched to Rhino plus VisualARQ (now referred to as R+VA) to replace the parametric tools from VW architect.
Since I was a beginner in both R+VA, it was sometimes overwhelming for me and it took time and effort to make the transition.
Now that I got the fundamentals and the feeling for R+VA+Layout (one also needs to understand the Layout features in Rhino to create the architectural sheets) I do not feel the need to come back to VectorWorks or switch to Revit.

VectorWorks and Revit are very similar tools by the way, both overloaded with features and with a bias towards orthogonal projection views (namely plans, sections and elevations).
Rhino is focused on 3D modeling. For designers, this changes everything.

Here are my R+VA pros and cons :

Pros

  • Rhino is powerful and stable
  • VisualARQ adds architectural features (like floor plan views and sections) and parametric architectural objects to Rhino
  • Architectural objects are suitable for both 3D modeling and 2D documentation
  • R+VA Import and Export to AutoCAD is simple and light (better than VectorWorks AND Revit :confused: )

Cons

VisualARQ is new (version 1.9) so :

-  Only VA objects (walls, slabs, roofs, beams, windows and doors) carry BIM information after exporting to .IFC format. Other geometries are also exported but will appear as generic solids.
  • The tools for 2D graphic presentation and documentation are limited when compared to VW and Revit. For example, there are no 2D drafting aids (like border and stamp for sheets, bubble grids and scale bar). They all have to be drawn manually.
  • There is no automatic coordination between detail numbers and sheet numbers.

The list of cons presented is mostly about cosmetics (lack of 2D graphic features), productivity (sheet coordination and stamp) and BIM interoperability ( .IFC export). All these items can be addressed with time without fundamental changes in the way Rhino works. The way Revit and VectorWorks were conceived in the other hand, makes it very difficult for them to become like Rhino.

The 3D capabilities of Rhino combined with the parametric architectural objects of VA are a game changer because they improve the design process

Conclusion : R+VA are great :smile:

2 Likes

This issue has already been addressed in VA version 1.9.4, it is now possible to assign IFC classes manually for odd architectural objects within Rhino/VisualARQ

1 Like

Continuing the discussion from VisualARQ users:

Thanks for your take up on this, most appreciated for potential new users.

From what I’ve seen to date, VisualARQ seems like a good product. I think R+VA is way more than an add-on & to get noticed more in the Architectural/Construction software arena, where I think it’s pitch should be, it may do better as a stand-alone product…!!!