AutoCAD 2013/2014 DWG Format
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Using the MOVE command....
When prompted, I select the objects that I desire to move...
After the selection is finished - I press the enter key
AutoCAD ask for the base point - I select a base point (sometimes using an osnap, sometimes just a random point)
When prompted for the second point - I either use an osnap (It happens with them all but I most frequently use - Endp, Midp, Perp, Int) or use ortho drag and enter a distance manually - to select the "move to point". Instead of the command using the second point that I've selected as the final move point - it relocates the first "base point" to the location of my "move to" point.
To finally get the command to move to the right location, I can then type "@0,0" and it will snap to the new "second base point" and finish the command. However, sometimes I even have to enter this 2-3 times before it works.
This is REALLY frustrating and all of the designers in my fortune 500 company are experiencing this same glitch. I've been tasked with finding the solution. Typing @0,0 is a simple work around but not a solution.
Sometimes I've picked the same location over and over again and after 5-10 attempts - it will finally accept the second move point and finish the command.
Can't attach a dwg as it is confidential information but I can tell you it happens in small drawings and large drawings - but not all the time. Everything we draw is with dynamic blocks (except the simple line work) and don't know if that might be the issue???
We do NOT have the problem if we use dynamic move grips - just the move command.
EVERY designer is having this issue - regarless if they are using a standard wheel mouse or a Logitech G700.
We've expereinced this issue with 2012 and now with 2013 - both full versions and LT seats.
Thanks for your help!
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Just happened again...
Copy and Paste of Command Line:
Command: M MOVE Select objects: 1 found
Select objects: 1 found, 2 total
Select objects: 1 found, 3 total
Select objects: 1 found, 4 total
Select objects: Specify opposite corner: 6 found, 10 total
Select objects: Specify base point or [Displacement] <Displacement>:
Specify second point or <use first point as displacement>: 48
@0,0
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Are you starting the move command from a ribbon or toolbar or from the command line? I am wondering if the move command has been modified on the ribbon. Try useing .move command from the command line instead. Also turn DYN off to eliminate any problems with dynamic input.
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Move from the command line (I'm old school R10 forward guy - so no ribbon for me)... Dynamic Input off as well...
When I drag the objects using Ortho mode - I just enter the distance at the command line as I have for years.
Thanks for your interest in my issue
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Thank for the temporary solution Kevin.
This bug is really getting on my nerves.
AutoCAD seems to have more and more problems with keyboard/mouse events and user interaction.
I noticed for me that this bug seems to happen more often when AutoCAD tries to regenerate the entities of the jig (preview drawing) while the cursor is moving for the second point request. As if the jig regeneration had priority over keyboard/mouse entry. If I wait for the jig to completely show the Move/Copy preview, then the bug don't show. Maybe it's my graphic card that is not powerful enought, but still, it doesn't make any sense that some keyboard or mouse entry are not processed properly.
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
The “Jig” means the drawing preview made from the entities you want to move / copy / rotate / scale / … It’s a term I saw in some AutoCAD programming threads about how to draw your own “Jig” to use in your custom AutoCAD commands programmed in .NET.
My hardware acceleration is now “ON”. So far I don’t have the bug yet…
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I'm running a new HP Z400 w/ 16 gig RAM, Xeon 6 core 3.33Ghz processor with Nvidia Quadro2000 Video card - and only work in 3D.... Shouldn't have a processing issue but something is up.
I've adjusted some snap settings and I'll see if that helps.
I'll report back through the day as it happens...
I'll also try to let it regen the preview if it happens again.
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Still doing it... Trying to create a drawing with our dynamic blocks but not the confidential side of stuff so others can test it out... No luck on getting it to work.
There's another thread in LT were someone was having the same issues - This has to be an AutoCAD glitch and not just a random isolated issue.
Thanks again for everyone's help.
Re: MOVE Command issues - 2013 and 2012 - Full version and LT
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Here's a zip file containing a MP4 of the issue....
Here's a Copy Paste of the commands during the video...
Command: m MOVE Select objects: Specify opposite corner: 5 found
Select objects: 1 found, 6 total
Select objects: Specify opposite corner: 8 found (2 duplicate), 12 total
Select objects: Specify base point or [Displacement] <Displacement>: Specify second point or <use first point as displacement>: Command: m MOVE Select objects: p 12 found
Select objects: Specify base point or [Displacement] <Displacement>: endp of Specify second point or <use first point as displacement>: perp to Command: m MOVE Select objects: p 12 found
Select objects: Specify base point or [Displacement] <Displacement>: endp of Specify second point or <use first point as displacement>: perp to
You can see - I only have 12 items selected (all dynamic blocks with attributes and Block Property Tables) - and the problem occurs using osnaps and just clicking without using osnap... It's like it's getting a "from" osnap instead of a second base point.


