AutoCAD Land Desktop

[#1]

I'm running LDC 2009, without service pack 1 installed.

Up until this morning this has not been an issue.

When working in paper space and switch back and fourth between ms and ps, there is a 4 to 5 sec lag time before I can do anything else. as you might imagine this cause a great loss of time when paning and zooming through a locked viewport. last week I installed Civil3d 2009 and uninstalled LDT 2007, I ran a repair this morning figuring that the uninstall is what was causing the issue. but the repair didn't do a thing for me. Any ideas?

Thanks,

[#2]

This is caused by Microshaft .NET framework installs, if you install ANYTHING other then the required .net install for '09 (.net framework 3.0) you will get the regen problems/broken stuff.

Multiple fixes to try here

if none of that works, remove ALL instances of .net framework and re-install '09

[#3]

---

lhampton wrote:

This is caused by Microshaft .NET framework installs, if you install ANYTHING other then the required .net install for '09 (.net framework 3.0) you will get the regen problems/broken stuff.

if none of that works, remove ALL instances of .net framework and re-install '09

---

Sorry, but this is incorrect. I have near-instant regens and layout switches in LDT2009, and I have C3D2009 through 2013 installed on the same Win7, x64, machine. 2012 and 2013 both use .NET4.0. I also do custom programming using .NET4.0, so there would be no way for me to be able to uninstall it.

The more likely culprit is layouts set to plot to a network printer which cannot be found. Autocad has a hard time working with network printers which do not exist.

[#4]

Weird, in the 25+ acad LDT/c3d installs ive done 80% of the LDT 2009 installs retracted the slow regen problem once .NET 4.0 is installed. All network printers are named correctly & present (all .ctb/.pc3 shortcutted printers are present, and named correctly), all drivers up to date, using "Autodesk Certified" hardware. Viewres, Layoutregenctl, indexctl, xloadctl all tweaked, does not fix the problem.

Suggestions?

[#5]

---

lhampton wrote:

Suggestions?

---

I can't think of anything right now. I've seen others mention the same slowdowns you see, but have yet to find a common denominator for all cases. As I mentioned, the missing printer issue seems to be the most common, but it is not the cause in some cases such as yours.

Perhaps if you could post, or send via email, a drawing which exhibits this issue I, or someone, may be able to track it down.

miff AT sonic DOT net