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 …
In my effusive welcome of AutoCAD 2013’s updated Help system, I wondered if I had been shocked into missing some glaring problem. Unfortunately, that’s exactly what happened. In my enthusiasm, I managed to totally miss the fact that the new system has not been introduced for offline users.
If you use the new system, there’s a link on the front page to the offline files. I got as far as downloading and installing what I thought was the offline version of the new system and discovered that it didn’t want to install because the old one was already installed. What I should have then done, and didn’t, was to uninstall the old and install the new, before running it in offline mode. I intended to get around to that to check the performance and responsiveness of the respective versions, but didn’t have the time right then. …
For many users, the most useful new feature in AutoCAD 2012 is going to be the updated Array command. It adds a great deal of very welcome new functionality that will provide a potential productivity boost for 2D and 3D users. But it’s from an Autodesk wedded to its infernal 12-month product cycle, so of course it’s half-baked.
So what’s good about the Array command in AutoCAD 2012?
Associativity. By default, arrays are now associative objects. This means that if you want to, say, modify the distance between columns a couple of days after you drew them, you can now do so. If you’re a Ribbon user, it’s easy to change array parameters because when you select an array, you get a Ribbon tab dedicated to just that task. If you’re not, then the Properties palette allows you to do the same thing.
In a comment in response to a Deelip post yesterday, Brad Holtz pointed to an article he wrote in 1999. It’s interesting to note that while much of the computing world today bears little resemblance to the scene at the end of the last century, this article remains almost completely accurate and relevant. Indeed, it’s so right that you might even be tempted to think, “Duh, isn’t that obvious?”
One section that stood out to me had this to say:
Many software systems never even get beyond the acceptable stage …. vendors of these systems are continually coming out with new versions, never stopping long enough to fix the problems with the existing systems.
It’s fascinating to me that this observation came at the very time that Autodesk was switching from a company that wasn’t exactly like that to one that very much was (and still is today), …
After an interminable delay and a complete absence of information from Autodesk (no, “contact your reseller” doesn’t count, especially when they don’t know anything either), it seems Raster Design 2011 is going to be released on 20 July. If that’s correct, those of you who use, say, image formats not directly supported by AutoCAD (e.g. ECW, MrSID) are finally going to be able to start using AutoCAD 2011, “only” 117 days after its release.
Don’t worry, I’m sure Autodesk will be refunding 1/3 of this year’s Subscription fees for both products. (Yes, that’s a joke).
I only hope the delay has given Autodesk enough time to fully fix the network/standalone SNAFU that blighted the Raster Design 2010 release. It’s still broken for users of network AutoCAD 2010 (or related vertical) and standalone Raster Design 2010. As there appears to be nothing new in the product except Windows 7 and 2011 …
This 5th post concludes the Callan Carpenter interview series. For the record, this interview was done in real time over the phone, with no prior notice of the questions.
SJ: The 12-month cycle that you have for most of your software has come under some criticism from all sorts of people, especially me. Once you have your customer base practically all on Subscription, what’s the incentive for the 12-month cycle to persist?
CC: In what way have you criticised the 12 month cycle?
SJ: In that it damages the product. In that there’s not enough time to release a properly developed product within that 12-month cycle. This is an observation that many people have made going back many years. That’s the basis of the criticism; not that, “Oh no, you’re giving me more software”. Well, there are people who complain about that but I don’t think that’s a valid criticism. …
My poll on this subject is still running (see right), but so far about 2/3 of respondents rate AutoCAD 2011’s new browser-based Help system as 0, 1 or 2 stars out of 5 (total fail, very poor or poor). Frankly, I’m surprised it’s doing as well as that. Have a look at this discussion group thread to get an idea of the sort of reaction I was expecting it to receive. (Kudos to Autodesk’s moderators for allowing the discussion to continue with relatively little obvious censorship, at least so far).
There are many good new things in AutoCAD 2011, but Help isn’t one of them. Even if you like the concept of online help, this implementation of that concept is a failure. Even when used offline, this release’s browser-based Help is manifestly inferior to its CHM-based predecessor. Yet another victim of the 12-month release cycle, this feature is horribly …
In a recent blog post, Deelip Menezes appears to be shocked by the very idea that a particular CAD company (no, not Autodesk) would ship software that contains known bugs. I thought he was joking, because he’s surely aware that practically all software companies with highly complex products release software with known bugs. As Deelip points out, those companies with 12-month cycles are particularly prone to doing this. There is no possible way any company can release something as complex as a CAD application within a fixed 12-month cycle without it containing dozens* of known bugs (because there isn’t time to fix them after discovery) and dozens* of unknown ones (because of insufficient Beta testing time).
Reading Deelip’s post and subsequent comments more carefully, it becomes clear that he doesn’t mean what a casual glance might lead you to believe he means. Deelip makes a specific distinction between …
It has been good to see extensive public participation by Autodesk people in various discussions in different places. The Revit team isn’t hiding. It is asking for feedback on the Autodesk discussion groups, the AUGI forums and its own blogs, and getting lots of it. Much of it is negative, but it is to Autodesk’s credit that I’m not seeing much in the way of denial, or demands that the criticism must be constructive. I’ve been trying in vain for years to convince some people at Autodesk that denial is counterproductive and that criticism doesn’t have to be constructive to be useful.
The sort of messenger-shooting that I’ve seen some Autodesk people do from time to over the years (*cough* …
At the end of January, I asked for your questions to put to Autodesk product managers. My intention was to pose your questions in a video interview format while attending the AutoCAD 2010 product launch, but for logistical reasons I was unable to make this happen.
Autodesk’s Eric Stover kindly arranged for your questions to be answered anyway. The delay in getting these answers back to you is my responsibility, not Autodesk’s. The answers come courtesy of the following product managers:
Diane Li – lead manager on AutoCAD;
Guillermo Melantoni – 3D and Parametrics expert;
Kathy O’Connell – customer requests, quality improvements, and 2D improvements.
I will post each question and answer a day apart, to give you chance to comment on each issue separately. Here is the first question, courtesy of Chris Cowgill:
Q: With the current release cycle being so short, has anyone considered suspending …
After my recent attendance at the AutoCAD 2010 launch, I have a few dozen subjects I’d like to blog about, lots of video editing to do, and not enough free time in which to do it. Many of my fellow launch-attending bloggers have beaten me to it with many of the meaty bits, but I’ll be covering much of that stuff in my own way and from my own perspective over the next few weeks.
One thing I can do with minimum effort is to pass on an important piece of information I haven’t seen mentioned elsewhere yet: the date that Autodesk plans to actually ship AutoCAD 2010. That date is (drumroll)…
Tuesday, 24 March 2009
No great surprises there; the 12-month release cycle continues as usual.
Although this information was imparted to a room full of bloggers in an on-the-record session, I suspect it may have slipped out …
I’ve now closed the poll that asks this question, and the results show a typical bell-curve shape with the peak clearly on “Half-baked”. There is a slight bias to the bottom end, but not a significant one.
This result doesn’t surprise me, as I’ve seen and heard a lot of user comments to that effect, and I’ve made such comments myself. I’m not saying that this poll is definitive proof of anything, but it sits pretty well with my perception of what AutoCAD users generally think.
Now I’d like you to consider a related question. If we accept for the sake of argument that the average major new AutoCAD feature is half-baked, is that necessarily a bad thing? There are some valid arguments that can be made for pushing out features before they are complete. I’ll examine the pros and cons from my perspective later, but for now I’d …
No, I don’t mean the sort of crash where AutoCAD stops working. The current financial crisis, I mean. I must preface these comments with a disclaimer. I have no qualifications in finance and make no claim of financial expertise. These are purely a layman’s thoughts. Don’t buy or sell stock based on what I have to say here. Toss a coin instead.
So, what on earth am I thinking? I’m thinking that although Autodesk (along with most other companies) will undoubtedly suffer greatly from the coming economic conditions, it’s not all dark cloud. Here are some potential silver linings.
Autodesk is cashed up. If its competitors aren’t all carrying enough fat to survive the lean times, Autodesk could come out of the post-crash period with greater market share than before. Of course, this is contingent on Autodesk having products, customer service and a customer-friendly outlook that are attractive enough to …
I’ve just added a poll asking this question. Actually, the poll question is rather longer than that, because I want to make it as unambiguous as possible. Other polls I’ve seen on this subject, including ones by Autodesk and Cadalyst, have always left room for speculation about what a given answer would actually mean. Sometimes, the question has been so ambiguous that the results have been completely meaningless. I’ve tried hard to avoid that, and if that means the question is rather long, so be it.
In my poll, you’re being asked to consider a scenario where over a long period of time (10 years, say) the total charge from Autodesk for upgrades or Subscription would be the same, no matter what the release cycle. You would also get the same number of major new features, minor new features and other improvements. Your ability to choose to pay either upgrade fees or annual …
I’ve opened a poll asking for your opinion about whether the 12-month release cycle of AutoCAD and its variants is harmful to the quality of the software that Autodesk is providing. I won’t express my own opinion on this subject here yet, but will do so later, once the poll is closed. In the meantime, I’d love to hear your opinions on the subject.
One of the banes of AutoCAD over the past few years is the phenomenon of the half-baked feature. A new feature is added to the product with serious design deficiencies and/or bugs and other shortcomings that make it much less useful than it should have been. I’m sure you have your own favourite examples of this. I may expand on this theme in future, but for now let’s concentrate on one brand new and particularly undercooked feature, the Action Recorder.
The ability to record and play back macros is undoubtedly something that many users want, and has featured prominently in some wishlists. Autodesk has now provided the Action Recorder. Wish granted, right? A shining example of Autodesk listening to its customers and providing what they want and need? Not exactly. In fact, this wish has only been granted at the most superficial level.