Prevent door/window to snap to nearby wall?

VisualARQ
1

Hello!
Got the case here where I want to place a door across a corridor (90° to the corridor walls). However, the door always ‘snaps’ to the left or right wall. Is there a way to prevent this? The wall should have the exact width of the corridor.
Thanks!
Best regards
Eugen

2

My colleague found a workaround: put the door inside a block.
Edit: But then the 2D display (opening side) of the door won’t work anymore. Also, when editing the block, the doors do snap to the nearby walls again.

3

@Eugen does it work for you if you place a wall across the corridor, and then you insert a door in that wall? that way the door will detect the crossed wall and not those of the corridor.

4

Hello Francesc!
Yes, that worked. My initial mistake was trying to put 2 doors side by side into that crossing wall, because I forgot that doors can have multiple leaves. A single door snaps correctly to that wall.

Regardless, I’d strongly suggest implementing a mechanism to override/extend that auto-join feature. I had numerous situations where e.g. walls do not join the way needed, no matter what I try.
Some time ago we discussed this ArchiCAD-like feature where only objects that share a common index parameter get connected. Lately you seemed to avoid that topic, but let me assure you that this is important, and would solve many problems that arise when you try to do everything with one super smart auto-join feature. It cannot know all the time what’s needed.
Thanks for considering! Hope this will be in V3.
Best regards
Eugen

5

Hi Eugen,
Please report these situations so we can see if there is a solution.

This feature is on the table, but we need to discuss how to handle it, and it requires a major change on how VisualARQ works. So it’s a medium-long term change.

6

Hello!
Thanks for the reply! When I find the time I will send some files (time is the factor these days with the office job and a little child…)

I case you don’t have ArchiCAD at hand - they allow exactly one ‘join group index’ per layer (not even per object). Like in our brief discussion back then, I’d suggest not to allow more than one index per object, too, or things can get really complicated.

A thing to figure will be what vaSpaces will do when surrounded by walls of different join indices - but that should be solvable I’d like to think.