Opening area calculation error

unhandled

#1

Hello VisualArq community.

I am experiencing a very frustrating situation with the area output of visualarq whenever I have a wall which contains openings. The area is always off by a large amount. The area given from visualarq when selecting the individual elements is accurate, but when intersecting both, the resulting wall area is not the difference of both initial objects
(See example; 13.15 - 7.53 does not equal 8.88)

I cannot find the logic behind the areas calculation visualarq is doing. I have tried replacing the windows for openings and doors. I have tried with a straight wall. I have tried with a single opening at a time. I have tried changing options such as cut depth, opening side, alignment etc… and the mistake is always there.

Please help!
Thanks!


#2

Hi @Sadi It seems there is a bug in the calculation of the wall area. We will fix this in the next VisualARQ version. Thanks to report it!


#3

Ok I have been playing around with openings and walls, I think it has to do with the automatic extension of walls. For example the length value of a wall does not update when a wall extends to join another wall. In this case the length value is the length of the wall that was drawn.


(Tim) #4

Speaking about the area (a bit off topic though), I would like to add something I’ve noticed, a minor problem, not sure if it is a bug, but spaces don’t show the area in some situations where zones are enclosed with walls containing structural elements (in my case) like columns or curtain walls, are they not included in calculations of a closed space?
###On this image you can see bedroom’s area can not be calculated as well as WC’s


###If I hide the columns you can notice the openings, is that the case? Should one instead let the wall go through the columns?

###Same story for the Curtain walls.


#5

In this case this is done on purpose. I mean, the area of the wall is calculated according to how it is extended to another wall. If you want to control this extension you can edit the “Maximum Extension” parameter at the Wall Properties panel.


The bug is caused by another reason we need to figure out.


#6

@timglobal, The Space object, up to the 1.9 version, detects walls and columns for the area calculation. If you hide a column the Space area shouldn’t change, because the column is still there although you don’t see it. If you don’t want to take the column into account for the area calculation, you need to delete it or create the Space from a Curve that you need to draw manually with the desired contour.

The curtain walls are not still detected for the Space object, but they will be in the VisualARQ 2.0 version. So in that case you need to create the Space from a Curve as well.

In your screenshots you show some spaces with area 0.00. There must be some gap among the wall intersections, because it should work. If there is a gap the space won’t able to detect a closed boundary. Play with the wall ·maximum extension" value or the Wall end points so you make sure they are all connected to each other. Otherwise send me that model to visualarq@asuni.com and we will check it out.
Thanks!


(Tim) #7

@fsalla Thank you for reply, you were right about the gap, I “resnapped” everything back to the right places and space detected it’s area.


#8

@sadi, this error is already fixed in VisualARQ 2