Hi,
I think there is another issue related to Alignment Offset and intersections.
I may intentionally have two Beams sharing exactly the same path/endpoints, but use the Alignment Offset to place one above the other, so their actual resulting geometry does not overlap.
The reason for keeping the same reference position is useful: both objects can follow the same Level/reference and move together, without having to create additional Levels or Guides just to position each component.
However, VisualARQ still seems to solve an intersection between them because their underlying paths/endpoints coincide.
Shouldn’t the actual geometry after applying the Alignment Offset be what finally determines whether an intersection exists?
The reference path could still be used to find possible connections, but if the resulting solids don’t intersect, I don’t think a join should be solved.
This may be worth checking more generally for other VA objects using alignment offsets as well, not only Beams.
Otherwise the Alignment Offset cannot fully serve its purpose as a way of sharing reference geometry while producing independently positioned physical geometry.
