AutoCAD LT 2012 - Move Command Problem

AutoCAD LT 2012 - Move Command Problem

Anonymous
Not applicable
40,427 Views
96 Replies
Message 1 of 97

AutoCAD LT 2012 - Move Command Problem

Anonymous
Not applicable

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 ]

0 Likes
Accepted solutions (2)
40,428 Views
96 Replies
Replies (96)
Message 61 of 97

Anonymous
Not applicable

I was having the same issue with 2014 trying to move objects to my orgin point of (0,0,0) using a keyboard entry or any point trying to use the three coordinates (X,Y,Z)

 

type in command: dynpicoords enter (1) if it is set to (0).

 

This fixed the problem for me instantly.

 

Hope this helps.

 

Keith

Message 62 of 97

Anonymous
Not applicable
set dynpicoords value to (1)
Message 63 of 97

Anonymous
Not applicable

Hi Dean,

 

What you don't fully understand is this:

The user selects objects, initiates the move command, clicks on the base point, then clicks on the "destination point".  But what Cad then does by itself is it changes the destination point into the base point and when you click on a new destination point it changes it into the base point again, and this goes on for a random amount on repetitions.

 

I have the same problem with 2016 and 2017.  It is totally random and cannot be controlled.  I don't have any floating toolbars or command lines, I use Cad as is with no modifications or anything funny.  This is how it was when I installed it.  The computer I am working on did not have Cad on previously.  I installed 2016 in April, then uninstalled in full and installed 2017 recently.

0 Likes
Message 64 of 97

Anonymous
Not applicable
Corli, try setting DRAGMODE variable to off/0.

*Delchi Fafach, PE*
720-785-4623 (cell)
Delchi@dlkeng.com

DLK ENGINEERING, LLC
1300 Plaza CT North
Lafayette, CO 80026
0 Likes
Message 65 of 97

Anonymous
Not applicable
OK, here's a problem that I just had on ACAD 2012 (yes, it's an old AutoCAD. The company I've worked for since 2013 botched the installation of ACAD 2013 to where it doesn't work very well AT ALL, and they're looking at purchasing ACAD 2016 if they can scrape the money together...we seem to be in a 'down year' right now) I did a Move command in a drawing of several lines and circles. I wanted to move EVERYTHING inside the box I created (opposite corners). I typed in the distance I wanted the "contents" to move, after using the cursor to indicate which direction I wanted to move. I then select 'Enter'. MOST of the items inside the box moved perfectly...but many of them stayed in their original location! For example, I was moving the "contents" UP .oo2 inches, The SIDES and TOP of one polygon moved properly, but the BOTTOM LINE of the polygon stayed in its original place...how does something like this occur with a window Move operation if ALL of the polygon is inside the selection box? (the polygon sides were not permanently joined, by the way)
0 Likes
Message 66 of 97

pendean
Community Legend
Community Legend
Did you use a CROSSING WINDOW to select everything in the "box"? There are two "window" selections.
If the remaining objects are not on locked layers (or you have layer 0 frozen) then they are part of a bigger object you did not select.
0 Likes
Message 67 of 97

Anonymous
Not applicable

It's happening also in 2018, I changed keyboard and mouse from wireless.

 

Attached is my file.

0 Likes
Message 68 of 97

delchi
Observer
Observer
I think I solved it by setting the DRAGMODE variable to off/0. Sounds like a bug.
Message 69 of 97

Anonymous
Not applicable

That seems to fix it.  Thank you

Message 70 of 97

pendean
Community Legend
Community Legend

What exactly is "happening also in 2018"? walk me through what you are trying to do in this file you posted to I can try and replicate the exact issue.

 

Capture.PNG

0 Likes
Message 71 of 97

Anonymous
Not applicable

"Move"

Select items to move.

"Select Base point"

drag to new location

"Select 2nd point" and the process starts all over again...and each click changes the base point to the current point clicked.

0 Likes
Message 72 of 97

pendean
Community Legend
Community Legend

Looks like you found a workaround that works for you in LT2018: is LT2018 fully patched and updated? Unlike you two I'm not having issues with Dragmode set to auto in LT2018.1.1Capture3.PNGCapture2.PNGCapture.PNG

 

Note that RECOVER command did find problems in your file and I did turn on/thaw all layers since it appears you move content without doing that judging by the dimensions that suddenly ragged out over long distances. See attached.

0 Likes
Message 73 of 97

Anonymous
Not applicable

Thank you, I'll try doing that.

0 Likes
Message 74 of 97

The_Oak
Participant
Participant

Maybe "adding 2 and 2 and making more than 4" but I've just experienced a similar problem however, the cause of mine was obvious as it immediately followed adding elements "saved as" from a later version of AC. By exporting instead of just saving, the insertion didn't cause the move problem.

EXPORTTOAUTOCAD is my new friend.

0 Likes
Message 75 of 97

matt
Enthusiast
Enthusiast

Hi.  The year is 2020 and i have a G700 and on one of my computers with the same issues you described back in 2012.  Do you remember?  How did you fix it?  I think my mouse is bad.

 

Also, sorry to see you were communicating w/ Pandean.  He's one of those types that doesn't know anything but replies to everything.  I am supersized he didn't ask you to change the color of the car you were driving to see if that helped.  hahahahaha.

Message 76 of 97

tiger4956
Advocate
Advocate

Your's is the first post I've answered in many years, and I've basically given up. The problem still persists, even in Autocad 2017 on a different computer & newer operating system.  By the way, I'm running Autocad MEP, but I see my question is in the LT forum. 

 

The problem still occurs when I select a random point as the base point and a random point as the finish point.  In other words, if I select the endpoint, midpoint, center, etc. as a base point, I can usually get away with selecting a random landing point.  Another workaround is to rapidly double-click at the landing point until Autocad accepts it.  Dragmode OFF may help, but that makes it rather difficult to see where you want to move things to.

 

It almost seems as though Autocad is "lost" when you pick a random point.  It may be related to the current zoom factor, I will try to pay attention as to whether or not it occurs after a regen.

 

In summary, I don't recall ever having the problem if you pick "snap points" as your start and end locations.  Note that "snap points" exist in the drawing database as points with specific numeric values, whereas random points are generated from your  current mouse location and may have a huge number of decimal places.  The whole problem may be due to some system rounding error in the last decimal place of the random pick points.

 

Hmmm...  that leads to another thought.  I'll have to see if the problem can be duplicated with "SNAP" turned on - i always work with SNAP off.

 

Good Luck!

 

Rob

0 Likes
Message 77 of 97

Anonymous
Not applicable
Hi, I solved it by setting the DRAGMODE variable to off/0. Hope that helps!
0 Likes
Message 78 of 97

tiger4956
Advocate
Advocate
Yes, I believe I mentioned that as a possible solution, except that with
dragmode set to zero you can’t see where you’re dropping the objects.
0 Likes
Message 79 of 97

Anonymous
Not applicable

I've had this problem for months and setting dynpicoord to 1, instead of 0, finally fixed it. Thank you so much.  

0 Likes
Message 80 of 97

Anonymous
Not applicable

I tried this, but the object won't get selected

0 Likes