topic Re: Input values not correct in AutoCAD Forum

Input values not correct

BLAKE_SUSS — Mon, 01 Aug 2022 17:21:07 GMT

New computer fresh install of Autocad 2023.

I use grips a lot to stretch many things from lines, p-lines, dynamic blocks, dims etc. for some reason when I grab a grip, drag in a direction (any direction) and type in an unit of distance and hit enter it doesn't always react the way I'm used to. Sometimes it works correctly say 12" one direction and if I try go back to exactly same spot by inputting 12" back the grip will not end up in the same spot. Also I've noticed that if I wish to draw a dim line or even a regular line for that matter and use a unit of say 5'-0" it will not always be correct. I'm very confused as to what is causing input values to not be accepted correctly. is it a dynamic input setting or something? please help its driving me crazy

thnx

Blake

Re: Input values not correct

imadHabash — Mon, 01 Aug 2022 17:55:58 GMT

Hi,

I suggest to turn OFF the OSNAP ( F3 ) and/or dynamic input ( F12 ), any changes ?

Re: Input values not correct

paullimapa — Mon, 01 Aug 2022 18:26:52 GMT

In addition to @imadHabash solutions, I would also turn off SNAP [F9]

Re: Input values not correct

BLAKE_SUSS — Mon, 01 Aug 2022 18:39:59 GMT

F12 seems to do nothing at least not that I see at the command propt, but if I go to dynamic input settings I already had everything turned off. F9 is off as well.

But interestingly F3 did cause my problem to go away. That's a real bummer tho cause I use many osnaps as well as grips.

Is there a reason why osnaps would interfere with input values? and is there maybe a work around for this so that osnaps can still be used in conjunction with direct input?

Re: Input values not correct

user181 — Mon, 01 Aug 2022 19:02:19 GMT

Try setting the variable OSNAPCOORD to 2 if it's not. Then try to draw the line with osnaps still on.

You can also change it in the OPTIONS on the User Preferences tab. Set priority for coordinate data entry to Keyboard entry except scripts.

Re: Input values not correct

paullimapa — Mon, 01 Aug 2022 18:54:42 GMT

Did you try just turning off SNAP [F9]?

Re: Input values not correct

Kent1Cooper — Mon, 01 Aug 2022 20:23:52 GMT

@BLAKE_SUSS wrote:

.... I use many osnaps ....

Do you perhaps use too many? Sometimes people just turn on all of the Osnap modes, which is an invitation to trouble or confusion, especially if NEArest is included, which will almost always "win" over others, and prevent you from getting one that you really want. Does it make any difference if you limit the modes to just a few that you need most often [I like the END/MID/INT/PER combination], and when you need some other one, call for it at the time?

Re: Input values not correct

BLAKE_SUSS — Tue, 02 Aug 2022 10:47:54 GMT

F9 was turned off

thnx

Re: Input values not correct

BLAKE_SUSS — Tue, 02 Aug 2022 10:58:50 GMT

I have end/mid/cntr/intr/and insrt turned on.

these are the same snap choices I've been using for years? difficult to see how this wld cause issues now?

I will say that it is definitely a problem with the osanps tho, cause my stretch problems go away when it's turned off completely.

This is very frustrating, never had this problem before.....

thnx

Re: Input values not correct

user181 — Tue, 02 Aug 2022 13:17:18 GMT

You didn't mention if you've tried my suggestion in message 5 to set OSNAPCOORD to 2

Re: Input values not correct

BLAKE_SUSS — Tue, 02 Aug 2022 14:36:40 GMT

DING DING DING!!

OSNAPCOORD set to "2" fixed my problem.

What a strange user preference to set but that was the issue.

Thank you (user181)!! I can now keep my sanity.

Re: Input values not correct

cadffm — Tue, 02 Aug 2022 15:04:02 GMT

>>"What a strange user setting, but that was the problem"

What's strange about a setting that allows AutoCAD to apply the object snaps you set to the coordinates you specified?

Osnapcoord=1 is the perfect choice in 99.99% cases, value=2 is default and you had changed it to 0 - we don't know why.
Perhaps you played with some unknown scripts, lisps or played in OPTIONS, USER PREFERENCES, Priority for Coordinate Data Entry

Actually, the current setting (value 1 or 2) is strange, the behavior with value 0 is formally correct / but in practice it is almost never desired.