Is there a way to do it? It may work if line work behind the section is orthagonal to the section to osnap to, but I have a section through mouldings wrapping around a curved wall, and need to dimension the mouldings visible in clipped section, but I can’t snap to anything but the lines through which the section does not go.
Hi David,
Snapping only works on unclipped geometry. The section lines are just a display feature (they do no really exists in the model), so snap feature cannot detect them.
We’re trying to figure a way to solve this.
Thanks,
Enric
Any news about this problem? I’m still having the same issue here.
Best Regards,
Daniel
It is a problem. The purpose of most sections is to dimension the sectioned surfaces.
But it may go beyond Va, because we can’t snap to Clipping Plane cut surfaces either. My workaround - for a non-orthagonally sectioned persepective - is to generate a 2d VaSectionView and layer a Detail with the 2D VaSectionView on top of the Detail with the 3D Hidden view. With a rendered detail also at the bottom of all that, it’s cumbersome.
Another workaround, I guess, is to intersect the geometry with a plane and create an intersection curve at that location. You should then be able to snap to that curve.
Thanks Wim. Wish I’d thought of that.
I see that Pascal offers a ClippingPLaneCurves Rhino script.
Will it work - and be stable - in a Visual Arq Section?
Hi David,
Unfortunately, this script will not work with VisualARQ sections, as this script only looks for Rhino Clipping Plane objects.
Regards,
Enric
Hello!
Snapping to sections would be much welcome! As would snapping to the level lines in an elevation.
2 options:
- It’s clear that ‘display’ lines can’t be snap targets so maybe VA object generate ‘real’ section curves instead of just a ‘display’ version?
- Or, the Rhino snapping gets extended to snap to a special type of geometry that only serves that purpose and isn’t part of the scene. That would be outside of the scope of VA devs of course.
Hi @Eugen,
I agree that the ability to snap to section curves would be awesome. Regarding your options:
- It may work with VisualARQ objects, but it won’t for Rhino geometry like poly-surfaces. So this is not a complete solution. Moreover it will make sections slower, as computing real sections curves for certain objects can take some CPU time.
- As you have pointed out, this needs some work from McNeel.
I’ll try to take a look and see if we can do something in VisualARQ for the next release.
Regards.
Enric
It works within a Va Section though, as a workaround:
Here it is providing contour lines through a Rhino Object and two VaWalls:
(The Clip Plane is precisely coplanar with the VaSection. ClipPLaneCurves created undesired points and lines as if the VaSection were an object, but it also creates desirable snappable lines at the section cut contours.)
The contour linese are coplanar with the VaSection but they show up in a Detail View with the section cut, and create snappable lines on otherwise non-snappable geometry. For now it’ll have to do.:
Hi all, the inability to snap (measure / centre orbit) to a VisualARQ object that has a VaSection applied is frustrating indeed. Not sure if there are other threads on this, but has any progress on a solution been made since previous post in Oct last yr?
I think this thread is worth resurrecting since this is pretty critical for architectural applications.
Here’s a classic example:
In this video, I’m trying to move a top plate 2x6 within a wall. Selecting it is possible, but requires two different shortcut commands that are somewhat obscure and then finding the necessary osnaps appears to be impossible. I’ll figure out some way to make it work eventually, but it’s a genuine pain.
This is a particularly good example because it shows how this is a major issue for anyone hoping to move production work like this to less experienced staff and expand the use of R8/VA from niche, single phase work to an entire project, single platform solution.
With that in mind, here’s a couple questions:
- Where is this issue on the roadmap for VA/R8? (The current roadmap link doesn’t seem to be working)
- Does anyone have a viable workaround for moving and dimensioning objects in section that is robust and accessible enough to adopt as a long term solution?
- Is this fidelity of drafting an intended use for VA/R8?
It’s a testament to how far VA has come that this is one of the last remaining significant barriers to it’s viability as a full project, single platform solution. Thanks for your help!
I’d also like to emphasize the importance of this issue…
I find it really difficult to explain to my colleagues coming from ArchiCAD/Revit why it’s not possible to snap dimensions onto a section detail view - let alone accurately select, move or measure individual objects.
Thanks,
Michal
@Clayton_Muhleman @MichalKrizo we are aware about the importance of this issue and the need to find a solution. I’ll keep you posted.
We need to redo this page.