AutoCAD LT 2017 Object Snap Tracking issues- help?

[Anonymous]

I just upgraded to AutoCAD LT 2017 and am having issues with object snap tracking. I've included a screencast showing my problem.

The problem occurs when I try to create a new polyline referenced from a point over an existing polyline. In my screencast I drew a 12" line and had no issues when trying to draw a new polyline 4" or more from the left endpoint. When I try to draw a new polyline 1", 2", and 3" from the left endpoint the command doesn't work.

Any ideas why this is happening and how to fix this issue?

EDIT: When reviewing the video, I see typing in 4" didn't work either, as the new PL snapped to the midpoint of my first PL. So that's an issue, too.

[Imui]

snap to nearest

[Anonymous]

I don't understand what you want me to do with that...

[john.vellek]

Hi kw-arch,

I tried to duplicate this exercise in AutoCAD LT 2017 on my computer.

I think the problem you are having lies in the fact that you do not pause long enough over the startpoint.

I have attached a screencast and you will see that as I hover, the dynamic text actually changes before I enter the value for the new length.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[Anonymous]

Thanks for the response, but unfortunately that's not solving it for me, whether I have dynamic input on or off (I keep it off since it irritates me). My cursor still seems to be snapping to the nearest point to the length I enter.

[john.vellek]

Hi @Anonymous,

It looks like you are getting the start point for your lines. When you are selecting the direction (I assume your ortho is on), is it possible that you have other snap settings on that are getting in the way since your cursor is so close to the existing line?

Perhaps try toggling some of the OSNAPS off to see if it impacts the performance as well as moving your cursor a bit further away from the exisitng line.

Let me know the results please.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[pendean]

What is OSMODE variable set to in your screencast?

[Anonymous]

Thanks again for the response. Yes, it works if I turn off Osnap. This isn't very useful, however, because I need Osnap to indicate the initial reference point. I draw like this all the time and have never had an issue in previous versions of AutoCAD- the distance I entered manually always overrode the Osnap. Moving my cursor well beyond the end of the initial line also isn't providing the desired results.

[Anonymous]

OSMODE is 47.

[pendean]

So basically what we are saying is this: one of your running Osnaps is the culprit in why you cannot complete the task you show.

Any reason you cannot simply tap F3 to flick off the running osnaps, do what you need to do, then tap F3 to flick it back on? It's worth testing to confirm our guesses are accurate.

I tried to repeat your video actions here in LT2017 and I must be missing something that it is not failing the same way. Only thing I'm not doing is hovering too close to the ENDPOINT/MIDPOINT as you do.

[john.vellek]

Hi @Anonymous,

I am still unable to duplicate the problem. I will do some more research but it is unlikely that I will find anything definitive. I suggest as a workaround that toggling your snaps on and off using the F3 key can work for you.

Perhaps this is a mouse precision issue. Can you try another mouse to see if that changes the results?

You could also do a Reset Settings to Default but I am not positive it will have any impact other than to make you go through the exercise.

[Anonymous]

I've tried each Osnap setting individually, but the dimension only enters correctly if all are off. The reason I don't want to turn F3 on and off mid-command is because it's awkward and hampering productivity. I haven't had any issues with this on previous versions of AutoCAD. I was hoping there might just be a new system variable in 2017 that was causing this, but at this point I just want to go back to 2016.

[Anonymous]

That's disappointing to hear. No, it's not a mouse issue. I was hoping there might just be a new system variable in 2017 that was causing this, but it seems like more of a bug on my end. I might try restoring to default anyway, because working around this is driving me crazy.

[john.vellek · Accepted solution]

Hi @Anonymous

Did you try any of the other options such as a different mouse or a Reset? Since none of us can get this to happen and duplicate your results, perhaps there is something else going on.

[Anonymous]

Hi- It wasn't the mouse, but it works fine after resetting to default. Apparently it's an issue with importing custom settings. Not the results I was hoping for, tbh, since now I have to start from scratch with the customization.

This issue happened with the other computers in our office, too. All new machines and clean installs of 2017 with imported custom settings from the old computers.

[john.vellek]

HI @Anonymous,

At least we know where the problem lies. I suggest that you try importing customization again but one category at a time. Test between each step to determine at what point it fails. I don't think the import is at fault but one of your customizations is at fault. If you can identify which one, then fixing the other workstations will go much faster for you.

[Anonymous]

Can you point me in the direction of instructions as to how to import one setting at a time? I wasn't aware that was possible (small office, no tech support- I'm trying to figure this out as I go). Thanks!

[john.vellek]

Hi @Anonymous,

I guess the real question is what kind of customizations do you have? I like to isolate all my unique company-related customizations in their own folder and simply add it to the support file path.

Can you give me an idea of what you are trying to save and then move into your new release?

If you elect to use the Autodesk provided utility (Migrate from a previous release), just check one category at a time for your import(s).

I always prefer to do all of this manually so I know exactly what is getting migrated and to where.

[Anonymous]

So, due to the fact that I was upgrading ACAD as well as switching computers, I ended up installing LT 2016 on the new computer, importing my settings from the old computer, then migrating all of the settings from 2016 to 2017. This seems to have solved the issue. Previously I installed 2017 on the old computer and then migrated and exported my settings and imported them on the new.

Thanks for all your help on this.

[john.vellek]

Hi @Anonymous

I am glad things are back to "Normal" for you and that you should be able to get back to work. Thanks for your patience.