AutoCAD LT 2012 - Move Command Problem

[Anonymous]

Ok, I am using AutoCAD LT 2012. So I open the move command, select my objects to move, press enter, then select my base point.  At this point everything is fine.  Then I try to select the point to move the objects to with the following - shift/right-click, select "from" in the shortcut menu, I choose a point to move my objects away from, then I type in a coordinate (@750,0) to move my objects to . . . here is where the objects should move and the command should close . . . BUT instead the command remains active and wants to move the objects from the 2nd point that I selected.  Sometimes it works it works, but most of the time it does not.  So what is wrong with my AutoCAD?

[ The subject line of this post has been edited for clarity by @handjonathan Original: Move Command Problem ]

[steven-g]

There are 80 posts in this topic, so it is very difficult for anyone to know what you have tried. Do you have the latest update to your version? 

If the problem is still there after updating then please start a new topic and give us a full description of what your particular problem is, along with a copy of the .dwg file so we can try and help.

[chris.rowcliffe]

I solved this by turning Num Lock on!

I had accidentally hit the Num Lock key which caused this problem for me.

Can't believe it was that simple......

[michaelJF592]

Ok.... so I'm here, 10 years later, because I'm having trouble simply typing in the destination coordinate (0,0) on a Move command. I upgraded from AutoCAD LT 2013  to 2022. I found your answer of "Try # instead of @" to work in moving my objects to the 0,0 location.  I have never had to type in the "@" symbol in the past... so, my question here is how do I make the move command to ALWAYS be the # instead of the @? 

[cadffm]

Hi,

>>". I upgraded from AutoCAD LT 2013 to 2022."

Nothing changed between both version (related to your problem)

>>"so, my question here is how do I make the move command to ALWAYS be the # instead of the @? "

Nothing to do with your move command, it is the fundamental coordinate-input,

so LINE or COPY or CIRCLE... all the same - a generally thing how to input coordinate points.

>>"I found your answer of "Try # instead of @" to work in moving my objects to the 0,0 location."

>>"I have never had to type in the "@" symbol in the past..."

If you are using DYNAMIC INPUT feature (Dynmode is on), type in

DYNPICOORDS<enter>[F1]

If you like to use the CLASSIC INPUT method, turn off your DYNAMIC INPUT MODE  (F12 or DYNMODE<enter>[F1])

Basics

https://help.autodesk.com/view/ACD/2023/ENU/?guid=GUID-0A0135DB-3216-482B-81DD-74E6DB8CA3E3

[pendean]

@michaelJF592 Nothing is different between the two versions: like in 2013, you need to set DYNPICOORDS (System Variable) to be what you always want if you are unable to use the core default of asking for what you want all the time with @ and # that's been part of autocad for 40-ish years now.

Here is the link from HELP to guide you.https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2020/ENU/AutoC...

Post back if you get stuck somewhere with it all.

[michaelJF592]

Well... I haven't been using A-CAD that long, but pretty darn close and I've NEVER had to type in an "@" OR a "#" when I want to specify a "move to" coordinate... nor have I ever HAD to set any DNYPICOORDS to make it work the way I want it to.  I have always just typed in the coords as "x,y" and it simply moves to that location.  I can also change the DNYPICOORDS, in 2013, to "0" or "1" and it "works" the same without either of the prefixes (@/#).  So, I don't know why it would be necessary to do it in 2022 version... I guess some geek somewhere wanted to make an impact... or piss off some old guy. ¯\_(ツ)_/¯ 

Anyway... Thanks for the fix!

[pendean]

---

@michaelJF592 wrote:

Anyway... Thanks for the fix!

---

Glad it worked.

Here is an interesting observation, in both programs the default setting for the variable is the same, so if that was indeed the fix then you must have had a local event that triggered the change as it is not OOTB

[michaelJF592]

Believe what you will and post as many screenshots as you like, but like I said... I have NEVER EVER... and I mean NEVER EVER in 30+ years had to "set" or "change" any default or OOTB setting for ANY version of AutoCAD to accept only "0,0, -> Enter" to Move an object/selection to 0,0 except 2022.

Again, thanks for the fix.

[pendean]

@michaelJF592 You personally do not have to change anything: it was changed. A reality you agreed took place. it's that simple. It's not rocket science, no reason to get overly excited. It was changed, who did it no one will ever know (or much care if it never happens again).

And you're welcome.

[cadffm]

>>"to accept only "0,0, -> Enter" to Move an object/selection to 0,0 except 2022."

This setting is default since the dynamic feature was born, since Version2006

In your case, however or whoever changed that for each install since Version 2006 "for you"

The plain fresh programcode is the same for everyone and every install.

DynamicInput is ON and coordinate input format is set to relative (0,0,0 means - Don't move to X, don't move to Y, don't move to Z)

Perhaps you changed it in 2006 and in every later install you migrated the setting from the older version

or similar.

As Pendean wrote: It was changed, who did it no one will ever know.

[marie.barnsleyZ47C4]

I've had the same problem with the move command when the grid snap was on, pressed F9 to turn off and move command went back to normal.

[michaelJF592]

Riddle me this... If in DYNPICOORDS 0 = Relative and 1= Absolute (you know, those things "that someone changed" for me), then why, in AutoCAD 2013, does both the 0 and 1 value move the selected objects to 0,0 when I enter it as the destination coordinate... and Version 2022 doesn't?  You guys and your manuals... 😆

[cadffm]

Because your dynmode is another?

Turned OFF (<1) ? or is set to dynmode=2

edit:

The default setting was the same as in newer version:

dynmode=3 and dynpicoords=10(relative) - what causes that move to 0,0 will change the position.

If you used another setting than dynmode=3 and dynpicoords=1, you changed it in 2013

and you need to do the same in other versions.

[michaelJF592]

I installed 2013 myself and I can say that I did not change or set anything from the out-of-the-box settings.  I did, however just now, check the DYNMODE value that you suggested and it is set to (-3).  I also did some changing to that value as well (to 1 and then 2 separately) and made some moves to 0,0... not once did I need to use a "@" or a "#" for the object to move to the 0,0 coords.  I'm sorry, but you just cannot convince me that it has been that way since 2006... because v2022 is the only one that I've had to do anything other than "0,0 -> enter" to move an object to those coords.

Enjoyed the convo and glad I was able to get an answer to my issue. Later Taters!

[cadffm]

"check the DYNMODE value that you suggested and it is set to (-3)"

Because you changed it.

For example:

You imported/migraded settings from another install or you pressed [F12] to disable dynamic input.

In 2013 and all other Versions  default is 3 (dynamic input is on)

"I also did some changing to that value as well (to 1 and then 2 separately) and made some moves "

Why? Dynpicoord is for DynamicInput method, your dynmode is off (-3),

dynpicoords is used while dynmode is 1 or 3

Hey, software is the same for all of us and for each install.

You don't missed the dynamic feature, you forgot it after you found how to disable it.

Rock on 

[michaelJF592]

"you forgot it after you found how to disable it." ---> Negative, Ghost Rider. I don't forget...

[pendean]

@michaelJF592 Almost all of us find settings changes to be confusing. Regardless of whether you or someone/something else did it, the default setting for each variable in AutoCAD/LT straight-out-of-the-box is what is listed in HELP in the program.

It's best to know that, and take control yourself by changing any of them you need back: you can also help yourself catch any changes you yourself are not aware changed by setting up as many of them in SYSVARMONITOR command (if your versions have it) or as a script file like we in our office have done since LTv1.0 30-ish years ago.

Own it. Be a boss. AutoCAD let's you do just that all the time.

HTH