AutoCAD 2010/2011/2012 DWG Format

[#1]

Ever since switching to 2012 (and upgrading to a new HP computer) I have noticed that when I am in a medium to large file, autoCad will hang up and freeze for a couple of seconds up to almost a full minute when I start a command like "line" or "rotate" and zoom in to pick the first point. It usually happens when the curser begins to highlight one of the osnap options and I continue to use the mouse zoom wheel to get in closer in order to pick exactly which end point, mid point, or center point that I want to snap the first point to. While AutoCad is temporarly frozen, I can go to another apprlication that is running (such as Word or Outook) and work there until AutoCAD unfreezes. Does anyone else have this problem or know what a solution might be.  I am on a WIndows 7 64-bit machine with 8GB ram, i7-2600 CPU @ 3.4Ghz dual Core, with ATI FirePro V4800 and have SP1 for AutoCAD 2012.

[#2]

Turn off WIndows Aero Theme, go with Windows Basic Theme, and see if that helps.

Also, what is hardware acceleration set to in AutoCAD, on or off?

[#3]

Unfortunately turning Aero off and using a Basic, non-aero, theme did not eliminate the freezes. Hardware configuration is currently set to be managed by the Performance Tuner. Under Manual Tune the enable hardware acceleration is checked on.

[#4]

Turn off hardare acceleration in AutoCAD, see if that helps.

If you can, define what size DWG files this starts occuring, we seem to have identical PCs and I don't see it so far.

[#5 · Accepted solution]

After contacting the technical support team at Autodesk, I received a reply that same day! (Did not expect that; way to go Autodesk) Using video screen capture technology, the support tech showed me exactly what he was doing as he played around on the file I sent trying to replicate my problem. After a few back and forth e-mails it was determined that the hang-up only happens with complex shapes defined as a region while trying to zoom in the middle of a command once the osnaps are trying to find possible snap points. We discovered that simple regions are not a problem and the development team will be notified for a future fix.  Until then work arounds include turning Osnap off when zooming around complex regions, being careful not to zoom or scroll when in the middle of command after osnaps have begun to find points on the complex region, or by exploding the region and making it a block instead.

[#6]

Thanks Pendean for your help in identifying (or at least determining what was not) the problem.