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.
If you’re a small CAD vendor, please consider helping out CAD journalism legend Randall Newton with his homework.
Randall is doing a university survey project on the marketing communications issues in Small CAD vendors. He has a survey with 5 questions about marketing communications; if you think you can help, please email randall dot newton at gmail dot com and he’ll send you the survey and explain its uses. He needs the responses by 20 January.
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).
It always amuses me when people proclaim a rising technology as not just promising, but the way of the future that will inevitably take over. Anybody can see that’s the way things are heading, they say. No use fighting it. Don’t question the certainty of the forthcoming tech revolution, you Luddite! It’s a sea change, resistance is futile, get on board now or be swept away on the flood waters of progress.
What a load of bollocks.
What really surprises me is when people who are old enough to know better join in with this sort of thing. Those of us who have been around a while have seen many “inevitable” technological revolutions dry up and fizzle out, some more than once. It gets old.
Remember a few short years ago when touchscreens were going to be part of everybody’s desktop setup as ubiquitous as the mouse? I do, but I also remembered touchscreens on desktop computers failing in the 80s for the exact same ergonomic reasons they went nowhere this time around (thanks for the lesson, HP). That’s why none of the monitors I bought in the last few years have had touchscreens, and I’ve yet to see a single desktop touchscreen in active use.
Next off the rank is VR. Some of the people who were around when virtual reality failed the first time are somehow now convinced it’s now The Next Big Thing, despite the reasons it failed originally remaining stubbornly in place. No, in three years’ time you’re not going to be holding site meetings in your office wearing a silly pair of goggles and bumping into the coffee machine. Really, you’re not. It didn’t happen in 1990 and it won’t happen in 2020 either.
Here are a couple of things I enjoyed reading recently.
To celebrate, I went out and bought a gramophone, I mean, turntable. I’m happy to report that I still haven’t parted with a single cent for online music. That’s so yesterday.
Next time somebody tries to tell you something like, “The whole software industry is moving to the rental model, all software will be sold that way soon, there will be no avoiding it,” please refer them to paragraph two above.
Thanks to Hans Lammerts on Twitter for pointing out this amusingly cringeworthy AutoCAD 360 YouTube ad:
The guy spilling his coffee and falling over reminds me of the people in those infomercials that can never get the simplest things right:
https://youtu.be/3eMCURWpNAg
OK, so the ad’s bad, but how’s the product? I had a look for myself at the browser version of AutoCAD 360, which is the current name for what has been Visual Tau, Project Butterfly and AutoCAD WS in previous iterations dating back before Autodesk’s acquisition of the Israeli technology in 2009.
It’s a while since I tried it, so I was interested to see the progress that had been made. After all, CAD in the Cloud has been Autodesk’s focus for a long time now, and as this is likely the first product people try out, you’d expect it to be pretty dazzlingly good after all those years of development, right?
Interestingly, it’s still called a Beta, which hardly inspires confidence. Nevertheless, it didn’t misbehave for me, at least to begin with. It didn’t do very much at all for me, though.
On opening a very simple small 2D drawing, the first thing I noticed was the white background. As the drawing contained yellow text, that was no good so I looked for the settings to change the background to black. Couldn’t find any settings. I guess I didn’t really want to read that text anyway.
Nevertheless, I could zoom and pan around OK with tolerable performance. When I tried to select some objects to edit them, nothing happened. I looked around for buttons to press to do things. There was very little to see, and nothing I could find for doing anything much other than redlining over the top of what’s already there.
The second time I tried to open the same drawing, it just hung there, displaying a blue propeller thingy:
I gave up and tried again. This time, things were different! It locked slightly differently:
Now I see why it’s still called Beta.
To be fair, it hasn’t locked like this for me in the past so maybe it’s a one-off. Assuming it’s working, it’s a useful enough viewer. It has some limited markup functionality. That’s it. It’s free, and you get what you pay for.
Calling it AutoCAD 360 is highly dubious. It’s not AutoCAD or anything remotely close to it. It’s not even CAD. It’s a simple online product with capabilities that fall well short of the weakest CAD application back in the bad old days, when people could only dream of something as advanced as the dumb guy’s Nokia in the embarrassing Autodesk 360 ad.
There are also mobile versions of the software for iOS and Android. Haven’t tried them recently, but when I did they were acceptable viewers. Apparently you can pay for versions that actually let you do things. Go for it if you feel confident in Autodesk’s ability to provide a quality product. Me, I’m out.
One of the multiple reasons Autodesk has failed to win over the masses to its Cloudy CAD vision is fear of unreliability. Anything that relies on using somebody else’s computer over the Internet adds potential points of failure to those already there on a standalone desktop system. These additional vulnerabilities include:
Your browser or thin client software fails
Your modem, cabling or other Internet connectivity hardware fails
Your Internet service provider has an outage
Malware or DDOS attacks on your domain or service
Governmental Internet service interference
Internet connectivity infrastructure failure
Malware or DDOS attacks on vendor domain or service
Cloud vendor infrastructure disaster
Cloud-based CAD software down for maintenance
I voiced my concerns about this in 2011, but technology has moved on since then and surely things are running as smooth as can be these days, right? Most computer users use Cloud services for backing up, sharing files, etc. and that seems pretty reliable, surely? How’s it going for Autodesk? Let’s ignore potential failures at your end and in the middle and confine ourselves to service reliability at the vendor end.
Autodesk kindly provides a health check site with a History option that allows you to look back in time in fortnightly steps to see how things have been going. At the time of writing, there are 25 full 14-day pages you can examine. Want to take a guess at how many of those pages show no problems?
Two.
That’s right, 92% of the last 25 fortnights have had at least one time where at least one Autodesk CAD Cloud service has been down or degraded. The most recent clean fortnight was in June last year. Most of the pages show multiple failures, such as this:
Some of those failures have exceeded an entire working day. How do you fancy that when you have a tight deadline to meet?
Let’s see how this compares with the service availability record of my old-fashioned standalone desktop CAD products over the same time period:
Edwin Prakaso at the excellent CAD Notes blog has done something that, in hindsight, is blindingly obvious but nevertheless very useful to a multitude of people. He’s written a simple script file that sets up the Classic workspace (or something close to it). It works in any recent AutoCAD or AutoCAD LT. Here’s the blog post:
Autodesk has yet again demonstrated why continuous automatic updating is no panacea for avoiding CAD update disruption. On the contrary…
If you have noticed some of your PDFs exported from AutoCAD getting huge and unwieldy lately, AutoCAD 2017.1.1 could be to blame. Try uninstalling it using Programs and Features > View Installed Updates and see if the problem goes away. It may also be possible to work around this by going into PDF options and turning on Include Hyperlinks. Source: The Swamp.
Here’s one possible* install history:
You install AutoCAD 2017. This defaults to also installing Autodesk desktop app. If this works on your system and you leave it on there doing its thing and consuming your resources, it will attempt to automatically keep your Autodesk software up to date.
Autodesk desktop app installed AutoCAD 2017.1. You like this because it has added a couple of nice features. In apparently unrelated news, you seem to be getting more fatal errors and several of your add-ins have stopped working. You decide to do without them.
Autodesk desktop app installed AutoCAD 2017.1.1. Your add-ins have magically started working again and there seem to be fewer fatal errors.
You get some huge PDFs from AutoCAD but read this post and uninstall AutoCAD 2017.1.1. The PDFs you create are no longer huge, but your add-ins have stopped working again and there seem to be more fatal errors.
You read this other post and manually install the AutoCAD 2017.1 Hotfix. Your add-ins start working again. The fatal errors remain.
Autodesk desktop app continually and perpetually nags you to install AutoCAD 2017.1.1.**
You uninstall Autodesk desktop app. Your system speeds up and the nags go away.
Moral of the story? Autodesk isn’t competent enough to trust with automatic updates. Uninstall Autodesk desktop app. Relax.
* YMMV
** I don’t know if this actually happens (Autodesk desktop app is not going to be installed on any of my systems to find out) but it wouldn’t surprise me.
I had my Samsung Galaxy Tab S 8.4″ Android tablet spontaneously die last night, and it refused to respond to any button pressing, cable connecting or threats. Holding down the power button for 10 seconds (or more) did nothing, as did Dr. Google’s top tip of holding down Power, Volume Up and Home for 10 seconds.
What worked for me was holding down Power, Volume Up and Volume Down for 10 seconds. It restarted without anything being lost and is now back to normal.
In an October 2015 post I’ve only just noticed, snappily titled No More Software Like a Can of Baked Beans: Why Software Subscription Serves It Up Fresh, Autodesk VP (edit – now CEO) Andrew Anagnost bravely attempts to sell Autodesk’s move to all-rental software. This is a rather belated response, but fortunately there is no statute of limitations on skewering spin so let’s get started.
How does he go? On a positive note, top marks for creative writing! The general theme is a strained and somewhat Californian analogy in which perpetual licenses are like canned goods (bad), and rental is like fresh produce (good). However, it’s presented well and professionally written. Among the highlights are:
Perpetual software licenses are like high-fructose corn syrup – no, I’m not making this up. Stop laughing at the back there!
This is a change that is simply a better experience for everyone – everyone who likes the experience of paying more for less, that is.
It’s to create a better product, something tailored to customers – creating a better product seems beyond Autodesk, at least where AutoCAD is concerned. Actually, it’s to create a more expensive product. Tailoring is something we customers been doing for over 30 years without the use of rental software, thanks.
There will be less disruption – except a) how we pay for the product is independent of how/when the product is updated and the disruptions inherent in that, and b) even ignoring the erroneous conflation, it’s a mistake to assume that continuous updates are less disruptive. Recenthistoryproves otherwise.
Companies (e.g. Autodesk) will work even harder to keep you happy as a rental customer – history gives the lie to this one, too; the closer Autodesk has got to this model and the more people have been locked into annual subscription/maintenance payments, the worse the value for money has become. It also ignores the various alternative ways Autodesk will use to try to keep you tied in. What do you think all that Cloud investment has been for?
Autodesk is focusing on helping customers succeed with its products and services – I don’t think so. Autodesk is focusing on trying to keep its shareholders happy.
Serial numbers are a terrible dehumanizing thing, rental will make them go away and relying on Autodesk’s internet expertise for Cloud-based licensing is a much more attractive proposition – serial numbers are fine, that’s just silly. There are a host of unnecessary problems introduced by Cloud-based licensing, even when dealing with companies that aren’t as crap at the Internet as Autodesk (e.g. the Redshift site won’t even let me scroll back up once I’ve scrolled past the end of the post). The idea of Autodesk disposing of serial numbers and implementing a phone-home scheme instead is pretty terrifying, and I can only hope that technical issues prevent it from ever reaching production. Mind you, the fact that some new thing is clearly unfinished to the point of uselessness doesn’t seem to prevent Autodesk releasing it these days, so who knows? Hmm, I feel another post coming on about this…
Autodesk will make all your customization work for you on all computers and other devices wherever you go – let’s put aside for a moment Autodesk’s total failure to even provide a usable vanilla AutoCAD on the Cloud so far. CAD Managers, would any of you care to hop in and let Andrew know what’s wrong with this picture?
Constant automatic incremental updates are like reading news articles daily and much more convenient than larger upgrades which are like getting a whole year’s worth of news at once – again, this makes the fatal error of conflating payment and upgrade delivery methods. Putting that aside, if we’re talking about virus definitions and OS or browser security hole fixes, then yes, automatic updates are the way to go. CAD software, not so much. Particularly software from Autodesk, given the incompetence shown to date in its attempts to make this model work. Even putting aside the practicalities, I could do a whole long post on why this concept is all wrong. Maybe I will later. Meantime, Andrew needs to talk to some CAD Managers to get some idea of how the real world works.
“OK, so there’s still the major elephant in the room: What about the cost?” – good of you to mention that elephant, tell me more.
For customers, there is real financial advantage by eliminating that huge upfront payment. – For some customers, yes. Not so many, though. Short-term customers are the minority. What about the millions of long-term users who would have their annual costs blown sky-high by falling into your rental trap? Andrew, I see you mentioned the elephant in the room and then tried to avoid meaningful discussion of it, giving the impression you had addressed the issue without actually doing so. Sorry, but I noticed. Care to try again? Tell me more about how you expect either a) customers to be better off by paying more, or b) Autodesk to be better off despite customers paying less. Pick either one of those and run with it, I’m sure it will be entertaining.
“And if you don’t need a product for months at a time, switch it off, and then switch it back on. It will be there ready and waiting for you” – strange, that kind of flexibility seems to work for perpetual licenses too, at a fraction of the long-term cost of rental. No guarantee that flexibility is a reality for rental products, though, because the vendor may not provide that product when I need it, or may have racked up the prices to exorbitant levels, or may have introduced new incompatibilities or other technical problems. Oh dear, the boot is very much on the other foot with that argument.
“After three years, software becomes obsolete…” – er, no. Many people (myself included) are happily productive using at least some software more than three years old. Some of it works better than the newer stuff. Hands up all those people who couldn’t possibly live without the latest version of Word or Excel, for example. Anyone? Didn’t think so.
“…and the pace of obsolescence is rapidly increasing” – if we’re talking Autodesk software, then the pace of obsolescence is doing the opposite. AutoCAD improvement has slowed almost to a halt, for example. There is little in any of the last few releases that gives an AutoCAD 2017 user a significant productivity advantage over an AutoCAD 2013 user, say. And anyone using AutoCAD 2010 or earlier has a much more efficient Help system than that provided in any of the last 7 releases. I guess that’s the kind of anti-progress that happens when you sack a bunch of knowledgeable people every few years and divert too many of the remaining resources to trendier projects that you end up junking anyway.
Customers of Autodesk can continue to renew their maintenance contracts for as long as they want – except that Carl Bass has now indicated otherwise. Andrew, maybe have a word with your boss and get back to me on that one?
“The company is always listening to how to improve the transition and setting out for the long road, not the short win” – except rental is all about the opposite: short term savings that cost big in the long term. And don’t get me started on the irony of claiming Autodesk is “always listening” while promoting an all-rental scheme that goes against the very clearly expressed wishes of customers.
“It’s this beautiful kind of world where things are connected and work together better” – does it have rainbows and unicorns, too? Strewth. Come off it, Autodesk is rubbish at CAD interoperability, even among the AutoCAD-based products. Why should anyone who’s been struggling with poxy proxy objects for a couple of decades believe that paying differently is going to act as some kind of magic spell to make everything exquisite in CAD Connectivity Kingdom?
Here’s the TL;DR version of my response to Andrew’s arguments if you can’t be bothered reading all that:
Bullshit.
What are the real reasons Autodesk is going all-rental?
Autodesk wants to charge us long-term users three times as much money for the same thing and leave us with nothing at the end of it.
Autodesk thinks we’re all stupid and don’t own calculators.
Adobe did this and made it work, and Autodesk thinks it can do likewise despite significant business differences, much higher prices and an untrusting customer base.
Autodesk has run out of motivation and/or ideas to improve its traditional cash-cow flagship products, to the extent that customers increasingly no longer see value in upgrades or maintenance.
Increasing income by product improvement is way too difficult; price gouging and spin is much cheaper.
I’ll conclude with my own strained analogy:
Autodesk spin is like a tin of baked beans. No matter how attractive the packaging, the end result is just a bad smell.
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.
Back in 2011, Autodesk, some other vendors and many industry pundits were utterly convinced of the inevitable and near-imminent victory of Cloud-based CAD over standalone software. I wasn’t. I wanted to get a feel for how isolated my viewpoint was, so I started a poll and let it run for a while. Here’s how that turned out:
As you can see, this blog’s readers were less than convinced about the inevitability of that Cloudy future. Not so Carl Bass, who had this to say in an April 2012 TechCrunch interview:
I’d say two to three years from now, every one of our products will be used online. The only way to use them will be online.
So let’s say you’re an AutoCAD user. A successful Cloud push by Autodesk will mean that you and very large numbers of people just like you be using AutoCAD or an equivalent Autodesk product on the Cloud by 2014 or 2015. If that doesn’t happen for you and all the other users of Autodesk products, then that’s failure by definition. Autodesk will have failed to meet its own publicly stated goal, and that’s exactly what I’m expecting to happen …. I am convinced there is a dichotomy between the expectations of Autodesk and those of its customers, and that spells trouble. Autodesk is either going to succeed in pushing its customers into a future they are not expecting, or it is going to fail and be forced to revise its expectations. I predict that the latter will happen…
It’s now way past Carl’s predicted online-only timeframe. A successful strategy by Autodesk would mean we Autodesk customers would have all have been exclusively CloudyCADing for a couple of years by now. Is that what happened?
Knock me down with a feather, it turns out that Autodesk’s big Cloud-only push has worked out just as predicted, not by Carl but by the readers of this blog. Take a bow, Nostradamuses!
Yes, there are now Cloud-saving options in a lot of Autodesk’s software, as there are in most competitive products. Yes, Autodesk is still attempting (often astonishingly badly) to online-tie-in desktop CAD users. Yes, Autodesk has a lot of Cloud-only software products, even if many of them don’t generate revenue and some of them are headed for the chopping block. Yes, some of Autodesk’s online offerings now have utility. Yes, there are many students and hobbyists out there, often isolated from commercial and production realities, having fun tinkering with Autodesk’s largely free online software and in some cases producing some seriously cool stuff that looks great in Autodesk publicity material.
Real paying customers, using Autodesk Cloud-based products as their primary mission-critical CAD software in a production environment? Not so much. People are still using that terribly old-fashioned desktop software for that. Autodesk has failed to make reality conform with Carl’s prediction.
Why should I care? I care because Autodesk has taken vast sums of money from AutoCAD customers, and is trying hard to extract even larger sums via its compulsory rental scheme. Instead of spending that cash on genuinely useful improvements to the product that is the source of that income and the basis for many of its vertical products generating further income, Autodesk has left AutoCAD to wither on the vine. It has been some years since an AutoCAD upgrade was anywhere near good enough to be worth the amount Autodesk currently charges for maintenance, let alone the trebled(?) amount it likes to think it can get away with charging in a couple of years.
It’s not because there’s no potential for improvement, either. Autodesk gets a lot of feedback about what could be improved in AutoCAD, but ignores most of it, sometimes choosing to do dumbthings instead that make things worse. In contrast, Bricsys has proven that it’s possible to make huge strides in improving a straightforward 2D/3D DWG-based desktop CAD application in a single year; Autodesk’s efforts are woefully inadequate in comparison. Meanwhile, by chasing an elusive exclusive Cloudy cornucopia, Autodesk has frittered away a fair fortune on a plethora of production-pointless products.
The update was apparently released over a month ago on 17 November 2016. Autodesk needs to work out an alternative mechanism to Autodesk desktop app so that those of us who won’t/can’t use it will still be informed when updates become available. If only there were some other method Autodesk could use to communicate with customers! Too hard, apparently.
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.
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
The reason you should never rely on SaaS for anything important is that, well, you just can’t rely on it. If the software breaks, or the vendor goes under, or decides that line’s not profitable enough, or just loses interest, you’re screwed. More importantly, you’re screwed on a timeframe that’s out of your control, and probably much shorter than you would like. You can’t just go on using the software until you’re ready to move on, like you can with perpetual licenses.
Thanks for the latest lesson, Autodesk, regarding 123D:
Over the past few years, millions of people have unlocked their creativity with the Autodesk 123D apps and community. We’ve grown from one desktop tool in 2011 to multiple apps across desktop, web, and mobile.
We’re incredibly proud of these products, and even more proud of what you all have MADE with them. But we recognize that the portfolio has become complex. We are making some changes to simplify our Autodesk portfolio and workflows for people everywhere who love to make things. We are consolidating these tools and features into key apps such as Tinkercad, Fusion 360, and ReMake.
Today, we are sharing the news that in early 2017, after we complete this consolidation, we’ll be shutting down 123dApp and turning off many of the apps to new download. Rest assured that we remain committed to providing free tools to hobbyists, kids, hackers, and makers around the world. We value you, your models, and are going to do this consolidation in the right way.
You’ll be able to access and download your content from 123dApp in the coming months. We will make every effort to make sure you will be notified before we make any changes to the apps or website.
What’s next? We’ll be working closely with you, the 123D Community of users, to make sure your questions are answered. We’ll be sharing more details on this blog and our support forums, and will notify you when we start to implement changes.
Autodesk is committed to help people make anything and we are committed to help you continue to do just that. Look for more detailed information in the next few days, weeks and months.
–The Autodesk 123D Team
Whether Autodesk’s definition of “the right way” coincides with that of users remains to be seen. Of course, Autodesk 123D is free and you get what you (don’t) pay for. But if you think Autodesk won’t do this with its paid SaaS products, you’re dreaming. The same applies to any vendor, but Autodesk in particular has a horrible history of killing products and leaving masses of crying orphans to fend for themselves.
Some of you may be aware I’m an activeveteran fencer. I’ve been a bit quiet over the past month because I’ve been away, attending two major fencing tournaments. I’ll post some video later, but here are my national and international medal results this year:
Open Men’s Sabre Teams (Western Australia) – Silver
Veteran Men’s Sabre – 50+ Gold
Veteran Men’s Foil – Silver and 50+ Gold
Veteran Sabre Teams (Western Australia – Captain) – Gold
Veteran Epee Teams (Western Australia – Captain) – Gold
Veteran Foil Teams (Western Australia – Captain) – Bronze
** At these Championships I fenced in 11 events and came away with 7 medals, which I believe is a men’s record for Australian events.
So among other things, I’m 50+ Sabre Champion of Australia, Oceania, Asia and the Commonwealth. The Western Australia Championships were also awarded a couple of weeks ago, where I won Veteran Championships in all three weapons and the Master-at-Arms (all-rounder) Championship. All-in-all, a pretty good year!
Steve Johnson
05-12-2016 05:30 UTC
I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions.
If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in the call working as expected. I’ve chopped down our startup routine so you have an example.
; error : no function definition ; expected FUNCTION at [eval]
Awesome Bricsys Person
05-12-2016 12:32 UTC
Hi Steve,
There was a regression introduced in V17.1.10 that caused startup code to execute too early under certain conditions, before the lisp engine document context was properly initialized. This has been fixed now for the next update.
Steve Johnson
06-12-2016 02:43 UTC
I must say, the responses I’ve been getting to my support requests have been absolutely bloody brilliant. Cheers!
Let’s just finish the sequence, shall we?
Second Excellent Bricsys Person
13-12-2016 19:18 UTC
Hi Steve,
I have very good news. The fix is included in BricsCAD V17.1.11, available for download.
Thank you for your help.
Following a fast and straightforward download and install, I can confirm that the bug is fixed. The elapsed time from my bug report to the fix being publicly available and me being informed personally of the fact was 8.5 days. Note that this isn’t a workaround, patch or service pack, it’s a permanent fix that is now automatically in place for everybody who downloads the software.
Edit: the new version was actually released at 4 PM on 9 December, so it was less than 4.5 days from report to fix. Outstanding!
I should mention that I also received a prompt and relevant response from Dale at McNeel, despite the fact that the problem was nothing to do with him!
For somebody used to dealing with Autodesk, this is a breath of fresh air. Bricsys team, take a bow!
Hidden in amongst a bunch of the usual highly dubious subscription statements from Carl Bass is an announcement that spells doom for Autodesk perpetual license owners. I will resist the temptation to skewer Carl’s spin (for now) because this announcement is much more important:
Bass also confirmed that the company plans to converge the two existing subscription models — maintenance and product subscriptions — into a single offering over the next two years. “If you look out to fiscal year 2020, we want to be in a place where, first of all, we have a single kind of offering with a single back office and infrastructure to support it, one that will be a combination of product subscriptions as you see them plus a consumption model on top of it. That’s where we see the business heading.
“Along the way, it’s how do we motivate customers to move from one model to another in the program, what are the price points, and how does that transition work? In our mind, getting to a single model is really important. It will give the best service to our customers, it will be the most affordable for us to have, [and] we can start getting rid of some of the systems that were designed for a different era and concentrate on giving a world-class experience to users.”
Translation: Autodesk is going to drive up prices of maintenance subscription (perpetual license keeping-up-to-date fee) to match the much higher prices of product subscription (rental). Maintenance subscription will then be merged into oblivion. Your return on your long-term investment in Autodesk software will be zero. Your reward for decades of loyalty to Autodesk will be to have your software costs blown through the roof.
If you’re not already making plans to abandon the Autodesk ship, you really need to do so now. Don’t say I didn’t warn you. Don’t say Carl didn’t warn you.
Get out or get screwed big-time. I mean, get out or get motivated to transition into a world-class experience.
To be precise, I have a real problem with writing about BricsCAD. I’ve written some pretty complimentary things about BricsCAD lately. In the interests of balance, I’ve been intending to write about some of the issues people can expect to deal with when moving from AutoCAD to BricsCAD. Such issues certainly exist. The problem I have with that is that the issues keep going away!
Here’s how it usually goes. I find a problem in BricsCAD. I submit a support request. Within hours, I get a meaningful response from a person who understands the issue. Within days, I’m informed it’s been fixed internally and the fix will be in the next update. Within a week or two, that update is released. I download and install the updated version. It’s basically a full reinstall, but all settings are seamlessly retained and it’s faster and less painful than an AutoCAD Service Pack installation. The whole thing from start of download to completion typically takes 5 or 6 minutes. The problem is gone, and I have nothing to write about!
Here’s the latest interaction. This is typical, and has been repeated many times:
Steve Johnson
05-12-2016 05:30 UTC
I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions.
If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in the call working as expected. I’ve chopped down our startup routine so you have an example.
; error : no function definition ; expected FUNCTION at [eval]
Awesome Bricsys Person
05-12-2016 12:32 UTC
Hi Steve,
There was a regression introduced in V17.1.10 that caused startup code to execute too early under certain conditions, before the lisp engine document context was properly initialized. This has been fixed now for the next update.
Steve Johnson
06-12-2016 02:43 UTC
I must say, the responses I’ve been getting to my support requests have been absolutely bloody brilliant. Cheers!
Now, can you imagine the same scenario with Autodesk? I’m sure many of you have lived through it. First thing would be an automated response. A day or two later would be a confused support person coming up with totally unrelated links to Knowledgebase articles. A series of increasingly frustrating back-and-forth emails might go on for days or weeks until the Autodesk person finally plays their trump card, blaming the third-party routine (incorrectly) and/or stating that they don’t support users’ customization.
Such a problem would stay in AutoCAD indefinitely. Repeated reports, year after year, using subscription support and the forums and formal reporting mechanism in the Autodesk Beta program, would make no difference. Eventually I would give up and the problem would never get fixed. Again, this is typical, and has been repeated many times. This applies to bugs, incompatibilities, feature design, performance issues, user interface difficulties, documentation system idiocy, you name it. It’s massively frustrating and I know many very smart people who have given up even trying. The only exception is documentation content; that gets fixed as soon as possible, within the limitations imposed by Autodesk’s arcane systems.
The difference in attitude between Autodesk and Bricsys is glaring, stark, obvious. Autodesk pays lip service to providing customer service and software quality. Bricsys just gets on and does it.