AutoCAD 2012 to 2015 - laggy and sluggish

All generalizations about xxx version being slower than xxx version can be dismissed IMO. I regularly run both AutoCAD2011 and AutoCAD2015 on a machine that would generally be considered less than optimal according to the current AutoCAD system requirements, and neither is one bit "laggy" or slow. Having said that, AutoCAD is now, and has always been finicky, and it doesn't take much for one feature/conflict to drag even a Cad super station to it's knees. What's not always easy is figuring out what's causing the problem

It was mentioned that it got "worse" with Hardware Acceleration disabled, so the graphics system would be among the first place I'd look as simply disabling HA shouldn't necessarily cause command lag.

AutoCAD2015 is supposed to be optimized for DirectX11, your card may not be DX11 capable, and even if it is, some have reported better performance when switching to DX9 (link) What you don't want to see at the top of the GRAPHICSCONFIG dialog is a software driver listed as the Virtual Device, rather than DX9 or DX11. Also specific to AutoCAD2015, you may try turning off LINEFADING and/or LINESMOOTHING when Hardware Acceleration is enabled

Other trouble shooting suggestions:

Disable all the Input search options

Dock the Command Line (Docked, not anchored)

Disable COMMANDPREVIEW

Disable PROPERTYPREVIEW

Disable SELECTIONEFFECT

Disable PRESELECTIONEFFECT

Disable SELECTIONCYCLING

Disable ROLLOVERTOOLTIPS

Disable QSELECT

Close Properties Palette

Close Layer Manager

Purge drawings of unnecessary linetypes (DGN)

Purge drawing of unnecessary layers

Purge drawing of unnecessary Annotative scales

Purge drawing of unnecessary Regapps

Purge drawing of unnecessary Geometry/Parametric Constraints

Resize AutoCAD window if it's maximized, or maximize AutoCAD window if it's not already.

All generalisations about xxx version being slower than xxx version can be dismissed IMO.

I won't agree with that. I mentioned side by side testing of 2014 and 2015 on the same hardware, there are significant performance differences between the two. One could only dismiss such differences because they may not be noticeable after a certain period of usage time, but back to back testing I assure you, it's very obvious to me. Everything from launch time, to the time it takes to switch between model/layout to the time taken to display the filtered list of commands (when typing a command, eg: opt for options is much slower in 2015).

Maybe some of these GUI issues can be attributed to some goofball developer thinking it's a great idea to add similar visual effects such as fade-in animations to AutoCAD much like the same silly animations polluting operating systems.

AutoCAD2015 is supposed to be optimised for DirectX11

Well again, another over zealous often chanted myth, at least you said 'supposed'.

AutoDesk and AutoCAD people are apparently zombies hypnotised by the Steve Jobs "Reality Distortion Field" effect. From what I see, there are no magical DirectX "optimsations". As mentioned, AutoCAD doesn't even touch the GPU. Download "Nvidia Inspector" and observe the GPU load metering for ones self. Use an X-Ray, Realistic or similar visual style. Move the cursor in free space and the GPU will show some load, (which is useless) but it's less than 8% when actually doing anything like 3D orbit, panning, rotating or selecting or anything that it SHOULD be used for. The only thing to say on the subject of DirectX is that AutoCAD 2015 will now 'only' acknowledge the presence of DirectX11 hardware. If the hardware isn't on AutoDesks' happy list, the hardware shows as 'Not Recommended'. If the DirectX11 hardware is a Quadro, AutoCAD reports the hardware as recommended. Be aware, there isn't any performance difference. The hardware also isn't utilised-it performs no different to the 'not recommended hardware', such as Gforce. AutoCAD 2014 and below will not acknowledge DX11 hardware if it not on the happy list eg Geforce. Additionally consider, and don't take this lightly, when was the last 'specialised/optimised performance driver' issued by Nvidia for AutoCAD and what release was that designed for. I'll tell you, there isn't a current special driver and there hasn't been any such development for AutoCAD since 2010, for that and prior versions and they have no intention of creating specialised drivers for current AutoCAD.

Now if we compare AutoCAD's 'JOKE' of a 3D engine (supposedly DirectX11 optimised) to a 'real' 3D engine, such as Redway3D used in BricsCAD, we notice fluid, silky smooth 3D orbiting, rotating, zooming of the same large 3D models tested in AutoCAD (which is comparatively like running on an Atari 1040STE). Nvidia Inspector's GPU monitor verifies that the Redway3D engine is fully utilising the GPU. Adding another GPU of the same type (SLI), shows the load being evenly distributed over the two for even smoother effortless manipulation of the model. CPU usage is not fully pegged as it is for AutoCAD and this is further evidence the 3D engine is doing a proper job by using GPU hardware.

Now, for AutoCAD, before you jump on the 'you shouldn't use it like that' (Steve Jobsian iPhone 4 antenna-gate reference) irrationality, consider AutoCAD Plant 3D, (AutoCAD derivative) it too suffers from similar atrocious performance as AutoCAD, discussed here. Plant has that key phrase you hate hearing when speaking of AutoCAD, '3D' ho ho ho - no excuses ;-)

Maybe AutoCAD is in a erosion-ally slow transitional phase (5+ years and counting) and that the DirectX 3D engine code is a work in progress, as yet to literally switched on. That's the optimistic thought. I'd guess AutoCAD is on life support. AutoDesk don't give a **** any more about it and just show a few new visual things to make it look like there's activity while they continue to milk their customers with minimal effort (cynical perspective).

carry on

I'm running 2014 and 2015 side-by-side and see no performance issues in either. Your mileage may vary.

It sounds like you've got some major performance issues, willb. Your experience is not typical. An inadequate video card can and will have an effect on AC's performance. A better one will improve it. It is not an end all, be all and may not be in the case for the OP but saying it has little to no affect is not accurate.

If what you are saying is true then AutoCAD help is lying.

OP->Always be careful of the repeated claims that buying a video card for AutoCAD is going to be of any benefit. I've done much testing on this subject and I can confidently say that the video card plays an almost zero role in improving AutoCAD performance. I'm speaking specifically about AutoCAD 2015 and 2014 which uses DirectX/Direct3D video cards. AutoCAD prior to 2008 (?) supposedly had OpenGL code and at that time workstation cards such as Quadro/Firepro were used. Since i'm fresh to this game (AutoCAD) I can't confirm any performance characteristics of those systems. However, monitoring GPU usage with Nvidia Inspector clearly shows the video card isn't utilised. I use a modified X-Ray visual style with materials, textures, shadows off with a Faceted lighting quality (far too difficult to use Wireframe as there's just too many line obstructions for me-3D only). Monitoring the CPU however will show a single core fully utilised with a 100% load proving that AutoCAD is purely a single threaded CPU bound application.

 

I can also verify that AutoCAD 2015 is very slow and laggy in the many ways you've mentioned. The GUI is noticeably slower than that of 2014 as they've changed all the GUI typography and created that dark them which slows things down considerably if one was to compare both versions side by side. However, 2015 dramatically improved multiple object selection for me. In 2014 it was almost impossible to select many objects to perform routine commands, mirror, rotate, copy, move etc, AutoCAD with cough, splutter and take over 30 seconds to select then over 1 minute to begin the task and then freeze up, hang in any visual style aside from 2D Wireframe.

 

AutoDesk unfortunately appears to have a 'deny all' and 'don't give a ****' type attitude and have no aspirations of improving the performance of their product, well the only performance they seem to care about is sales performance.

What was the exact response Autodesk gave you when you contacted them?

All generalizations about xxx version being slower than xxx version can be dismissed IMO...

I do appreciate your tips and I will give them a try but do you not see the hypocrisy in that statement?

I didn't generalize, I've made it quite clear that this is my experience and what I've found to be a small sect also experiencing this. Just because it runs snappy on your system doesn't mean it will run like that on everyone else's.

I know it's likely a feature or setting that is causing this, which I also made clear, and the whole point of this thread was for help locating the issue.

I like where you went with the HA based on my comments, you're thinking logically. But I should have clarified that the command line lag stayed the same, but it was model space that turned laggy. Moving, copying objects was sluggish.

I've printed out your list for when I get back to the new machine to try it out. I'll let you know if anything made a difference.

I'm running 2014 and 2015 side-by-side and see no performance issues in either. Your mileage may vary.

This pretty much sums it up. YMMV.

Thanks again everyone for their input.

I didn't intend for this thread to become a version vs version argument.

I'm just try to solicit help from a community of experts.

I would take everything willb said with a grain of salt. I'm no expert but I see some flaws in his logic and his extreme absolutes really muddy the waters. For instance, would you really expect a newer version of any software to not run slower, noticeable or not, on the same system?

This is purely anecdotal but I was working on a 5 year old machine and I kept using 2013 because 2014 and especially 2015 were slower and just had many glitches (for lack of a technical term) while working. IT just bought me a new computer, Dell OptiPlex 7020, Win7 64, i7 4790 3.60GHz, 16 GB 1600MHz memory, SSD, and AMD Radeon 2GB GPU. Note that the GPU is a fairly pedestrian card but so far is working without any problems, and I admit this machine is new and so I haven't had time to work on a project in 3D as yet. So far 2015 is working great, although I still don't like most of the additions to it, so new hardware every 3 years for me rather than the 5 or 6 I have been doing.

@ MDrawings. The first paragraph of my reply was directed at willb, who in post #20 wrote; "I can also verify that AutoCAD 2015 is very slow and laggy.... The GUI is noticeably slower than that of 2014.... "

Those were the "generalizations" I was referring to... sorry for the confusion.

Forgot about this. The Autodesk reps are just a bunch of sales 'mooks' and are mostly clueless, they're only interested in selling more licenses. When it comes to Autodesk support, they either do not bother to respond or you'll get a scripted company line such as 'we've never heard of any problems from other people, you're the first case and as such it of little interest to use to investigate further, good bye thanks for lining our pockets'.

->RobDraw I don't know anything about MEP AutoCAD, but if they say that about AutoCAD than I can positively say it's absolutely false. Look the only time I see the GPU being hit is when Selection Preview Highlight is enabled and the cursor runs over an object, the GPU will spike a bit maybe 30%. Also a spike when those hove over tags pop up. This is useless because when performing normal use tasks such as a full orbit, rotate, pan etc the GPU is practically idle. This is still the case in 2016. Also in 2016 they have reduced the time it takes to select items, but only in 2DWireframe, none of the other visual styles have any improvement, also a little more responsive to copy the selected items, again only 2DWireframe. For 3D anything other than the most simplistic small models it's not really practical to work in 2DWireframe, there's just far to many lines and it's incredibly difficult to retain a sense of location. Ideally i'd spend 99% of the time in X-Ray, and the other in Realistic to detect any obstructions. As it is, there'd need to be a minimum of a 12GHZ CPU to adequately push the models around. Since that isn't happening anytime soon a pair of Geforce video cards could handle it right now if the 3D pipeline was coded to utilise them.

I find it more convenient to work in 2Dwireframe only switching to Conceptual when needed. The other thing I do to eliminate or cut down on visual clutter is isolate the layer I am working on.

I find it more convenient to work in 2Dwireframe only switching to Conceptual when needed. The other thing I do to eliminate or cut down on visual clutter is isolate the layer I am working on.

Sadly we loose the move, rotate, scale, Gizmo, and the UCS icon is a small single line which is harder to pick up and more around. LayerISO can be useful but it freaks me out because it doesn't actually do what it really should do, that is hide every other layer, it just locks it a makes it opaque, the freaky bit is when running a selection set, the other layers look to be selected but the operation won't be performed on them, can be spooky.

LayerISO can be useful but it freaks me out because it doesn't actually do what it really should do, that is hide every other layer, it just locks it a makes it opaque, the freaky bit is when running a selection set, the other layers look to be selected but the operation won't be performed on them, can be spooky.

Have a look at LayerISO settings. You can have layers turned off when layer isolate is applied. It's another case of AutoDesk turning on new "features" by default, often leaving people wondering about the "old" way.

I've not encountered much in the way of drawbacks to isolating a layer. Different work styles I guess.

You need to post more questions here

Sadly we loose the move, rotate, scale, Gizmo,

The gizmos still work in 2DWireframe, you just have to start the command first.

and the UCS icon is a small single line which is harder to pick up and more around.

Right click on the UCS icon > UCS Icon settings > Properties (or type UCSICON at the command line) and change it to a 3D style and make sure it's 3 lines wide

LayerISO can be useful but it freaks me out because it doesn't actually do what it really should do, that is hide every other layer, it just locks it a makes it opaque, the freaky bit is when running a selection set, the other layers look to be selected but the operation won't be performed on them, can be spooky.

As Rob said, there are "Settings" for LAYISO, Default is "lock & fade", but you can change it to "Off" instead. Same for LAYFRZ, Freeze globally or VPFreeze.

With regard to reducing the number of objects on screen, I do 95% of my work through a large single viewport in Conceptual Visual Style. There's nothing that can be done from the Modelspace tab that can't also be done through a Viewport, but you have a lot more control over object display within a VP, so it's win-win IMO. Freezing Layers is better for computer performance than turning them OFF because objects that are "OFF" remain in AutoCAD's memory and AutoCAD considers them during any command where those objects could be affected, whereas when you Freeze an object, AutoCAD releases it from memory and does not do any further calculations on it until/unless it's thawed. Using VPFreeze, you're only Freezing/Thawing objects in the current VP, so if/when you need to see something that's not currently displayed because you either have the object or the layer isolated, just bump back into MS or another VP that has different layers frozen.

Have a look at LayerISO settings. You can have layers turned off when layer isolate is applied. It's another case of AutoDesk turning on new "features" by default, often leaving people wondering about the "old" way.

Well noted Rob, I am late to the party, and reading through the thread, I was going to mention that, as soon as I saw the OP's previous post.

How on earth do we access VPFreeze??? The only place I find this is by opening up the layer manager and clicking the VP freeze button. There's no VPFreeze command and there's nothing in the Help to say where to even access it. There's also no easy way to unlock ALL locked layers other than again by opening up the layer manager window and selecting all layers by control 'A' then clicking the lock icon, ack..tedius.

It's the same button as LAYFRZ. Just do it while in an active viewport.

Command LAYFRZ works for VPFREEZE after activating the viewport. No buttons needed.