IFC4 VisualARQ

VisualARQ
, ,
1

Will IFC4 export be available in the next version of VisualARQ (Visualarq 3) ?

2 Likes
2

Yes, it will.

4 Likes
3

Thank you ! Great !

1 Like
4

Hi Guys,

is there any release date for VA 3? IFC 4 would be essential =)

cheers

1 Like
5

Hi @user28,

We don’t have a release date yet, but we will let you know once we have a WIP version.

6

Ah, c’mon… a little hint? This year? Next month?
I know, I know… I hate it too, when people ask me how long something will take. But I have to say something.
=]

3 Likes
7

Yes. It’s time to say something. Is AUSNI really working on VA 3?
ASUNI should say at least release year.

1 Like
8

We plan to release VisualARQ 3 next year. We have got some of the new features quite advanced in an internal WIP version, other features that are in progress, and another group of features that we need to determine whether they will be finally included in version 3 or will be postponed in future versions (if they may delay the release of VA 3).

3 Likes
9

Ok, thanks for being open!

I personally hope all planned features regarding better Layouting/Documentation will find their way into VA3 - DWG export from Layout space, better tables, section/plan views directly on Layouts… this kind of things.
Thanks again!

4 Likes
11

Hi,

is there the updated information when the ifc 4 will be supported?

Thank you

2 Likes
12

Hi @kristjan.tolk we are working on the IFC4 support for VisualARQ3, that will be released soon.

3 Likes
13

Great! Keep up the good work!

1 Like
14

Hi Francesc, I hope you’re doing well! Quick question, is there any progress on IFC4 support in VisualARQ 3? I’ve been digging through the forum, and it seems I’m not the only one eagerly waiting for it to land. Right now, I can only export to IFC2x3, is that still the expected behaviour, or am I missing a hidden setting somewhere?

Just trying to plan ahead a bit, and knowing when IFC4 might be ready would help a lot. Any insight would be much appreciated. We’re cheering for the VA team from the sidelines, keep up the great work, and may the bugs be few and the features plentiful!

1 Like
15

Hi @Fabsye I hope the IFC 4 export will be implemented in the VisualARQ 3.6 or the 3.7 update. I’ll keep you posted.

Is there any specific reason why you need to export to IFC 4 and not to IFC 2x3 ? (We want to ensure that in addition to export to IFC4, the model exports with the desired features or specifications).

1 Like
16

Hi Francesc, thank you for raising such an important point! The big difference between IFC 2x3 and IFC 4 is really about maturity and future-proofing. IFC 2x3 has been around forever, stable and widely supported, but it’s a bit like using a trusty old flip phone… it still works, but you can’t expect it to handle modern apps. IFC 4, on the other hand, is the official ISO standard, with richer geometry (hello NURBS!), more detailed property sets across architecture, MEP and infrastructure, and far better interoperability with tools like Revit, Archicad, or even Bonsai BIM in Blender. It’s actively evolving, so using IFC 4 means smoother exchanges and less data loss. In short, the future is definitely IFC 4!

1 Like
17

@Fabsye Thanks for your reply. I was asking this because depending on the features you are looking for, the IFC 2x3 export might work for you instead of the IFC4. I know IFC4 has more detailed property sets, but as regarding NURBS, if the software you open the IFC file with doesn’t support NURBS, exporting the model to IFC 2x3 or IFC4 might not make so much difference.

1 Like