Community
I've got used to the frustrating practice of 2011 turning off my OSNAPs when I am inserting an elevation point on a feature line. 
I've learned to work around it. I haven't tried that in 2013 yet. But I just edited an alignment and got the same behaviour. Trying to snap the PIs of my alignment onto existing geometry, I have to turn my osnaps back on before each click! 
It's actually faster to just click in random places, then go back and snap the PIs to where they need to be. AAAAAAAAAArrrrrrrrrrrrrhhhhhhhhhhhhhhhhhhhhhgggggggggggggggg!!!!
Please, please tell me there's a sysvar that I've missed. Or is this another "that's the way it supposed to work"? Really? Becasue if I want my OSNAPs turned off for a specific task I can think of some very easy ways of doing it, and I don't want C3D stepping in and doing it for me.
Mark Green
Working on Civil 3D in Canada
2011. Make sure you have some running OSNAPs set. Go to the ribbon > Modify > Edit Elevations > Insert Elevation Point. Click on a feature line. Suddenly you realize that none of your OSNAPs are working. Hit F3 > the OSNAP settings box pops up to let you set a new running OSNAP, because they are all turned off.
2013. Make sure you have some running OSNAPs set.Click on an alignment> right-click > Edit alignment geometry > Insert PI. Suddenly you realize that none of your OSNAPs are working. Hit F3 > the OSNAP settings box pops up to let you set a new running OSNAP, because they are all turned off.
Mark Green
Working on Civil 3D in Canada
@Jeff_M wrote:2011 - I can confirm this behavior.
Do you like it, or see any good reason for it?
@Jeff_M wrote:2013 - I cannot confirm, the OSNAPS remain on and working for me. You didn't mention whether SP1 has been installed. I do have it installed.
As said, I do have SP1. Couple of other points:
With the feature line, once I start the command, click on a f-line and turn on the osnaps, they stay on as long as I am editing that f-line. When I repeat the command for the next f-line, I have to turn on the osaps again.
With the alignment (in 2013) it was different. I had to turn them back on for every | single | click |.
And I just now tested in a different drawing in 2013, and got different behaviour. Is this what you're seeing? In this second drawing, when inserting an alignment PI and then hit F3, it says <Osnap off> or <Osnap on> at the commmandline as you'd expect. All appears normal, exept the osnaps still aren't actually working. In a way this is worse, since there was no way to turn the osnaps on at all.
Mark Green
Working on Civil 3D in Canada
@troma wrote:
@Jeff_M wrote:
2011 - I can confirm this behavior.
Do you like it, or see any good reason for it?
I rarely use running osnaps, so I've never noticed it. No, I'm not sure why they chose to turn them off for this command.
@troma wrote:
And I just now tested in a different drawing in 2013, and got different behaviour. Is this what you're seeing? In this second drawing, when inserting an alignment PI and then hit F3, it says <Osnap off> or <Osnap on> at the commmandline as you'd expect. All appears normal, exept the osnaps still aren't actually working. In a way this is worse, since there was no way to turn the osnaps on at all.
No, I see nothing like this. If they are on before starting the Insert PI command, they work fine. If off when starting the command, I do have to turn them on for each PI inserted but they do work correctly.
I just realised that it is only the endpoint osnap that is deactivated by this command. Of course, it's the only one I want to use. Possibly previously it was the only running osnap that I had active, so I thought that they had all been turned off.
Mark Green
Working on Civil 3D in Canada
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")