Tag Archives: AutoCAD

Bloatware – a tale of two CAD applications

You may have seen me mention in passing that AutoCAD is bloatware. That’s not just the general grumpy-old-user moan you see from long-term users like me, who can remember when AutoCAD used to fit on one floppy disk.

Yes, programs get bigger over time as new functionality is added and old functionality needs to be retained. Hardware gets bigger, better, faster over time to compensate for that. I get that. Understood.

The AutoCAD bloatware problem is much more than that. AutoCAD is literally ten times the size it needs to be, to provide the functionality it does.

How do I know? BricsCAD proves it. Here’s what I mean.

BricsCAD V17.2 64-bit Windows Download
Downloaded File Size (KB)
BricsCAD-V17.2.03-1-en_US(x64).msi 248,812
Total (1 file) 248,812 (100%)
Equivalent AutoCAD 2018 Downloads
Downloaded File Size (KB)
AutoCAD_2018_English_Win_64bit_dlm_001_002.sfx.exe 2,065,829
AutoCAD_2018_English_Win_64bit_dlm_002_002.sfx.exe 328,277
AutoCAD_2018.0.1_64bit_r2.exe 120,663
AutoCAD_2018_Product_Help_English_Win_32_64bit_dlm.sfx.exe 180,013
Total (4 files) 2,694,782 (1083%)

Which dog is which? They’re both cute, but which would you put your money on in a race?

(Original image: Przykuta)

(Original image: Lisa Cyr)

I’m actually being very generous to Autodesk in this comparison. The two primary AutoCAD download executables alone expand from 2.4 GB to 5.2 GB before install, requiring a total at least 7.6 GB of disk space before we even get to the same ready-to-install point as BricsCAD’s 0.24 GB MSI file.

No, it’s not because BricsCAD is a cut-down application compared with AutoCAD. The opposite is true. Overall, BricsCAD is significantly more feature-rich than AutoCAD. It near-exactly duplicates over 95% of AutoCAD’s functionality and then adds a big slab of its own on top of that. Some of it is in paid-for optional extras, but the code that provides that functionality is still included in the same small download.

This issue isn’t unique to AutoCAD. Super-morbid obesity seems to be standard among Autodesk products. The AutoCAD-based verticals that add a comparable level of functionality to that the BricsCAD download includes are much bigger again!

Anybody care to explain what’s going on here?

AutoCAD 2018.0.1 mystery partially resolved but questions remain

As I mentioned earlier, the release of AutoCAD 2018 was followed almost instantaneously by the first update, 2018.0.1. At the time of writing, there was no official information about this update. Some information is now available, but more questions have arisen.

If, like me, you don’t/won’t/can’t have Autodesk desktop app running on your systems, the only current official way to get at the download is using Autodesk Account (but read the whole of this post before you go there). That’s also how you get at information about the update. Go to Management > AutoCAD > Downloads > Updates & Add-ons. From there, it’s not obvious how to get the information, but it’s under More options.

From there, pick View Details. This will show you the following information (after you pick More):

As you can see, the severity is considered high. If you pick View release notes, you can see the readme, or you can go straight to it if you have this direct link. Here are the fixes described in the readme:

  • Occasional crashes when ending an AutoCAD session using specific API code no longer occur.
  • Publishing annotative multiline attributes no longer results in incorrect annotative scaling.
  • PFB fonts can now be compiled successfully as SHX files.
  • The border of a mask is no longer plotted in PDFs when “Lines Merge” is turned on.

Although it would be easy to have a go at Autodesk for shipping a product that needs fixing within hours of release, that wouldn’t be entirely fair. No software is flawless. Stuff happens, and the sooner fixes are provided to resolve that stuff, the better. So I commend Autodesk for getting this fix out quickly.

That doesn’t mean Autodesk is blameless, though. Read on.

First, the way the information about this update was (or wasn’t) disseminated was sub-optimal. It has required too much prodding and guesswork to get to the point we are now, and we’re still not where we should be.

Next, there’s scant information in the readme. I don’t see any documented way of including this fix in a deployment, for example. That means it’s not possible to create a one-step automated install without resorting to trickery.

Further, this update isn’t available on the main Autodesk site. It needs to be. Even if you know the version number to look for, a search at autodesk.com will come up blank:

Using the Autodesk Knowledge Network Download Finder won’t help, either:

Fortunately, these direct links appear to work:

This brings me to my fourth point of criticism. See that the 64-bit executable has “r2” on it? The one I downloaded on 23 March doesn’t. The 64-bit executables are similar in size to each other but the binary content is different. The 32-bit 2018.0.1 has a date of 22 March and the 64-bit 2018.0.1 r2 has a date of 24 March. So it looks like the patch has been patched, at least for 64-bit users.

Information on this patch-patch is non-existent. Should somebody who downloaded and applied the 64-bit 2018.0.1, download and apply 2018.0.1 r2? Will that work? Do they need to uninstall 2018.0.1 first? How should they do that? Will the 32-bit 2018.0.1 also be updated to r2? Should those users hang off a few days to avoid wasting time or go ahead with what’s there now?

Over to you, Autodesk.

AutoCAD 2018 – why did the DWG format change?

In my review of AutoCAD 2018, I had this to say about AutoCAD 2018’s changed DWG format:

Why does AutoCAD 2018 need a new DWG format? It probably doesn’t. The 2013 DWG format is capable of holding pretty much anything you want… Although Autodesk cites performance reasons with certain drawings, I strongly suspect the new DWG format was introduced purely to make life difficult for competitors, and to encourage wavering customers to stay with Autodesk for fear of losing compatibility. In other words, it seems likely this is an anti-competitive change rather than a technical one.

In a recent blog post, highly respected Swiss-based Autodesk development and research person Kean Walmsley had this to say on that subject:

The main reason for the break in compatibility is some longer-term work that’s going on inside the AutoCAD codebase. For now this is really only surfacing in small ways – I expect it’s contributing some performance benefits, for instance – but the work is absolutely critical to the long-term viability of the product.

Kean’s a straight-shooter and I’m always ready to be corrected if it can be shown that I’m wrong. So I would be interested to learn more detail about this long-term work that’s critical to the long-term viability of the product. It might be good news for customers or really terrible news. If the groundwork is being laid for a file format that’s more heavily cloud-reliant or subject to continuous change, say, that would be an absolute tragedy for customers.

Autodesk is clearly manoeuvring customers into a position of maximum tie-in using various nefarious means, and if the DWG format change is part of that then it’s to be condemned. Maybe further information would help alleviate such concerns. Kean can’t provide that information, and neither can the selected bloggers who were given some insight under NDA last week, but I’m sure someone at Autodesk could. That is, if there really is nothing to worry about.

Kean also had this to say:

AutoCAD continues to be a core part of Autodesk’s business – and it continues to receive significant investment in terms of development resources – but don’t expect that to translate to buckets of shiny new features: AutoCAD’s feature maturity means the investment is rightly being focused in other areas (at least for now).

This had me wondering if Kean mistyped “immaturity”, because almost every AutoCAD feature from the last decade was released immature and only the lucky few eventually got finished. There’s a huge mass of outstanding work left to do in AutoCAD just to bring its existing half-baked features up to scratch, practically all of which could be done without disrupting customers with a new DWG format.

As for the feature set itself being mature, I can’t agree with that, either. Maybe it’s considered mature within Autodesk because of defeatist thinking about what’s possible with DWG-based CAD software? Kean’s comments seem to reinforce that impression. From where I’m standing, the lack of progress in recent AutoCAD releases demonstrates a severe lack of imagination and hunger to improve the product, not any inherent natural plateau in CAD development.

I believe this because Autodesk’s keener competitors have shown that no such plateau exists. Bricsys has proven that it’s very possible to improve an AutoCAD-like DWG-based product out of sight with genuinely useful and productive new features, and they can do it without changing the DWG format. Incidentally, my preliminary tests indicate BricsCAD V17 opens and saves DWG significantly faster than AutoCAD 2018, again without the need for a new format. More on that in a later post.

Back to Kean:

This is a tricky balance – and could easily be interpreted as a big company not caring about (some of) its users and only being interested in milking its cash-cow – but the work happening behind the scenes is significant and I believe will ultimately prove to be of real value to our customers.

Real value? History has taught me to be dubious about that. Many things that Autodesk promotes as being of value to customers turn out to be of net negative value. Time will tell with this one.

Sorry, but I really don’t believe that Autodesk cares about AutoCAD and its users as anything but an income source. I know there are still honest, hardworking, enthusiastic people within Autodesk (like Kean) who want to improve the product on behalf of customers. Good luck to those people, because their efforts are being stymied by management. The results we’re seeing out here in customer land are dismal, and no matter what spin is put on that, it must be disheartening.

Autodesk people, caring about users? Sure. Autodesk, the public listed company, as directed from the top? Nope. Autodesk’s actions and inactions tell me otherwise. Zero cares are given. No words can fix that, no matter who they come from.

AutoCAD really is being treated as a cash cow; hang one of those bells around its neck and be done with it.


(Original image: Daniel Schwen)

AutoCAD 2018 – disable InfoCenter

Here’s another AutoCAD 2018 download, just in case you haven’t had enough.

If you want to disable AutoCAD’s InfoCenter (and you should, unless have a specific reason for keeping it – here’s why), go get the updated download from uber-expert Owen Wengerd’s ManuSoft Freebies page. It works for AutoCAD and AutoCAD LT.

AutoCAD 2018 – there’s already an update

If you downloaded and installed AutoCAD 2018 yesterday and don’t/won’t/can’t have Autodesk desktop app running on your systems, you may already have another download to do, because AutoCAD 2018.0.1 is out.

At the time of writing there is no sign of this update on Autodesk’s main site, but you can get at it using Autodesk Account. Go to Management > AutoCAD > Downloads > Updates & Add-ons.

All that’s downloaded is an executable. No readme, nothing. There is currently no official information about the reasons behind this update, what it includes, what it might affect, how to include it in a deployment, etc. You’ll need to make up your own mind whether to install this update now or wait for information about it. I suggest the latter.

Of course, if you’re using desktop app and allowing automatic updates, you don’t need to worry about any of that that. Just trust Autodesk to not break anything and hope for the best.

What’s the worst that could happen?

Edit: see this post for further information.

AutoCAD 2018 – bear this in mind

Given the dearth of new functionality in AutoCAD in recent years, it’s understandable that Autodesk has taken to claiming credit for the same thing twice. The same features have been touted once for the 2017.1 mid-term update and again as 2018 new features. Even I fell for it, listing linetype gap selection as a 2018 feature in my original review.

For the purposes of reviewing the earlier AutoCAD releases and AutoCAD 2018 as upgrades, I have included the 2017.1 features in 2018, not 2017. Some of those features are praiseworthy, and there have been some minor improvements to some of the 2017.1 features in 2018, but let’s count them just once, please.

Blogs and sites that just regurgitate Autodesk’s take on what’s new in AutoCAD 2018 might inadvertently repeat the double-dipping. Bear that in mind when you read reviews.

AutoCAD 2018 – 2/10, would not rent

It must be March, because another AutoCAD has just been launched. Despite this one being codenamed Omega, I’ve been assured it’s not the final AutoCAD release. The good news is that AutoCAD 2018 is twice the upgrade that 2017 was. But hold your excitement, because the bad news is that 2017 was only a 1/10 upgrade.

Autodesk has continued the well-established tradition of acting like a low-quality sausage machine, reliably popping out consistently unexciting products at regular intervals.

Here’s what’s in this year’s underwhelming sausage:

  • Xrefs now default to relative path attachment and there are a few associated tweaks including find/replace path
  • You can select objects off-screen (handier than it sounds)
  • File dialogs remember settings
  • A couple more dialogs can be resized
  • There are a couple more tiny user interface tweaks
  • The stuff from 2017.1 is included, of course, some seeing minor improvements since then
  • iDrop support is gone (will anybody miss this?)

Thrilled? Me neither. The xref stuff is worthwhile, and Autodesk does deserve credit for not adding any seriously undercooked “headline” features or pointless eye candy. That, along with the 2017.1 stuff, quietly fixing some old bugs, sorting out a few old feature issues and some unsung but worthy API documentation improvements, is just about enough to make this a 3/10 upgrade.

But wait! Autodesk earned itself a minus point to take it from 3 to 2 by inconveniencing customers with yet another API change (so your 3rd party stuff will need updating), and most unfortunate of all, a DWG format change. We had grown used to enjoying a lack of compatibility issues (with plain AutoCAD, anyway – don’t get me started on the verticals), thanks to the 2013 format surviving five releases rather than the traditional three. Now that’s over.

Why does AutoCAD 2018 need a new DWG format? It probably doesn’t. The 2013 DWG format is capable of holding pretty much anything you want, as Bricsys has shown with BricsCAD V17’s ability to compatibly store 3D parametrics and (optional) BIM and sheet metal features within that format. The changes to AutoCAD 2018 don’t come anywhere near that level of complexity. Although Autodesk cites performance reasons with certain drawings, I strongly suspect the new DWG format was introduced purely to make life difficult for competitors, and to encourage wavering customers to stay with Autodesk for fear of losing compatibility. In other words, it seems likely this is an anti-competitive change rather than a technical one.

Oh, and the desktop icon is the same as 2017, so if you run both releases side by side while you’re waiting for your add-ons to be updated, you’ll find it difficult to see at a glance which shortcut is which and what’s already running. Minor irritant, but an unnecessary cheapskate move.

There are alleged to be performance improvements; probably true in places. I did notice a slight improvement in 3D Orbit performance, with AutoCAD 2018 now about up to BricsCAD standards. However, this aspect of AutoCAD 2017 performance wasn’t a problem with the sub-20 MB drawings anyway, so you may not notice a difference.

In my experience with the Beta, AutoCAD 2018 was frequently appallingly slow, particularly start-up time, which was atrocious. Those 14 million lines of code have added up over the years, and AutoCAD 2018 is bloatware; literally ten times the size of the more fully-featured BricsCAD V17 Platinum, which starts up in the blink of an eye. However, I will reserve final judgement on AutoCAD 2018 performance until I have had chance to properly test the production version. I have not factored performance in to my overall mark.

There’s nothing in this release that comes close to justifying the annual maintenance fees, let alone throwing away your perpetual license and signing up for subscription. If Autodesk wants customers to think it will be worthwhile signing up for a lifetime of rental fees in the hope that substantial improvements will result, this weak release represents a singularly unconvincing argument.

Overall, 2/10. This is a sub-mediocre release that shows once again that AutoCAD is in maintenance mode. Autodesk appears completely disinterested in AutoCAD other than as a cash cow, and severely lacking in imagination about ways of seriously improving it. Omega might not be the final AutoCAD release, but given the glacial level of improvement being shown, it might as well be.

33 years of AutoCAD upgrades rated – part 5 – summary

In this final post of the series, I’ll examine the patterns that have emerged from the upgrade history I rated in parts 1 to 4. Bear in mind I’m only assessing the DOS (up to R13) and Windows (from R12 on) versions of the full version of AutoCAD. Of course, this only represents my opinion of those releases and is bound to be biased by the uses I and my users have for the software. Your experiences and opinions will almost certainly vary.

What can I say? My assessment is based on a third of a century of experience, and I’ve tried to be as objective as I can. I’m not unique in perceiving the decline of the AutoCAD upgrade; you’ll see the same said by long-standing customers and experienced independents all over the place. Ralph Grabowski, for example:

The new feature list for AutoCAD’s annual “big-R” release has become so short that I stopped producing my annual “What’s Inside? AutoCAD” ebook series in 2013.

 
Back to my own assessment, here’s a graph that shows how I rated the releases:

One thing’s obvious and that’s the permanent drop in the rate of improvement that set in with the onset of the annual release cycle. My average rating for AutoCAD Version 2.0 to 2000 is 7.7. For 2000i to 2017, it’s 3.4. Autodesk switched to doing half as much worthwhile development between releases, but charged the same upgrade fee. Value for money halved.

We entered the era of an endless stream of annual releases with fewer genuinely useful new features. Worse, the abbreviated cycle meant most of those features went into production half-baked in design, implementation or both. Some of those undercooked features (the lucky ones) got some attention in the next release. Many more of them never got fixed, or got quietly removed later, or eventually got patched up years after the user base had ignored them to death.

Have a look at the decline from 2010 downwards. The average for the last five releases is 2.0. The rate of improvement per release, starting from a low point, took a nose dive. Value for money, which was poor, is now dire.

Conclusion? AutoCAD is in maintenance mode. Autodesk’s attention (and investment) is elsewhere and it is just going through the motions of updating the software. Progress has stalled. Inspiration is AWOL.

Nevertheless, through all this, we have still paid for new releases in various ways, and in huge numbers. No wonder Autodesk is convinced we’ll be silly enough to pay over the odds to rent software; there’s a precedent.

The more Autodesk has moved away from the optional upgrade model, through optional maintenance*, then effectively compulsory maintenance**, then finally to the compulsory rental model***, the weaker the upgrades have become. Autodesk no longer feels compelled to put in the development effort that will convince customers to shell out for the advantages provided by a new release.

Autodesk wants an endless revenue stream in return for merely providing access to the software, rather than as a reward for improving it: money for nothing. That’s Autodesk’s dream, and an understandable one. For customers, it’s a nightmare: nothing for money.

Part 1 – AutoCAD Version 1.4 to Release 11.
Part 2 – AutoCAD Release 12 to AutoCAD 2002.
Part 3 – AutoCAD 2004 to AutoCAD 2010.
Part 4 – AutoCAD 2011 to AutoCAD 2017.
Part 5 – Summary.

* Maintenance was previously called VIP and then Subscription.
** Autodesk restricted the availability of upgrades, priced it out of the market, and in some cases only sold perpetual licenses bundled with maintenance, before finally eliminating upgrades altogether.
*** Autodesk’s third attempt at rental (there were failed attempts in 2001 and 2013) was first called Desktop Subscription and then just subscription. I generally call it rental to avoid confusion with The Maintenance Formerly Known as Subscription.

33 years of AutoCAD upgrades rated – part 4

In this series of posts, I am looking back on all the AutoCAD upgrades I’ve experienced over the years and rate each of them out of 10. See post 1 for information about what the ratings mean.

In part 4, I rate AutoCAD 2011 to AutoCAD 2017.

  • AutoCAD 2011 (March 2010): 5 – Object transparency was a very important enhancement for some. The X-Ray and other visual styles made 3D editing more efficient. Object visibility (independent of layers) was handy but has confused some DWG recipients ever since. Selection Cycling, Add selected and Select Similar (which had been in AutoCAD-based verticals for a while) were true productivity enhancers. Geometric constraints were improved but still confined to 2D, as they are to this day. Finally, Autodesk’s first of several failed attempts at an online Help system meant this wasn’t such a good release as it could have been.
  • AutoCAD 2012 (March 2011): 4 – Array enhancements were a good idea, reverting to the 80s for their user interface was less smart. Content Explorer was woeful in just about every way, but provided some otherwise unavailable searching features. I found the in-canvas controls of benefit. Support for ECW files was important to my users. The Auto-command entry was a good idea that worked well enough in this release (but performs increasingly poorly with each new release, to the point where I can’t tolerate it these days). There were a few 3D enhancements. Yet another (the 12th?) 3D to 2D method was added, Model Documentation, which as usual for a major new feature wasn’t nearly finished. Don’t get me started on the nudge feature. Moving CAD vector objects around by effectively random amounts based on pixel sizes was as dumb an idea as I can remember. Help still sucked.
  • AutoCAD 2013 (March 2012): 3 – This release ushered in a new API and DWG format as expected. Less expected was this DWG format lasting 5 releases, which was a bonus out here in user land. There were a bunch of Cloud features destined to be ignored by most but very useful to some. Model Documentation improved almost to the point of production usability, but has stayed stuck at the almost-there stage ever since. Help got even worse and has never recovered. Property preview and lots of minor tinkering with various features were worthwhile but didn’t add up to enough to make this a must-have release; needing compatibility with the new DWG format was more likely to do that.
  • AutoCAD 2014 (March 2013): 2 – A basic free file tabs utility was pulled into the core without improvement, a disappointment to those of us used to much better functionality from 3rd party developers. There were some security enhancements that got in the way for many people, but without addressing the main security problem (automatic loading of code from implicit paths at startup). The command line grew in functionality and got slower (again), and there was a bit more minor tinkering here and there. Creating clockwise arcs would have been impressive in the mid 80s, but here only showed how slow Autodesk had become at fixing long-standing functionality issues.
  • AutoCAD 2015 (March 2014): 2 – Lasso was a useful change, as were improved dragging and selection. Unless you’re into point clouds, there’s not much else here of practical use, though. Application Manager was the first step down the dark path leading us to the attempted automatic update doom that lay ahead, and gets no points from me. Darkening the default appearance of the interface to resemble Paint Shop Pro from 2007 was no substitute for substance. At least it was optional. The removal of the option to use textual status bar toggles wasn’t optional. It represented a particularly petty piece of Autodesk interface arrogance and a classic example of Autodesk breaking the unbroken while leaving the broken broken. The New Tab (later called Start) was terribly slow and best bypassed. It’s unfortunate that Autodesk made an API change here, breaking from the established pattern of changing both DWG and API every three years.
  • AutoCAD 2016 (March 2015): 2 – Those people who found a use for the execrable Content Explorer would have been upset by its removal. I wasn’t. Geometric osnap, improved revision clouds, dimension command changes, PDF and point cloud improvements, ability to attach Navisworks files, not much else. No API or DWG change, which was good, but nothing much to see here, move along please.
  • AutoCAD 2017 (March 2016): 1 – Graphics performance, which to Autodesk’s credit has been quietly but significantly improved in recent years, got another boost. Performance in other areas has continued to get worse. Just starting up an older AutoCAD release or a competitor’s product is like a breath of fresh air and shows how bloated, slow and inefficient AutoCAD has become. Share Design View was useful to some, within its limitations. PDF import was sometimes useful and a nice-to-have; done to a higher standard than we have come to expect, it was improved further in 2017.1. Dialog box size enhancements were welcome but at least 10 years overdue. Autodesk desktop app is notable only for its awfulness. Terrible idea, dreadful implementation. Migration was finally looked at 11 years after it was broken, and about 8 years after I permanently gave up on it. I didn’t even bother testing the new version because I’ve arranged things so I can do very nicely without it, thanks. Associative centerlines and marks were a potentially good idea but the implementation was atrocious. Deliberately removing 192,192,192 transparency from button icons was an act of sheer bastardry that was worth at least -1 just on its own. Another API change after only 2 years was an inconvenience but at least 2017 kept the 2013 DWG format for the 5th release in a row, probably the best thing Autodesk has done for AutoCAD customers in recent years. Long may that continue.

Part 1 – AutoCAD Version 1.4 to Release 11.
Part 2 – AutoCAD Release 12 to AutoCAD 2002.
Part 3 – AutoCAD 2004 to AutoCAD 2010.
Part 4 – AutoCAD 2011 to AutoCAD 2017.
Part 5 – Summary.

Do you agree or disagree with these assessments? Feel free to share your memories and experiences.

BricsCAD’s LISP kicks sand in the face of AutoCAD’s

If you’re a power user or CAD Manager transitioning from AutoCAD to BricsCAD, one of the things you’ll like is that almost all of your LISP routines will just work. That’s not an statement that can be made about various Autodesk products that bear the AutoCAD name, such as AutoCAD 360, AutoCAD LT and AutoCAD for Mac.

It’s not just simple old AutoLISP code that runs in BricsCAD, but complex dialog routines that use DCL, and Visual LISP stuff that uses ActiveX. Yes, even on the Mac and Linux platforms. Some DOSLib functions are built in and the rest can be loaded, as with AutoCAD. Even OpenDCL is supported. It’s a quite astonishingly high level of compatibility.

But it’s not 100%. There are minor incompatibilities, system variable and command-line differences that cause problems in a handful of cases. It’s often possible to work around these and still retain the same code that works in both AutoCAD and BricsCAD. Reporting LISP bugs and incompatibilities to Bricsys generally gets them fixed super-quick.

Also super-quick is the speed at which your code will run. It’s immediately noticeable when running any LISP code that needs to do a bit of processing that it just gets done faster in BricsCAD than AutoCAD. Fast enough to extract the following comment from one of my AutoCAD users trying out a linework cleanup routine in BricsCAD:

Wow.

 
User impressions are one thing, but how about measurements? Today, I had a support job to do that involved running one of my LISP routines. I ran it on both AutoCAD 2017 and BricsCAD V17 on the same PC. AutoCAD took 2970 seconds (about 49 minutes), BricsCAD 1030 seconds (about 17 minutes). Over half an hour saved on one operation. That’s 2.88 times faster, which is consistent with my previous observations with a variety of routines.

Upshot: if you’re doing work where there’s a lot of LISP processing going on, switching to BricsCAD is going to save you a shedload of time.

There is a downside to BricsCAD’s LISP, and it’s a big one; no VLIDE. No equivalent, either. There are various programming editors around that can help with editing code, but no substitute for integrated debugging. It means if you’re a power user, CAD Manager, developer or support person, you’re probably going to have to keep one working copy of AutoCAD around even after you’ve completed the transition to BricsCAD.

Because VLIDE has been in maintenance mode for over 15 years it remains virtually unchanged year after year (including ancient bugs). So it doesn’t matter that much which AutoCAD release you have hanging around. Assuming you’re a perpetual license holder, when you drop the maintenance contract on one of your AutoCAD licenses, you’re entitled to keep using the software as long as you wish, albeit only the current release at the time the contract ends. How long the software will keep working is another matter, depending as it does on factors not entirely within your control.

This is an imperfect solution. Even keeping a copy of AutoCAD around won’t help much if you’re debugging a problem caused by something specific to BricsCAD. Filling the VLIDE hole is something Bricsys needs to work on.

33 years of AutoCAD upgrades rated – part 3

In this series of posts, I am looking back on all the AutoCAD upgrades I’ve experienced over the years and rate each of them out of 10. See post 1 for information about what the ratings mean.

In part 3, I rate AutoCAD 2004 to AutoCAD 2010.

  • AutoCAD 2004 (March 2003): 5 -The return of Express tools was a good start. Better still, Autodesk’s abortive attempt to sell Express Tools as an extra meant some effort had been put into improving them and they were much bigger and better in 2004 than they were in 2000. The death of the annoying UI stuff didn’t come a moment too soon. This upgrade had a few other useful additions and the new DWG format was more efficient, but overall nothing to get too excited about.
  • AutoCAD 2005 (March 2004): 4 – Autodesk introduced the Sheet Set Manager with this release; I guess one day they’ll get around to finishing it. Likewise, tables were useful but still imperfect today. Improved hatching. Fields. No DWG or API change. Mediocre.
  • AutoCAD 2006 (March 2005): 5 – Dynamic blocks (2D only) and in-place block editing came along with a bunch of extra palettes to make this a decent release in terms of new functionality. No DWG or API change. Big changes to customization, though, with the CUI command and format. CAD Managers had some serious rethinking to do. Migrating settings never worked properly for me in a custom environment from this release on. Losing the ability to easily customize toolbars directly on-screen was a pain; despite some advantages the CUI interface was excruciatingly slow, with a poor UI and bugs that remain to this day. No DWG or API change. This is the release where I really started to notice AutoCAD performance start to decline as a result of bloat and/or poor development, a trend that was to continue long-term and affects the value (and my rating) of each upgrade.
  • AutoCAD 2007 (March 2006): 6 – The Dashboard (later to become the Ribbon), visual styles, many 3D improvements, better rendering and new 3D to 2D methods make this a decent upgrade that 3D users in particular wouldn’t want to do without. The new DWG format and API version were inconvenient, but by now an expected part of the cycle.
  • AutoCAD 2008 (March 2007): 2 – Table enhancements were very handy for people using huge tables in their drawings, and most of the text enhancements were welcome. Annotative scaling was the big drawcard in this release, but Autodesk released it unfinished and therefore got it very wrong. The _XREF _XREF _XREF bug infested drawings and led to all kinds of apparently unrelated problems that persisted for years. Multileaders were another one of those good ideas that Autodesk insists on implementing badly, in this case by splitting off the styles from dimension styles and causing backward compatibility issues. The unreconciled layer warnings proved annoying for most and harder to turn off than they should have been. Overall, AutoCAD 2008 was a release to skip, even if you had paid for it.
  • AutoCAD 2009 (March 2008): 6 – The Ribbon release, and arrival of the Big Red A. The Ribbon was horribly slow and some people thought Autodesk should have dealt more with substance than appearance, but there were many other changes (mainly UI) that provided a genuine practical benefit. I think the ViewCube is awesome; the steering wheel, not so much. On the negative side was the mass of “idiot box” dialogs that kept popping up to interrupt your flow. You could turn them off, but not pre-emptively. The massive tooltips that repeatedly rose up to obscure everything were beyond annoying. The layer palette would have been good had it not been such a performance drag. Autodesk put a lot of effort into Action Recorder but failure to listen to what people wanted in a macro recorder meant that effort was wasted on a flop.
  • AutoCAD 2010 (March 2009): 6 – Lots of effort was put into 3D, particularly some clever work with surfaces. Geometric constraints were big news, but not as big as they could have been had they not been restricted to 2D. A downside to this release was that it removed the do-it-yourself inter-PC license transfer mechanism and introduced a web-based method that requires Autodesk’s ongoing cooperation (and existence). Better PDF support and non-rectangular viewports and xref clipping were welcome. Less welcome was Initial Setup, another of Autodesk’s many reviled attempts to get in your face at startup rather than letting you draw. This Ribbon was better than its predecessor, but still a Ribbon so most users ignored it. The new DWG format and API version were inconvenient but expected. Deserves some credit for being the last AutoCAD release with a decent Help system.

Part 1 – AutoCAD Version 1.4 to Release 11.
Part 2 – AutoCAD Release 12 to AutoCAD 2002.
Part 3 – AutoCAD 2004 to AutoCAD 2010.
Part 4 – AutoCAD 2011 to AutoCAD 2017.
Part 5 – Summary.

Do you agree or disagree with these assessments? Feel free to share your memories and experiences.

33 years of AutoCAD upgrades rated – part 2

In this series of posts, I am looking back on all the AutoCAD upgrades I’ve experienced over the years and rate each of them out of 10. See post 1 for information about what the ratings mean.

In part 2, I rate AutoCAD Release 12 to AutoCAD 2002.

  • AutoCAD Release 12 (June 1992): 9 – Big, big changes. A mass of UI and other improvements. Lots of new dialog boxes. The first release that retained its predecessor’s DWG format, which was very handy. DCL gave LISP and C programmers the ability to create dialog box commands. The first usable Windows version (the R11 extension version was a shocker). Came with a Bonus CD full of extra stuff; a big deal in those days of limited connectivity. Autodesk’s upgrade amnesty (upgrade from any earlier release for $500 in the USA) made this extremely strong value for money, too.

    • AutoCAD Release 13 (November 1994): 6 – Many of you will remember this most infamous of all AutoCAD releases. Too ambitious, long overdue yet released too early, full of bugs, terribly unreliable, markedly slower than its predecessor. Why have I still given it 6? Because of all the many highly useful UI improvements and drafting features it introduced; there were such a huge mass of them I won’t even attempt a summary. Because when running on NT and decent hardware it wasn’t actually that unreliable; running on 16-bit Windows was to blame for a lot of crashes. Because by the time of the final version (R13c4a – the twelfth!), it was not that bad at all, and because Autodesk provided excellent customer service by sending R13c4 out on CD to every registered customer. Because it introduced ARX, allowing C++ developers to do things with AutoCAD that had been impossible before. Because it came with a huge slab of printed documentation (sorry, rainforests). With lots to like as well as dislike, Release 13 was the ultimate curate’s egg release.
    • AutoCAD Release 14 (February 1997): 9 – A big performance effort, masses of bug fixes and many other practical improvements (e.g. hatching, draw order, fully functional object properties toolbar) mark this out as the sort of release that people remember for all the right reasons. The new stuff in this release was added because it would be useful to customers, not because it looked good in an advertisement. Bonus (later Express) Tools gave us a lot of handy stuff, even if it wasn’t officially supported. R14 was an upgrade done right.
    • AutoCAD 2000 (March 1999): 8 – A CAD application being able to open more than one drawing at a time might seem an obvious requirement, but it took until this release for us to get it, and very glad of it we were too. The property palette, layer dialog and lots of right-click options represented worthwhile UI improvements. The integration of Visual LISP (acquired during the R14 cycle as Vital LISP) and access to ActiveX functionality represented a revolution for LISP programmers. Very good upgrade.
    • AutoCAD 2000i (July 2000): -2 – What a difference a year makes! Yes, a that’s minus two for this initial attempt at an annual release (Autodesk didn’t make the timing work for another couple of releases). An emphasis on largely irrelevant-to-users Internet features intended to make Autodesk look all hip and now (anyone tried to access the Point A site lately?), a tie-in to Internet Explorer, annoyingly intrusive UI changes and the removal of the Express Tools, together with a dearth of genuinely useful new features (double-click editing being a noble exception) made this an upgrade only in name. The new Autodesk logo failed to wow customers, who stayed away in droves (at the time we still had that option, and exercised it when we failed to see value for money in an upgrade). A joke at the time was that the ‘i’ stood for ‘ignore’. Worst. Upgrade. Ever.
    • AutoCAD 2002 (June 2001): 3 – The bad things in 2000i were still there in 2002, so that’s a net 0. At least it retained the AutoCAD 2000/2000i DWG format in what was to become a regular 3-year DWG/API cycle, useful for customers and developers. The handful of useful additions (e.g. more associative dimension stuff) didn’t add up to much of an upgrade. At least it was an upgrade, in contrast to the downgrade its immediate predecessor represented.

    Part 1 – AutoCAD Version 1.4 to Release 11.
    Part 2 – AutoCAD Release 12 to AutoCAD 2002.
    Part 3 – AutoCAD 2004 to AutoCAD 2010.
    Part 4 – AutoCAD 2011 to AutoCAD 2017.
    Part 5 – Summary.

    Do you agree or disagree with these assessments? Feel free to share your memories and experiences.

  • 33 years of AutoCAD upgrades rated – part 1

    In this series of posts I will look back on all the AutoCAD upgrades I’ve experienced over the years and rate each of them out of 10.

    This is not a rating of the software in absolute terms, it’s a relative rating of the upgrade. That is, the improvement the software made on its predecessor. AutoCAD 2000i is a much better piece of software than AutoCAD Release 2.5, and given the choice I would rather use the former, no contest. But as an upgrade, 2000i sucked and 2.5 rocked. The biggest improving upgrade is the benchmark and gets 10; the others are rated in comparison. If a release is worse overall than its predecessor, it goes into minus territory.

    In part 1, I rate AutoCAD Version 1.4 to Release 11. This is not quite a full assessment of all AutoCAD upgrades because my AutoCAD experience started with AutoCAD Version 1.4 and there were releases before that, even if they only sold in tiny numbers.

    • AutoCAD Version 1.4 (October 1983): No rating because I didn’t use its predecessor, but if you consider that before this you couldn’t even remove a section of a line, this upgrade ushered in probably the first realistically usable version of AutoCAD.
    • AutoCAD Version 2.0 (October 1984): 8 – Very significant improvements including osnaps, linetypes, rubber banding for a bunch of commands, relative coordinate display, attributes, etc.
    • AutoCAD Version 2.1 (May 1985): 10 – AutoLISP, arguably the most significant new feature in AutoCAD history, came along during the 2.1 era (complete implementation took until 2.18). AutoCAD was the PC CAD leader because of its open architecture; AutoLISP opened that up a lot further and took AutoCAD from leader to winner. The beginnings of 3D, along with a host of other great improvements, made this, for me, the ultimate upgrade in AutoCAD history.
    • AutoCAD Version 2.5 (June 1986): 10 – Large numbers of important new drafting features especially editing and much better undo, along with a maturing of AutoLISP and significant performance improvements, made this a fantastic upgrade too.
    • AutoCAD Version 2.6 (April 1987): 4 – A bit of a stopgap release pending some UI changes to come, but some worthwhile additions such as transparent zoom, point filters and associative dimensions. Not in the same league as the previous few upgrades, though.
    • AutoCAD Release 9 (September 1987): 6 – The UI got a big and useful overhaul including the introduction of pull-down menus. Some very handy things were added to help menu macros work better. Limited in scope by the short timeframe from the previous release, this upgrade was good but not great.
    • AutoCAD Release 10 (October 1988): 8 – Lots of 3D enhancements including UCS and meshes are the highlight here. Viewports helped make 3D drafting more practical and a few AutoLISP enhancements helped make this a worthwhile upgrade. Decent working extended memory functions helped DOS users, particularly as more complex drawings were becoming increasingly common.
    • AutoCAD Release 11 (October 1990): 7 – Superficially identical to its predecessor, this upgrade gave us many improvements that weren’t immediately obvious, particularly two revolutionary (for AutoCAD) features: paper space and xrefs. ADS gave developers a C-based API (actually introduced in R10 OS/2, but DOS was the important one then).

    Part 1 – AutoCAD Version 1.4 to Release 11.
    Part 2 – AutoCAD Release 12 to AutoCAD 2002.
    Part 3 – AutoCAD 2004 to AutoCAD 2010.
    Part 4 – AutoCAD 2011 to AutoCAD 2017.
    Part 5 – Summary.

    Do you agree or disagree with these assessments? Feel free to share your memories and experiences.

    Undo, U, Redo, Erase, Oops differences explained

    It’s been a while since I posted any beginners’ tips, so here goes.

    There are several commands in AutoCAD to do with reversing things you’ve done. They are in some cases subtly different and this can confuse newcomers. Here’s what they do:

    • U – reverses the last command you used.
    • Redo – reverses the last U or Undo operation you performed, if that’s the last thing you did.
    • Undo – displays a set of command options that allow greater control over undoing things. (This is rarely used directly by a user, and is more of a programmer’s tool, so I won’t be going into any detail).
    • Erase – removes from the drawing an object or set of objects as selected by the user.
    • Oops – reverses the last Erase command, even if you have done other things in the meantime. (It also reverses erasures performed by the Wblock command, but such reversal is rarely needed these days).

    Note that many commands also have an Undo subcommand  which is different again from all of the above. For example, start the Line command, pick a few points, then enter Undo while still in the command. Just the last segment will be removed, and you can carry on picking more points. Most subcommands can be abbreviated, and this is true of the Undo subcommand within the Line command. While still in the Line command, enter U and this will have the same effect as entering Undo in full (or the other possible abbreviations Un and Und).

    This is not the case when entering full command names; entering U and Undo at the command prompt will do different things, although command line auto-complete can confuse matters further depending on your settings. I’ll ignore that for the sake of brevity.

    Let’s go through a command sequence that uses all of these things.

    • Enter the Line command (type LINE and hit [Enter]). Pick 6 points to create 5 lines but don’t hit [Enter] yet. While still in the Line command, enter Undo (UNDO [Enter]). This will use the Undo subcommand of Line to undo the last drawn line segment, leaving 4 lines. Pick another 2 points, leaving a total of 6 lines. While still in the Line command, enter U. This will undo the last drawn line segment, leaving 5 lines. Hit [Enter] to finish the Line command.
    • Enter the Line command, pick 4 points to draw 3 lines and hit Enter to finish the command.
    • Enter the U command. The effects of the last command (Line) will be undone, removing all 3 of the lines created by it.
    • Enter the Redo command. The U command is reversed, restoring the 3 lines.
    • Enter the Undo command. This will give you a few options, but the default is the number of steps to undo. Type 2 [Enter] and the last 2 commands will be undone (ignoring the U/Redo), removing the set of 3 lines and the set of 5 lines.
    • Enter the Redo command. The Undo command is reversed, restoring both the 5 lines and the 3 lines.*
    • Enter the Erase command. Select one line from the first group and two from the second, then hit [Enter] to finish the command and those 3 lines go away.
    • Enter the Move command. Select the remaining 2 lines from the first group, hit [Enter] to finish the selection process and pick two points slightly apart to move the lines a short distance.
    • Enter the Oops command. The 3 lines removed by the Erase command are restored, but note that the effects of the Move command are unaffected. If you had used the U command twice to restore the erased lines, the Move command would also have been reversed.

    Clear as mud? There are other possible complications depending on various settings, and there are various user interface options for invoking the commands that I haven’t discussed, but this will do to explain the basics.

    * The information in this post applies to any AutoCAD from the last 30 years, but as the command set in BricsCAD is almost identical, it can be used for BricsCAD too. Mostly. There is one exception; if you use Undo to perform several undo steps at once, then follow that with a Redo, only one undo step at a time will be reversed. If you want to redo everything, you will need to hold your finger on the Enter key to repeat the Redo command until it runs out of things to redo. Depending on what you want to do, this can either be very handy or rather inconvenient.

    AutoCAD 2017 for Mac released, still half-baked

    AutoCAD 2017 for Mac and AutoCAD LT 2017 for Mac have been released. Here’s a video highlighting exciting and innovative new features such as drawing and layout tabs. Despite such stellar advances, it’s safe to say that AutoCAD for Mac remains half-baked, even after all these years. Don’t say I didn’t warn you.

    According to Autodesk, these are the features missing from AutoCAD 2017 for Mac:

    LAYDEL, LAYMRG, LAYWALK and LAYVPI
    Tool palettes
    New layer notification
    Navigation bar
    ShowMotion
    Ribbon*
    DesignCenter**
    Sheet Set Manager***
    Steering wheel
    Feature finder for help
    Model documentation tools
    Dynamic block lookup parameter creation/editing
    Table style editing
    Multiline style creation
    Digitizer integration
    Geographic location
    Simplified, powerful rendering
    Material creation, editing, and mapping
    Advanced rendering settings
    Camera creation
    Point cloud
    Walkthroughs, flybys, and animations
    DWF underlays
    DGN underlays
    Hyperlinks
    Data extraction
    Markup set manager
    dbConnect manager
    WMF import and export
    FBX import and export
    Design feed
    Import SketchUp files (SKP)
    Design share
    3D print studio
    Reference Navisworks models
    Right-click menus, keyboard shortcuts, and double-click customization
    VisualLISP
    .NET
    VBA
    DCL dialogs
    Action recorder and action macros
    Reference manager (stand-alone application)
    Password-protected drawings
    Digital signatures
    Workspaces
    User profiles
    Autodesk desktop app
    Migration tool enhancements
    CAD standards tools
    CUI import and export
    BIM 360 add-in
    Performance Reporting
    Sysvar monitor

    * To be fair, AutoCAD 2017 for Mac does have a Ribbonesque feature, albeit one that that looks more like the pre-2009 Dashboard than the Windows-style Ribbon.

    ** Autodesk claims Content Palette to be roughly equivalent to DesignCenter, but it claimed that (wrongly) about the awful and short-lived Content Explorer. It’s wrong here too; Content Palette on Mac has nowhere near the functionality of DesignCenter on Windows.

    *** Autodesk claims AutoCAD for Mac’s Project Manager is functionally equivalent to the missing Sheet Set Manager.

    Also, some PDF export features don’t work when plotting, only when using Publish.

    No workspaces? No model documentation? No hyperlinks? No table style editing? Various kinds of reference files unsupported? No Visual LISP or DCL? Still? Come on Autodesk, you’re not even trying.

    That’s before we get on to the lack of third party applications, vertical variants and object enablers. Is Autodesk expecting full price for this thing? Really?

    It’s not all bad news, though. Not having Autodesk desktop app is no handicap at all. Also, according to Autodesk the following features are unique to AutoCAD for Mac:

    Coverflow navigation
    Multitouch gestures
    External reference path mapping
    OpenGL Core Profile support
    OS notification for updates
    Language switching in product

    Well that’s all right, then.

    When is a subscription-only update not a subscription-only update?

    Before I get started, I want to clarify the meaning of the word ‘subscription’. For about 15 years, the word Subscription (note the initial capital) meant something specific for Autodesk customers. It meant you had bought a perpetual license and instead of paying for periodical updates, you paid for a year’s Subscription in advance. In allowed access to any new release that appeared during that year plus various other benefits.

    That thing that was once called ‘Subscription’ has now been renamed ‘maintenance’ (no initial capital) in Autodeskspeak. So what does ‘subscription’ (no initial capital) mean? Rental. You pay in advance for use of the product for a period and when you stop paying, you stop using the product. This is now the only way to obtain Autodesk software you don’t already own. In addition to access to any new release that appears during the subscription period, it provides other benefits similar to what is now called maintenance.

    To confuse matters further, Autodesk briefly called rental ‘Desktop Subscription’ (note the initial capitals) and it’s still possible to find remnants of that terminology in current Autodesk documents. It’s also possible to find ‘Subscription’ and ‘subscription’ used interchangeably on the same Autodesk web page:

    autodeskisitsubscriptionorsubscription

    Minor quibbles aside, the important thing to note is that the term ‘subscription’ as currently used by Autodesk means something very specific. It means rental. When something is described as ‘subscription-only’ it specifically excludes ‘maintenance’ and other perpetual license customers. And that’s how the AutoCAD 2017.1 update was described:

    autocad2017-1subscriptiononly

    That subscription-only status of this update is what set me off. Preventing paying customers from accessing something that includes bug fixes is most unpleasant, and I felt obliged to say so. But it doesn’t appear to be the case. That subscription-only status is getting rubberier by the minute.

    • Autodesk states 2017.1 is “the first subscription-only update”. In addition to using the term ‘subscription’, being the first of something implies that it’s different to what happened before. That can’t mean that it’s available to all customers, because that’s what has happened with updates in the past. It also can’t mean maintenance customers can also access it, because that has happened for years for various enhancements, add-ins, productivity packs, etc.
    • Somebody as smart as Jimmy Bergmark (and that’s very smart indeed) is convinced that “even security enhancements and bug fixes are only available for subscription customers”.
    • There is no sign of 2017.1 on the public AutoCAD Downloads page.
    • As a maintenance customer, I didn’t receive notification of the update. However, I can see it in my Autodesk Account portal. It was apparently released quietly on 15 September 2016 for most languages, with French and German lagging behind for whatever reason.
    • The download is not restricted; anybody with the URL can download it (e.g. English 64-bit exe). I have no idea how Autodesk intends to restrict this update to certain customers.
    • I have been informed privately by an Autodesk person who should know that customers on both subscription and maintenance will get the update.

    This confusion can be traced to Autodesk’s decision to call rental ‘subscription’, a name that already had a significant, long-established and totally different meaning in the Autodesk lexicon. Because I can’t think of a logical reason for Autodesk to do this, I strongly suspect the idea was to obfuscate the changes to licensing by deliberately confusing customers. If so, congratulations, it worked. I’m baffled.

    Edit: Heidi Hewett has updated her post:

    autocad2017-1notsubscriptiononly

    Although the Preview Guide still only mentions Subscription (which shouldn’t have a capital these days, but does here), I think that’s pretty much cleared up the confusion now.

    On a positive note, I’d like to point out that Heidi has done these sorts of guides for years and always does an excellent job. Based on past experience, I would say it would be likely that she was simply passing on in good faith what she had been told, rather than being the origin of the incorrect information.

    Any BricsCAD users out there? v.2016

    Back in 2010 I asked the question Any BricsCAD users out there? and there were a few of you who had tried to replace AutoCAD with BricsCAD. Most who responded had made the change successfully, others not so much.

    Six years on, the situation is different. The fact that you can’t buy a permanent AutoCAD license any more has prompted some Autodesk customers to look more seriously at alternative vendors who do provide that option. Bricsys is one of those vendors, and their DWG-based AutoCAD alternative BricsCAD has improved way more rapidly than AutoCAD over the same time period. No, that isn’t a guess, I’ve been keeping an active eye on things. BricsCAD today is by no means perfect, but it’s impressive in many ways. LISP compatibility and performance are excellent, for example. BricsCAD v16 superior to the also imperfect AutoCAD 2017 in several areas, despite the total cost of ownership being significantly lower.

    Here’s the question I asked back then:

    I would be very interested to hear from any of you who have adopted BricsCAD (either partially or fully replacing AutoCAD or AutoCAD LT in your organisation), or at least seriously investigated using the product.
     
    Why did you investigate changing over? How far have you gone? What are your experiences? What are the pros and cons? How is performance? Reliability? Bugs? Ease of use? Familiarity? Support and other aspects of customer service? Total cost of ownership? Are you experiencing interoperability problems when exchanging drawings with Autodesk software users? How did you go with incorporating in-house customisation and third party tools?

    How would you answer that question today? Would you be interested in me providing more posts about BriscCAD, such as practical experiences with attempting a transition from AutoCAD?

    AutoCAD 2017 Service Pack 1 is out but you probably don’t want to install it

    As reported by Jimmy Bergmark, AutoCAD 2017 SP1 will break add-ins that use Autodesk’s built-in autoloader mechanism. It looks like it’s a problem caused by third party applications, but it’s not. It’s entirely Autodesk’s fault. The only fix at this stage is to uninstall SP1.

    It’s astonishing that Autodesk would release a service pack like this, introducing a nasty bug that will break customers’ existing functionality. This reminds me of the comedy of errors that was AutoCAD Release 13 with its multitude of updates, many of which introduced new bugs as well as fixing others. AutoCAD 2017c4a, anyone?

    If you needed any more evidence that automated continuous updates from Autodesk are A Bad Idea, here it is. What a crock.

    AutoCAD 2017 – Putting things back to “normal”

    The most frequently accessed posts on this blog are the AutoCAD 201x – Putting things back to “normal” series. They also attract a lot of comments:

    Most Commented Posts

    1. AutoCAD 2013 – An Autodesk Help writer responds – 164 comments
    2. AutoCAD 2012 – Putting things back to “normal” – 158 comments
    3. AutoCAD 2011 – Putting things back to “normal” – 135 comments
    4. AutoCAD 2009 – Putting things back to “normal” – 121 comments
    5. AutoCAD 2010 – Putting things back to “normal” – 106 comments

    The last one of these I did was for AutoCAD 2012, so I guess it’s well beyond time to bring things up to date for all those people who don’t like things being brought up to date. If there is something in particular I haven’t included in this post that you think people will find useful, please add a comment below and I’ll see what I can do.

    I’m not suggesting it’s a good idea to turn all of these things off, it’s just a resource for people who want to know how to turn some of them off. These items are in alphabetic order. If you can’t find what you’re after, try your browser’s find/search option to look for a word on this page rather than this site’s search option which will search the whole site. If you still can’t find it, please comment and let me know what I’ve missed.

    • Aerial View. If you’re a relatively recent user of AutoCAD, you may have never seen the Aerial View window, but you might still find it useful. The DSVIEWER command (which turns this window on) has been undefined. You can use REDEFINE DSVIEWER to turn it back on, or just enter .DSVIEWER (with a leading period). It may not work perfectly on all systems under all circumstances, but give it a try and see what you think.
    • Array Dialog Box. The associative array features added by AutoCAD 2012 did not come with an Array dialog box. After protests from the crowd, AutoCAD 2012 SP1 reintroduced the old dialog box. This has been retained ever since and is accessed using the command ARRAYCLASSIC. Why isn’t it called CLASSICARRAY? Because by the time Autodesk wanted to restore this feature, I had already published ClassicArray™ and owned the trademark. Did ARRAYCLASSIC make ClassicArray defunct? Not entirely. The old Autodesk dialog interface is much less capable than ClassicArray and only allows the creation of simple non-associative arrays. If you want a dialog box interface and the modern array features (including Path arrays), you will still need my ClassicArray (which has the fortunate side-effect of acting as a workaround for several of the Array command’s various bugs, limitations and design issues). If you just want to control whether ARRAY creates associative or non-associative arrays, use the ARRAYASSOCIATIVITY system variable (1 for associative, 0 for non-associative).
    • Autocomplete. You may well find the automated filling in of your typed commands useful, but I find it’s too slow and gets confused, resulting in the wrong command being used. If it’s getting in your way, turning it off is as simple as AUTOCOMPLETE OFF. There are a variety of settings you can selectively turn off individually if you prefer, see Command Line below.
    • Blips. The BLIPMODE command has been undefined, but you can use REDEFINE BLIPMODE to turn it back on, or just enter .BLIPMODE (with a leading period).
    • Button Backgrounds. If you have your own or third-party Ribbon, toolbar or menu items, you may notice that AutoCAD 2017 messed up their transparent backgrounds. Believe it or not, this was a deliberate act by Autodesk. I intend to write a more detailed post on this in future, but the short version is that the BMP background of 192,192,192 is no longer supported so you need to use another format (e.g. PNG files) if you want your buttons to support transparency.
    • Classic Commands. If you prefer not to leave the various new palettes on screen all the time, old versions of various commands are still available: ClassicGroup, ClassicLayer, ClassicXref and ClassicImage. (Autodesk deprecated these commands in 2011, which I think is a really bad idea, but at least they’re still there in 2017). There is also a system variable LAYERDLGMODE, which when set to 0 will make the Layer command work in the old (and faster) modal way. If you use this setting, you can still access the new modeless layer palette with the LayerPalette command. Going back further, there are command-line methods of using these commands: -Layer, -Plot, -Xref, XAttach, -Image and ImageAttach.
    • Color Scheme (interface). Goth AutoCAD doesn’t appeal to you? If you don’t want to draw with a product that looks like a 10-year-old version of PaintShop Pro, you can lighten things up a bit using Options (right-click on the drawing area and pick Options… or just enter OP), then pick the Display tab, set Color Scheme to Light. See Graphic Background below for more options.
    • Coordinates. Bafflingly, Autodesk decided that most CAD users are uninterested in where things are placed in a drawing, so coordinate display is turned off by default. You’ll obviously need to turn them on to do any meaningful work (well, duh), so pick the 3-line Customization button at the lower right and turn on the Coordinates item at the top of that menu. Pick and choose among the various other options to get the buttons you want.
    • Command Line. There are many enhancements to the command line that theoretically make your keyboard-based interactions with AutoCAD more productive. I find that all of these features are great if I’m not in a hurry. If I just want to enter a short command and hit Enter, I find the command I get is wrong most of the time. To control which of these command line features you want on, use the INPUTSEARCHOPTIONS command.
    • Content Explorer. The Content Explorer was pretty horrible in many ways and Autodesk killed it. It’s gone and is unlikely to return, so you can stop looking for it. DesignCenter is still there and still does most of Content Explorer’s job, only better. Unfortunately, this means those people who did use Content Explorer’s unique functionality (e.g. searching for text among multiple drawings) are now out of luck until Autodesk does something about that.
    • Crosshairs. Want 100% crosshairs? Many people do. As before, use the Options command’s Display tab and look towards the bottom right, or set the CURSORSIZE system variable to 100.
    • Cursor Badges. About a dozen commands in AutoCAD now display a little glyph on the cursor to give you a visual clue about what you’re doing. If you find these pointless or annoying, turn them off by setting CURSORBADGE to 1. No, I have no idea why you use 1 to turn them off and 2 to turn them on, rather than 0 and 1 like pretty much everything else.
    • Customer Involvement Program. Those in the know always turn off whatever Autodesk phone-home activity they can find, not just because we’re a bunch of tin-hat-wearing paranoiacs, but because uses your resources and harms your performance. I’ve observed this happening, despite having been assured by Autodesk people that such a thing couldn’t possibly be occurring. The CUSTOMERINVOLVEMENTPROGRAM command has given access to one such setting for a few releases, but now there’s DESKTOPANALYTICS too. It’s not doing you any good, so kill it.
    • Dynamic Input. If Dynamic Input slows you down, you can turn it off with the status bar toggle or F12. If you like the general idea but don’t like some parts of it, there are lots of options available in the Dynamic Input tab of the DSettings command to enable you to control it to a fine degree. You can also get at this by right-clicking the Dynamic Input status bar button and picking Settings… As an example of the sort of thing you might do in there, the default of using relative coordinates is difficult for long-termers to get used to. To turn it off, pick the Settings… button in the Pointer Input panel, pick Absolute coordinates, then OK twice. There are a whole range of DYNxxx system variables for controlling this stuff.
    • File Tabs. Want vertical screen space more than you want to see what drawings you have open? Turn off File Tabs with the FILETABCLOSE command. You can still switch between drawings with Ctrl+Tab.
    • Graphic Background. After various experiments with black, white, black, cream, etc., for the last few releases Autodesk has stuck a nearly black background in model space only. Many of you will want a real black background to provide better contrast. To do this, invoke the Options command and pick the Display tab. Don’t be tempted to choose Color Scheme because that just changes the appearance of various user interface elements. Instead, pick the Colors… button. This will put you in the Drawing Window Colors dialog box. On the left, choose a context you want to change (e.g. 2D model space), choose the appropriate background element (e.g. Uniform background) and choose the particular shade that takes your fancy. There is a Restore Classic Colors button, but that only takes you back to AutoCAD 2008 with its black model and white paper space. If you want a black paper space background too, you’ll have to pick the Sheet / layout context and specify that individually. You may wish to put the Command line > Command line history background setting to white, too. When you’re done, pick Apply & Close, then OK.
    • Grid. If you use isometric snap and grid, you will be glad to find that AutoCAD 2017’s line-based isometric grid works properly, unlike some earlier releases. If you still prefer dots, right-click on the Grid status button and pick Grid Settings…, which will take you into the Drafting Settings dialog box, which you can also get at with the DSettings command, or DS for short. In the Snap and Grid tab, the grid is controlled by the options on the right. If you want your dots back, turn on the toggles in the Grid style section. This can also be done using the GRIDSTYLE system variable. This is now stored in the registry rather than on a drawing-by-drawing basis.
    • Hatch Dialog Box. If you want the Ribbon on but prefer the old Hatch dialog box, set HPDLGMODE to 1.
    • Hatch Double Click. If you’re not using the new Ribbon-based hatch editing feature, you will probably want to invoke the HatchEdit command when you double-click on a hatch object. Doing this involves braving the CUI interface, but I have gone into step-by-step detail of that process here. In short, you need to drag and drop the Hatch Edit command from the bottom left CUI panel onto the double-click action for Hatch in the top left panel, replacing the default action (Properties).
    • Help. If you want your Help to work with adequate speed and reliability, or to work at all in some proxy server environments, you will want to turn off AutoCAD’s online help. The installer for the AutoCAD 2017 English offline Help can be found here. For other languages, see here. However, downloading and installing it isn’t enough. Go into Options > System, then look in the bottom right pane to turn off the Use online help toggle. The Help structure remains destroyed and the interface is still a long way short of the excellent CHM-based Help we had prior to AutoCAD 2011, but at least it’s not as slow and externally dependant as the online Help system. Note that the search mechanism in the offline version is notably weaker than in the online version.
    • InfoCenter. This is the set of tools on the right top of the AutoCAD window. It takes up space, reduces AutoCAD reliability and performance and forces the use of Internet Explorer to support Autodesk LiveUpdate technology. You probably want it gone. Here’s how:
      (vl-registry-write
      (strcat "HKEY_CURRENT_USER\\" (vlax-user-product-key) "\\InfoCenter")
      "InfoCenterOn" 0)

      Paste the above lines into AutoCAD’s command line area and hit Enter. Close and start AutoCAD and InfoCenter will be gone. If you ever want it back, use the above code with a 1 in place of the 0, then close and restart AutoCAD.
    • Layout Tabs. You don’t get to choose where the layout tabs go, but you can turn them on and off using the LAYOUTTAB system variable.
    • Navigation Bar. If you like the NavBar feature as much as I do, you’ll want to turn it off. You can close it easily using the little X in its top left corner. Alternatively, control it with the NAVBARDISPLAY system variable (0 for off, 1 for on) or click the [-] button in the top left corner of the drawing area and turn off the Navigation Bar toggle there.
    • Pull-down Menus. Enter MENUBAR 1 to turn pull-down menus on. To turn them off again, enter MENUBAR 0.
    • Ribbon. You can close the Ribbon with the RibbonClose command. If you ever want to turn it back on, enter Ribbon.
    • Ribbon Galleries. AutoCAD 2015 introduced Ribbon Galleries: drop-down preview images of blocks, styles, etc. This cool-sounding feature might annoy you with its (lack of) performance, and as happens way too often, Autodesk forgot to include an off switch. AutoCAD 2016 introduced the GALLERYVIEW system variable; set this to 0 to get back up to speed. (Thanks, RK).
    • Screen menu. The SCREENMENU command has been undefined, but you can use REDEFINE SCREENMENU to turn it back on, or just enter .SCREENMENU (with a leading period). However, you can’t access the screen menu section in CUI any more, so if you want to maintain your screen menu you will need to do it in an ancient release or with a text editor operating on a .MNU file.
    • Security. There are various obstacles to productive use that can be placed in the way by the various security settings that have been progressively introduced since AutoCAD 2014. However, I’m not going to provide advice on removing those obstacles because of the risk such action can entail; I don’t want to be a party to making your system more vunerable. If you wish to look into this area, look up the SECURITYOPTIONS command and the SECURELOAD system variable. One security setting I’d suggest you definitely leave at the default value of 0 is LEGACYCODESEARCH, because that setting will protect you from the most common AutoCAD-specific malware without any practical downside. Feel free to look it up and take your own informed action, but you almost certainly don’t need to set this variable to 1.
    • Selecting Dashed Lines. AutoCAD now allows you to select objects with linetypes by picking the gaps. If you don’t want this, set LTGAPSELECTION to 0. Although 0 is supposed to be the default, I’ve seen AutoCAD working as if it were set to 1 even when it says it is 0. If so, set it to 1 and back to 0.
    • Selecting One Object at a Time. Does AutoCAD insist on only allowing you to select one object at a time? You probably have PICKADD set to 0. Set it back to the default of 2 or look for the Use Shift to add to selection toggle in the left pane of the Selection tab of OPTIONS. AutoCAD has been known to mangle this setting by itself. Yes, even when there is no possibility of a LISP routine messing with it.
    • Selection Cycling. Depending on your preference and/or system graphic performance, you may wish to turn off selection cycling (set SELECTIONCYCLING to 0), or at least the list that appears when selecting objects that lie on top of each other (set SELECTIONCYCLING to 1).
    • Selection Effect. If you want AutoCAD to show selected objects with old-style dashed lines rather than a glowing halo, set SELECTIONEFFECT to 0.
    • Selection Lasso. You can now select objects within irregular areas using the Lasso tool by clicking, holding and dragging. If this gets in your way, turn off the 4 bit of PICKAUTO (e.g. change PICKAUTO from 5 to 1). You may prefer to use the toggle for this in the left pane of the Selection tab of OPTIONS.
    • Selection Preview. This feature annoys some users, adding as it does an unfortunate degree of stickiness and working inaccurately when Snap is in use. This is controlled in the Selection tab of the Options command. Turn off the toggles in the Selection preview panel on the left (these control the SELECTIONPREVIEW system variable). If you dislike the coloured boxes you get while doing a Window or Crossing, pick the Visual Effect Settings… button and turn off the Indicate selection area toggle. This controls the SELECTIONAREA system variable.
    • Snap. By default, AutoCAD’s snap no longer works while there is no command active. Set SNAPGRIDLEGACY to 1 to turn this feature off.
    • Start Tab/New Tab/Welcome Screen. If you want AutoCAD to start in a blank drawing rather than using the Start Tab (New Tab or Welcome Screen in earlier releases), set the STARTUP system variable to 0. Note that if you turn off the Start Tab feature during installation or deployment creation, it’s not possible to later turn it back on using AutoCAD commands. If you’re unsure about whether or not you want to use the Start Tab, defer that decision until after installation.
    • Startup performance. You may have noticed that AutoCAD’s Ribbon switching performance is much faster than earlier releases. You may also have noticed that when you start AutoCAD, the cursor is sticky for a while after the Command prompt is available. These two items are not unrelated; AutoCAD is loading Ribbon components in the background. If you would prefer this not to happen, set the RIBBONBGLOAD system variable to 0.
    • Steering Wheel. Do you have a funny silver thing following your cursor around? Despise it? If it will stay still long enough you can hit the little X in the top right. Alternatively, use the NAVSWHEEL command to toggle it or click the [-] button in the top left corner of the drawing area and turn off the Steering Wheel toggle there.
    • Status Bar Text. You can’t have text-based status line toggles any more, so you can call off the search. Yes, I know. This is the poster child for Autodesk deliberately ignoring the clearly expressed wishes of its customers.
    • Toolbars. In AutoCAD 2009, you could turn individual toolbars on and off by accessing a menu obtained by right-clicking on the QAT. Autodesk somewhat vindictively removed that option in 2010, and it’s still gone in 2017, so I guess we can conclude that Autodesk really doesn’t want you using toolbars. A toolbar-toggling menu is still available if you right-click in an unused docked toolbar area, but if you have no toolbars visible there will be no such area available. What to do? Turn on one docked toolbar at the Command prompt, then you will be able to access the menu by right-clicking on the blank area to the right of it. The following command sequence will do it:
      _.-TOOLBAR ACAD.Standard _Top 0,0
      Paste this into AutoCAD’s command line area and the Standard toolbar will be turned on above your drawing area. This will leave a grey area to the right that you can right-click into. The other toolbars will be in sub-menus under that, with the main set of default ones in the AutoCAD section. Note that this will only work if you have the acad.cuix file loaded (or partially loaded). This is the case in vanilla AutoCAD and some verticals, but it may not be the case in other verticals.
    • Tooltips. Excessively intrusive and oversized tooltips were a “feature” of AutoCAD 2009’s revamped UI design, and we’ve been plagued with them ever since. I’m glad to see that many of them have had their verbosity somewhat curtailed (thanks to Dieter), but they still annoy the heck out of me, particularly by obscuring what I’m trying to see in dialog boxes. To kill them with fire, see Options > Display and start turning off toggles about half way down the left side.
    • Trace. The TRACE command has been undefined, but you can use REDEFINE TRACE to turn it back on, or just enter .TRACE (with a leading period).
    • UCS Icon. Don’t like the new simplified UCS icon? Sorry! While you can use the UCSIcon command’s Properties option to change the appearance of the icon in various ways, there’s nothing to restore the UCS Icon’s appearance from previous releases with its little arrows pointing the way.
    • ViewCube. I like the ViewCube concept, and I think it’s a great piece of interface design. But not everybody agrees. It has caused performance issues and it’s not very useful for 2D users. If you want it gone, that’s a surprisingly difficult thing to find out about. The simplest way to remove it is by clicking the [-] button in the top left corner of the drawing area and turning off the ViewCube toggle there. If you want more control, it’s handled using the Options command, in the 3D Modeling tab, in the bottom left corner. Turn off those toggles that don’t make sense for you. There is a related set of system variables called NAVVCUBExxx.
    • Workspace. The Workspace (gearwheel) control is now located near the bottom right corner. The item called AutoCAD Classic is long gone, unfortunately, so you’ll need to make your own classic workspace by manually setting up your interface the way you like it, then saving it as a Workspace using the Save Current As… option under the Workspace control. See this step-by-step description by Luciana Klein, (for AutoCAD 2016) along with clues from the various items above, for information on how to do this. Easier still, there is a script file to do this in this post by Edwin Prakaso. There’s a bug in the Workspace control that means it no longer reverts to a saved workspace directly. If you want to revert to the correct version of a workspace, you need to switch to a different workspace first and then back again.
    • Xref Fading. Don’t like your xrefs looking different? Use the Options command’s Display tab and look at the Xref display slider on the bottom right, or use the XDWGFADECTL system variable.
    • Zoom Animation. If you prefer your zooms to be instant rather than progressing from one view to another in an animated series of steps, you can turn off that feature using the VTOPTIONS command or the VTENABLE system variable.

    If you have allowed AutoCAD to migrate your settings, some of the above will already be done for you, but by no means all of it. If past experience is anything to go by, the job done by Migration will be sub-optimal, but it received a major overhaul for 2017 so maybe it’s all good now. Call me paranoid/lazy/whatever, but I didn’t bother finding out. I’ve done without it for over a decade and will continue to do so; file under Problems left unfixed for so long that nobody cares when the fix finally comes.

    Once you’re happy with your new environment, I suggest you save your workspace under a name of your choosing (Save Current As… under the Workspace gearwheel control), then export your profile in the Options command’s Profiles tab. Keep a safe copy of both your exported profile and your main CUIX file (acad.cuix by default), because that is where new workspaces are stored.

    All of this advice is offered on an as-is, try-it-yourself-and see-what-happens basis. If in doubt, before you start messing make a safe profile, export it, then make an experimental profile and make it current. Back up any files you may have modified (e.g. acad.cuix).

    I’ve probably missed a few things, so feel free to point them out or ask questions. I’ll edit this post to add relevant information.

    Shout out to Robert McNeel & Associates

    Let’s start the rebirth of this blog on a positive note. I’d like to express my gratitude to Robert McNeel & Associates for what must surely be the most outstanding example of long-term customer service in the CAD industry.

    These days, McNeel is best known for the 3D modelling software Rhino. I have heard good things about this product, but have never used it. However, I am a long-term user of another McNeel product, DOSLib. This is an extensive set of functions that adds greatly to the functionality of AutoLISP. It all works very well and has saved me many hours of work that I would have spent reproducing that functionality. Of course, many LISP programmers could write functions to calculate a cube root, or read a text file, or display a date in whatever format you like, or copy files, or generate a GUID, or toggle the Caps Lock status, or display an HTML file, or return a list of OLE objects in the drawing, or display a multi-select file dialog, or return a list of Windows printers, or a hundred other handy things. The point is, they don’t have to because all that has been done for them and handed over for nothing.

    The documentation is straightforward and accurate, and is provided in the form of a good old-fashioned local CHM file. This Help system may be unfashionable, but it remains infinitely superior to the still-awful system that paying AutoCAD customers have had to put up with for the last few years.

    For those investigating alternatives to AutoCAD for whatever reason, the availability of DOSLib for Bricscad may help make that particular alternative a more attractive proposition.

    Despite McNeel and Autodesk breaking ties many years ago, McNeel’s Dale Fugier has continued to provide, maintain and improve DOSLib. What’s more, DOSLib has remained totally free of charge and ad-free throughout its history, which dates back to 1992! Sometimes, there really is such a thing as a free lunch.

    So here’s a big raised glass to Dale and Robert McNeel. Thank you for the many years of outstanding customer service in exchange for nothing but good feelings. Long may you prosper!

    Disclaimer: I have no pecuniary relationship with McNeel; no money has ever changed hands in either direction. This post is totally unsolicited; I hope it comes as a pleasant surprise to McNeel.