I’m modeling a water tower with VisualARQ. It’s quite a challenging project as there literally isn’t any straight wall within the building complicating the drawing tremendously.
The real-life building can be seen in this image: SINT-PIETERS-LEEUW | Watertoren | Pascal Kestemont | Flickr
Most of the walls are constructed by using “wall from curve”. For most walls this works fine but for some, I have a strange phenomenon. It concerns the red-bricked wall on top in the photo but which I’ve remodeled at ground level to explain my problem.
As you can see in the first drawing, I construct a one-layer wall along a rounded curve. No issues there.
When I move the wall 5 m towards the Rhino origin, after moving, the wall immediately shifts off it’s original curve beginning and ending (see drawing 2).
The same thing happens when the wall is constructed on a curve 5 m closer to the origin.
Can anyone explain this phenomenon?
Using Rhino Version 7 SR5 (7.5.21100.3001, 2021-04-10)
VisualARQ: version 2.10.1.14725 (2021/03/24)
Hi @morphhorizon, is there any other invisible wall that is intersecting with that curved wall? that might explain why it changes its length, since it might be trying to intersect with the invisible wall.
If this is not your case, could you share the 3dm file (or at least a reduced version of it with the involved geometry) so we can take a closer look?
Thanks,
It seems indeed the wall seems to want to connect to 2 other walls (which were hidden in the previous images).
Yet in doing so, at one end, the brown wall goes through the vertical white wall while on the other side, there is a gap.
Is there any way to prevent walls from interacting with other walls (a setting perhaps)? I understand the utility of connecting in “normal” builds but here, because of the 360° rounded walls intersected with 8 vertical beams, I think it more useful to have each wall fit between the others but not interact in any way with them.
If you want I can provide the (slimmed-down) model file but at this point I’m not suspecting unusual behavior is happening. VisualARQ is reacting as designed. It’s related to these issues but not entirely solvable in the same way).
