Text Snap in 2016

Text Snap in 2016

BMATT
Enthusiast Enthusiast
7,374 Views
8 Replies
Message 1 of 9

Text Snap in 2016

BMATT
Enthusiast
Enthusiast

So installed 2016 today and all is running well, just have 1 bug so far.  When I go to move the text a new snap appears, it is an 'X' that seems to appear at your text justification (Top Left or whatever), problem is when you are moving anything this magical new snap appears as you move over any and all text.  I can't seem to find a way to shut it off.  I use a lot of snaps, but this is not one of them and it does not seem to be grouped with his other snap buddies.

Please help,

0 Likes
Accepted solutions (1)
7,375 Views
8 Replies
Replies (8)
Message 2 of 9

nestly2
Mentor
Mentor

Cursor Badge or Node Osnap perhaps?   Can you post a screenshot with enough resolution that we can see this mystery object?

0 Likes
Message 3 of 9

GrantsPirate
Mentor
Mentor

That is Tracking showing, and in 2016 it seems to work whether you have Object Snap Tracking on or off.

 

Edit:  Set AUTOSNAP to 0.


GrantsPirate
Piping and Mech. Designer
EXPERT ELITE MEMBER
Always save a copy of the drawing before trying anything suggested here.
----------------------------------------------------------------------------
If something I wrote can be interpreted two ways, and one of the ways makes you sad or angry, I meant the other one.

Message 4 of 9

BMATT
Enthusiast
Enthusiast
But then no snap works at all. I still want my end points, mid points, etc.
0 Likes
Message 5 of 9

BMATT
Enthusiast
Enthusiast

Sure thing Nestly, here you go.

Its that little annoying "X" to the lower right of my cross hairs...

0 Likes
Message 6 of 9

darawork
Advisor
Advisor

AUTOSNAP has a range of values: http://help.autodesk.com/view/ACDLT/2016/ENU/?guid=GUID-BE7947EB-2A08-4406-A169-4C5E125B1F4D

Indeed, setting to 0 may be overkill. Perhaps try incrimental increases of the varible until you get to a level that is comfortable for you.

Mine is set to level 5.

 

That marker looks like an Object Snap Tracking marker (F11), you have the icon turned on.

Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760

0 Likes
Message 7 of 9

nestly2
Mentor
Mentor
Accepted solution

The green "X" at the lower right is just the Intersection OSnap marker.  (as noted by the Autosnap tooltip)  I assume that means Intersect Osnap is "running"  I don't have an explaination why there's an "intersection" being detected there, but I can find similar "intersections" on MText objects in AutoCAD2015 that seem not to be located at actual "intersections"

 

Intersect OSNAP marker.jpg

0 Likes
Message 8 of 9

BMATT
Enthusiast
Enthusiast
You are right, I swear I tried turning that "Intersection" off yesterday and it did not work...did today though.
Thanks for the help, I don't use the intersection that often, so I don't mind just typing it in.
Cheers,
0 Likes
Message 9 of 9

SSNE302
Contributor
Contributor

Found this post while fighting ACad with this exact same problem. At least from what I managed to duplicate, it had something to do with the mtext itself. I could not replicate it with single line text, and it was not happening on other files. It only happened on one file. It happened for days (turn off computer every night), so it was a recurring problem. Everything was the same between the multiple files, that I could see anyways. This morning I decided to ctrl-c, ctrl-v some text from a good file into the bad one, and low-and-behold, the problem disappeared. I un-did that paste and the problem was still gone. I didn't save the bad file, rebooted my computer to see if I could replicate it, and no, it's gone. I have zero idea what it was, but I have always had "Intersection" turned on and only one file had this problem. I checked column settings, paragraph settings, file settings, ACad settings, everything I could think of and everything was the same between the multiple different files I checked. All I can surmise is that there is either a setting that I don't know about that allows snapping to the column/row corners (the Intersection snap points changed with the text box size adjustments, but only show up when hovering over the text itself, not the box) or it was a really odd glitch. And this is NOT related to the Node snap. That was off the entire time, and when I turned it on to test, it snapped to the same place but the hover text said Node. When I turned it off, it said Intersection again. Also, this is NOT related to the text frame. I turned that on and the snaps were not anywhere near the corners of that frame box.

 

Hopefully this gives some more insight for anyone having this problem.

 

*** EDIT:  I should've known with Adsk...  Well, I did nothing different, and it's back, within an hour. I had rebooted and verified and opened/closed ACad multiple times to trial/verify that it was gone and it was.... until 2min ago. Same as before, shows "Intersection" when hovering, and only on this file. I went to create a new pline and noticed it snap funny and sure enough, the mtext column corner snap is back.... Screenshot attached. Snap locations marked with lines.

More info: I attached more images. This is getting weirder as I dig into it (it's really ****ing me off). So it seems like whatever is causing this snap thing is stemming from thinking the text is lines vs other shapes? It won't show the snap when I hover near/over any (snap aperture box on) lines (hori or vert), but will if I hover over a corner or any kind of radius. See images below. Image with green: it really seems like it has something to do with ACad looking at the text as lines, and the intersections of the lines is where it pulls the Intersection snap, but since that's not a thing, it pulls the nearest snap location, being the column nodes. I can't see why it would act like that with the dot of the "i", but that's how it's acting for me.

 

MTEXT SNAP GLITCH - 4.jpg

 

MTEXT SNAP GLITCH - 5.jpg

 

MTEXT SNAP GLITCH - 6.jpg

 

MTEXT SNAP GLITCH - 7.jpg

 

MTEXT SNAP GLITCH - 8.jpg

0 Likes