I'm finding that when I try to drag a closed polyline to be perpendicular to a line, it wants to snap to the next vertex instead (see attached jpg which explains it better than I can!). It tends to only happen if the line I want to be perpendicular to doesn't extend to the perpendicular of the vertex I want to move.
I've only had this issue with AutoCAD 2012 and not with any previous issue. Anyone else had this issue?
Does that line you're attempting to snap to happen to have a z-value to it as well? It may be attempting to shoot it perpendicular to the elevation. Are you using running OSNAPS or an OSNAP override? Not sure what could be causing this, but I'd start there.
Thanks but unfortunately that's not the answer. All the lines have a zero z-value/elevation and I'm still having the same issues with OSNAP off and just typing per.
I've attached a drawing to see if anyone else is having the same issues (though I suspect it's some system variable that needs to be adjusted on my machine!). Dragging the grip to be perpendicular to the red line fails, yet it succeeds if dragged perpendicular to the grey dashed line.
Any other thoughts people?
I've looked at your drawing and I'm getting the same issue you are. It only appears to work correctly if I use my OSNAP extension along with perpendicular turned on, or if I explode the rectangle and then grip edit the two common endpoints of the bottm right lines. I think this may be a bug in the software. If Autodesk doesn't step in and address this I might submit it via subsription center.
Thanks guys. I personally can't get it to work with any method other than extending the red line down to where the perpendicular is but glad you're having fractionally more success! I agree that it's probably a bug...
More than nine months later and new revision (ACAD13) and it is still not fixed.
Just found the same issue with mine rev. 2013.
A bit of difference is that the polylines do not have to be even closed. Any polyline gives me exactly the described behaviour, which is definitely not intended.
Does anyone know if there is any fix to this issue available by now?
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register