# VisualARQ 3 - Version 3.11 RC2 released

**URL:** <https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079>\
**Category:** News\
**Tags:** architecture, plugin, bim, visualarq, update\
**Created:** [July 22, 2026, 10:11am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079 "2026-07-22T10:11:04Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![enric](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/enric/32/624049_2.png) [@enric](https://discourse.mcneel.com/u/enric)\
**Post date:** [July 22, 2026, 10:11am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/1 "2026-07-22T10:11:04Z")

</div>

Hi,

**VisualARQ 3.11 - Release Candidate 2** is now available for download.

> ℹ &nbsp; **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&nbsp;3.11 is scheduled for official release on 🗓 **Wednesday, August 5th, 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](mailto:visualarq@asuni.com).

**List of changes since 3.11 RC1:**

> **New Features (3)**
>
> - **Object: Beam:**
> - `7615`: Custom plane for beam end cuts
> 
> - **Panel: Tables:**
> - `14941`: List objects ID in tables
> 
> - **Rhino WIP:**
> - `15795`: Compatibility with Rhino 9

> **Improvements (1)**
>
> - **Object: Guide:**
> - `15811`: When a guide is outside an active section boundary, its elevation guides should not be shown

> **Fixed Errors (21)**
>
> - **Crash:**
> - `15815`: Crash after copying a curtain wall
> 
> - **Grasshopper: Components:**
> - `15821`: Wall main Level should be where the wall path is located
> - `14741`: Wall is detected in two levels incorrectly
> 
> - **Grasshopper: Style:**
> - `15510`: Gumball at origin in a Grasshopper Style based beam
> 
> - **IFC:**
> - `10087`: It takes 30 minutes to open an IFC file
> 
> - **Interferences:**
> - `15102`: Door generates a wrong gap in a slab after adding it as interference
> - `14842`: The subtraction of an object added as interference doesn’t update
> 
> - **Level:**
> - `15858`: Show Plan View reference on top of other objects
> 
> - **Object:**
> - `15850`: Hide UUID parameter from the Properties panel
> 
> - **Object: Beam:**
> - `15826`: I cannot set a custom Beam cut plane until I reload the Properties panel
> 
> - **Object: Curtain Wall:**
> - `15359`: Curtain wall extension error when curtain wall and surface borders are coincident
> - `14589`: Curtain wall wrong result when moving it
> 
> - **Object: Openings:**
> - `15844`: It is not possible to change the opening dimensions when it is set to Other
> - `15834`: Door opening doesn’t follow the grip point position
> 
> - **Object: Plan View:**
> - `15853`: Cut Plane Elevation property in Plan views doesn’t work
> 
> - **Object: Roof:**
> - `15752`: Roof gets flat after subtracting an inner boundary
> - `15029`: Roof flips the alignment when it is moved next to another
> - `14527`: Wrong gable roof intersections
> 
> - **Object: Window:**
> - `15421`: Leaf grip point doesn’t work for changing opening side of a window in a slab
> - `14567`: Window can’t be placed in the extended part of a wall
> 
> - **Print: Hidden Vector:**
> - `13836`: Text in leader is not correctly aligned when printing it to PDF

**Download links:**

- ⬇ [VisualARQ 3.11 RC2 for Rhino 7](https://visualarq.s3.amazonaws.com/download/VisualARQ3.11-RC2-Rhino7.msi)
- ⬇ [VisualARQ 3.11 RC2 for Rhino 8](https://visualarq.s3.amazonaws.com/download/VisualARQ3.11-RC2-Rhino8.msi)
- ⬇ [VisualARQ 3.11 RC2 for Rhino 9](https://visualarq.s3.amazonaws.com/download/VisualARQ3.11-RC2-Rhino9.msi)

**Previous version:**

- 🔗 [VisualARQ 3.10](https://discourse.mcneel.com/t/visualarq-3-version-3-10-released/219577)
- 🔗 [VisualARQ 3.11 RC1](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc1-released/219806)

Enjoy!

---

<div class="post-metadata">

**Author:** ![kristjan.tolk](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/kristjan.tolk/32/90738_2.png) [@kristjan.tolk](https://discourse.mcneel.com/u/kristjan.tolk)\
**Post date:** [July 23, 2026, 7:13pm UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/2 "2026-07-23T19:13:35Z")

</div>

After save and closing the program in rhino 9 beta, all the VA elements are blocks when I opened the file again. Levels are gone etc.

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [July 24, 2026, 7:03am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/3 "2026-07-24T07:03:36Z")

</div>

Hi @kristjan.tolk, you are right. VisualARQ data is not saved in Rhino 9 Beta. We will fix this as soon as possible.

---

<div class="post-metadata">

**Author:** ![Toni\_Osterlund](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/toni_osterlund/32/762021_2.png) [@Toni\_Osterlund](https://discourse.mcneel.com/u/Toni_Osterlund)\
**Post date:** [August 5, 2026, 9:58am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/4 "2026-08-05T09:58:44Z")

</div>

Hi,  
concerning this:

> [@VA3 Bug - Hidden view pdf printout messes up leader alignment](https://discourse.mcneel.com/t/va3-bug-hidden-view-pdf-printout-messes-up-leader-alignment/214576/6):
>
> @Toni_Osterlund Problem fixed in VisualARQ 3.11 RC1: [VisualARQ 3 - Version 3.11 RC1 released](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc1-released/219806)

There are still differences in angle text alignment, when printing with Hidden view.

 ![kuva](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/e/5/f/e5f6db7526de8c38dab0b47a211d4538ca41f759.png)  
File can be found here:

> [@Anti aliasing breaks after printing](https://discourse.mcneel.com/t/anti-aliasing-breaks-after-printing/216669/15):
>
> @fsalla I managed to find a file and a procedure to repeat the moment that antialiasing stops. Open file Set “Print” from Layouts panel, while seeing the Model view Toggle “Use Layour Page Size” → antialiasing breaks File: [Glulam\_fillers.3dm](https://discourse.mcneel.com/uploads/short-url/s0db9Vu4uAfoVq2lCOoZMSNLzuv.3dm) (6.7 MB) Rhino 8 SR32 VA 3.11 RC2 I have VA loaded, I did not test this without VA. This might be a Rhino bug as well.

Also, some obvious line breaks in the PDF printout.

 ![kuva](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/4/1/2/412269ccd1330976faf99a29292c4877956dc9ac.png)

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [August 18, 2026, 8:51am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/5 "2026-08-18T08:51:36Z")

</div>

> [@kristjan.tolk](#):
>
> After save and closing the program in rhino 9 beta, all the VA elements are blocks when I opened the file again. Levels are gone etc.

@kristjan.tolk VisualARQ data is now saved in Rhino 9 BETA with the latest 3.11 update: [Update - VisualARQ](https://www.visualarq.com/download/update/)

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [August 18, 2026, 8:57am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/6 "2026-08-18T08:57:01Z")

</div>

> [@Toni\_Osterlund](#):
>
> There are still differences in angle text alignment, when printing with Hidden view.

Hi @Toni_Osterlund you are right. We will review this.

---

<div class="post-metadata">

**Author:** ![Rasmus\_Sainmaa](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/rasmus_sainmaa/32/760023_2.png) [@Rasmus\_Sainmaa](https://discourse.mcneel.com/u/Rasmus_Sainmaa)\
**Post date:** [August 27, 2026, 8:45am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/7 "2026-08-27T08:45:45Z")

</div>

Hey Francesc, for years I’ve moved my VARQ IFC exports to global coordinates just by changing the coordinates on IFC row #23 but now that’s broken. The same coordinate referencing IFCSITE placement is now on row #16 but if I put the coordinates on it the model comes located somewhere halfway to the moon. This happens on the V4 export engine which of course is now set as default… Please help.

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [August 28, 2026, 7:35am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/8 "2026-08-28T07:35:38Z")

</div>

Hi @Rasmus_Sainmaa Do you need to export the file to IFC 2x3 or to IFC4? If you need to export it to IFC2x3, you can still use the V3Engine.

I can see that the IFCCARTESIANPOINT((0.,0.,0.)) in the row #23 when using the V3 Engine is in the row #7 when using the V4 Engine (not in the #16). Isn’t it the same for you?

Do you have an example to test this with?

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [September 10, 2026, 8:23am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/9 "2026-09-10T08:23:34Z")

</div>

> [@fsalla](#):
>
> Hi @Toni_Osterlund you are right. We will review this.

@Toni_Osterlund this issue has been fixed in VisualARQ 3.12 RC2: [VisualARQ 3 - Version 3.12 RC2 released](https://discourse.mcneel.com/t/visualarq-3-version-3-12-rc2-released/222534)

---

<div class="post-metadata">

**Author:** ![Greg\_Bishop](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/greg_bishop/32/537310_2.png) [@Greg\_Bishop](https://discourse.mcneel.com/u/Greg_Bishop)\
**Post date:** [September 12, 2026, 2:10pm UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/10 "2026-09-12T14:10:43Z")

</div>

I am unable to load the current VisualARQ for Rhino 9. It gives me the following error:

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/b/3/4/b3432bf5bac9943b8824f73ce416d532d4e94a62.png)

---

<div class="post-metadata">

**Author:** ![Greg\_Bishop](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/greg_bishop/32/537310_2.png) [@Greg\_Bishop](https://discourse.mcneel.com/u/Greg_Bishop)\
**Post date:** [September 15, 2026, 8:03pm UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/11 "2026-09-15T20:03:47Z")

</div>

I would love a response to the above question regarding the VisualARQ plug-in failure to load. Thank-you

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [September 22, 2026, 10:43am UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/12 "2026-09-22T10:43:56Z")

</div>

Hi @Greg_Bishop just try it again with the latest update: [Update - VisualARQ](https://www.visualarq.com/download/update/)

---

<div class="post-metadata">

**Author:** ![Greg\_Bishop](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/greg_bishop/32/537310_2.png) [@Greg\_Bishop](https://discourse.mcneel.com/u/Greg_Bishop)\
**Post date:** [September 24, 2026, 12:30pm UTC](https://discourse.mcneel.com/t/visualarq-3-version-3-11-rc2-released/221079/13 "2026-09-24T12:30:28Z")

</div>

Yes thanks it works with the latest update. Thanks