Related to stair

Hi @fsalla,

Is there a way to achieve this at current stage on VisualARQ?

I’m using the latest VisualARQ.

Also, current version and 2.0 cannot generate angled wall. What users have to do is building a wall on Rhino and translate it to VisualARQ object.

Please add this fuction to 2.0


Hi Kev,
The video shows how to subtract a solid from a VisualARQ object (a stair in that case) without loosing its parametric properties. The only way to subtract a solid from a stair up to the 1.9 version is to explode the stair object (so it turns into a bunch of polysurfaces) and run a boolean difference with the solid.

Regarding the option to create angled walls, why do you need to convert the Rhino geometry into VisualARQ walls? If you need it to insert doors and windows, it’s all right, you can run the vaWallFromSolids command. But if you just want to show these walls in plan and section views, you don’t really need to do the conversion. Just assign projection and section attributes to the Rhino solids, and they will appear in the drawings.(
In case you need to convert them for exporting to IFC purposes, you can use the IFC Tag feature. (
Best regards,

1 Like


Here is the problems I talked about.

Example file: test.3dm (642.3 KB) (VRQ object)

“Regarding the option to create angled walls, why do you need to convert the Rhino geometry into VisualARQ walls?”

This is how VRQ behaves so far. What I meant was why not just simply avoid conversion process (Rhino solid to VRQ object)?
So far, VRQ can only create vertically straight walls.

Also, why inserting windows and doors cannot work on converted walls? (Please try inserting those to my example file)

Problem 2: VRQ misreads section view.

Problem 3: Can block object convert to VRQ in the future?

Hi @anon66739973,

  1. I’ll report the issue with that section view to VisualARQ developers and get back to you when they can fix it.

  2. It is not possible to insert properly doors and windows on those leaned walls created from a solid because VisualARQ openings can be only placed vertically so far, and therefore they can’t orient on wall surfaces if they are not vertical. Hopefully in future VisualARQ versions it will be possible to insert openings oriented on walls with non-vertical faces. On the other hand, when you create a wall from a solid, you need to define a wall path from a planar curve. That means that in your project you should create each wall side from a different solid so each one has a different path. But it’s not really practical.
    So in your project design I think it is better to work with Rhino geometry (for the walls and openings) and use Rhino commands to add openings). Later on you can assign section attributes for its 2D representation in plan and section views.

  3. You can already convert blocks into VisualARQ objects in the current version. This option is available for the Opening, Door, Window and Column objects. In the upcoming 2.0 version it will be also available for 3 new objects we will introduce (the “Furniture”, the “Element” and the "Annotation objects).

Kind regards,

1 Like

Hi @fsalla,

Thanks for the quick response.

  1. I think It’s OK to have walls and windows are not vertically oriented as long as in the drawings ARQ can represent. In my example file, what I was trying to achieve was creating openings in 3D object and call out those elements in the drawing. (But, Of course the best is to have them in 3D model as well, which Revit cannot do it as far as I know.)

  2. Block objects are Rhino blocks. I will further explain this part when I have time. I will send you a study model privately when I get back to here.

  1. When you create plans and section views in VisualARQ, every kind of geometry, no matter if they are VisualARQ objects or Rhino objects like curves, meshes or polysurfaces), will appear in the 2D drawings.
  2. Ok, send the model to to discuss this further.

Revit has a few different methods of creating non-vertical window elements; sloping curtain wall, roof based window and pretty sure you can do wall based window and host it within a model-in-place wall…
all of them tag (though curtain system tags as such).
All kinda feel workaroundish though…

@anon66739973 I get back to this old post to mention that we fixed the bug that was generating wrong section fills in Section Views in that file. You can try this with the current 2.2 version.

1 Like