Category Archives: Autodesk

Can you work without a command line?

15 Replies

On the Project Butterfly blog, a recent poll gave these choices:

  • I can’t work without the command line
  • I think it’s time for a new way to draw without the command line

In a follow-up post, the observation was made that “We thought that only a few people would work without a command line, but the results were refreshing.” Apparently, only 66% of respondents selected the first of the available options.

To this I respond, “Beware the trap of the biased sample”. The poll asked people who are largely users of a product that involves drawing without a command line if they can work without it. In response, an amazing 2/3 of them say “I can’t work without the command line”, i.e. they can’t possibly do what they are currently doing, every time they use the product on which the blog is based.

How is that “refreshing”? 34% is an incredibly small number when the only alternative answer is self-contradictory. It should be very close to 100%, surely?

Every poll has a biased sample, including my own polls here. The trick is in working out how strong the bias is and determining if it invalidates the results. In this case, readers of the Butterfly blog are largely users of a command-line-less product and therefore likely to have a strong bias against the command line. So that 66% number would be a bit bigger if addressed to a more general population, I reckon.

I’ve added my own poll for my own biased sample (that’s you lot out there, largely users of a command line-based application) using exactly the same question format. I’m not entirely happy with the way the options are worded as it is not entirely neutral, but I’ll stick with it for the purpose of the comparison.

While I might dispute the conclusions that might be drawn from the poll, I must say that I like the way the Project Butterfly team is doing this in the open. It’s much better than the traditional Autodesk practice of claiming that what they are doing is supported by polls among customers, then refusing all requests for the full details of those polls. As the devil is in the details, I automatically discount any such claims based on secret research, from Autodesk or anyone else. I encourage the Butterfly people to keep doing what they are doing, regardless of any nitpicking from me; it is very refreshing (there’s that word again) to see Autodesk being open and I want to encourage it.

In addition to voting, I’d love to have you add your own comments either for or against use of the command line in CAD. It may be old and unfashionable, but does that make it inefficient? Have you tried turning it off in AutoCAD and running purely on Dynamic Input? Have you had experience with CAD or similar products without command lines? Let’s hear it.

Autodesk Subscription support – how is it?

5 Replies

I’d like to hear your experiences with the support that is part of the Autodesk Subscription package. My own experiences have been mixed, but I’d like to hear from you rather than push any particular barrow. Have you used it? Good, bad, indifferent, all of the above? Is it timely, efficient, knowledgeable, clearly communicated?

Please add your comments!

AutoCAD does a Cheshire Cat

4 Replies

In Alice’s Adventures in Wonderland, the Cheshire Cat gradually disappears until nothing is left but its smile. The AutoCAD packaging has done the same thing over the years until now nothing is left but the 0s and 1s. In Release 13, one box was not enough to keep all the materials, but Autodesk gradually slimmed it down until in recent years your slab of upgrade or Subscription cash gets you nothing but a DVD in a case (with or without a pack of cards). However, you can go cap in hand to Autodesk and ask for a real manual of your choice, which will be shipped to you free of charge.

A few days ago, Subscription customers in 37 countries were all automatically opted in to a download-only upgrade mechanism for all Autodesk software, not just AutoCAD. Here are Autodesk’s stated reasons:

  • Convenience—It’s more convenient than installing software from a DVD or CD and is available 24 hours a day.
  • Sustainability—Because there’s no printing, packaging, or shipping, it’s a more sustainable choice.
  • Central control—Software Coordinators can provide users with electronic access to upgrades and manage software permissions centrally.

So this has nothing to do with increasing Autodesk’s profit margins, it is for your benefit and to help save the planet; that’s nice to know. However, depending on your circumstances and the available bandwidth at both your end and Autodesk’s, downloading a couple of GB or so for each product (double it if you need both 32 and 64 bit versions) may not be convenient. If you want to receive an actual disc containing the software, you will need to change a Subscription setting. You should have seen an email about this containing a convenient link to a page containing that setting.

If you haven’t taken care of this yet, I suggest you log on to the Subscription site, edit your Subscription Center Profile (click on My Profile in the top right) and change the Delivery Preference setting to Box. If there are multiple contact people on your Subscription contract, I suggest you ask your colleagues (particularly the person designated to be the Contract Manager) to do likewise. Having a box shipped to you does not prevent you from downloading the software. I suggest you do this sooner rather than later, because if you leave it until less than a week before the next release (historically mid-March), you’ll miss out.

How will you react to Autodesk’s new upgrade pricing?

41 Replies

As I reported early last year, Autodesk is going to discourage you from paying for upgrades as and when you see fit. It is doing this by charging you 50% of the cost of a full license to upgrade from the previous release. The same 50% cost will apply if you crossgrade [edit: crossgrade from an non-current release, that is] (say if you move from AutoCAD to a vertical). If your product is more than three releases old, you can’t upgrade. This change takes effect from 16 March 2010. There were some discounted upgrade offers to get you signed over early, but these have now expired. If you are thinking of upgrading or crossgrading, I suggest you contact your reseller, get out your calculator and consider doing it in the next few weeks.

There is some laughable doublespeak in the Autodesk marketing of this change, such as “streamlining our upgrade pricing based on feedback from customers and resellers,” but I can’t imagine anyone being fooled by such nonsense. It’s obvious that Autodesk is not doing this because you all asked for upgrade prices to be trebled to make a nice predictable percentage, it’s doing this to force upgraders on to Subscription. Once you’re on Subscription, you’re paying a year in advance for an upgrade (bonus cashflow!), and you’re something of a captive market, theoretically providing Autodesk with a more regular source of income. (The financial crisis has knocked something of a dent in that theory, as many companies have chosen not to renew subscriptions for products that were previously used by now-retrenched employees).

If you’re already on Subscription, you may be feeling pretty smug right now. Don’t be. Once Autodesk’s user base is effectively converted to the Subscription model, Autodesk will be free to do all sorts of things to that user base. Things like jacking up Subscription prices, reducing or eliminating existing Subscription services, and slipping little clauses into the EULA so you’re “agreeing” that you will lose your license if you stop paying your annual fees. You may be able to think of other things that you won’t like but which will benefit Autodesk shareholders. Maybe not, because Autodesk is too nice to its customers? Maybe I’m just cynical? Then again, if a couple of years ago I had suggested that Autodesk would treble (sorry, “simplify”) upgrade prices, more than a few would have thought I was paranoid.

Autodesk’s various little Subscription carrots have had limited success among its customers, so now it’s time for the big stick. In effect, Autodesk is encouraging you to get on Subscription or get out. What to do? Jump off the upgrade/Subscription train altogether and stick with what you have? Upgrade once now and stick there indefinitely? Upgrade every 3 years? Buy a new license every 6 to 10 years? Hang on and hope Autodesk introduces an upgrade amnesty in a few years? Move over to one of Autodesk’s competitors? My guess is that a large majority of us are going to just do as we’re directed and get onto Subscription.

I’d like to hear from you. What are you going to do, and why? If you’re on Subscription already, are you concerned about what Autodesk might do in the future?

Disclosure: I manage several dozen Autodesk licences for a large organisation which has been on Subscription for quite a few years.

CAD International interview on drcauto and other subjects

1 Reply

This morning I spoke with CAD International‘s Nigel Varley. Here is a paraphrased summary of the interview.

SJ: When did CAD International buy the drcauto intellectual property rights?
NV: About two weeks ago.

SJ: You are currently helping drcauto customers with authorisation codes, is that correct?
NV: Yes, masses of them. It’s taking up a lot of our peoples’ time.

SJ: Are you charging for this service?
NV: Not at present.

SJ: Do you intend to charge for this service in the future?
NV: Maybe. We may need to, both to pay for our time and to recoup our investment. I don’t particularly like the idea of annual renewals for software, so we may do something different in future.

SJ: If somebody wanted to buy drcauto products such as LT Toolkit now, could they do so?
NV: No, we’re still processing the materials we were given when we bought the rights. It wasn’t left in a well-organised state. I’m not sure if that was done deliberately or if it was just like that.

SJ: Do you have any plans to continue development of LT Toolkit or the other drcauto products?
NV: It’s too early to say at this time. I understand it doesn’t work right now with AutoCAD LT 2010 with Update 2 applied, or on 64-bit Windows, or on Windows 7. It’s not clear at this stage how much work is involved in making it work. It should be doable, but we can’t make any commitments at this stage.

SJ: So do you have a timeframe for doing any of this stuff?
NV: No, it’s too early. We’re still processing it.

SJ: What about former drcauto employees helping people out with authorisation codes?
NV: They have no rights to do that. They don’t own the intellectual property, we do. People need to be very careful.

SJ: Are you contemplating legal action?
NV: I think I’ll keep that under my hat for now.

SJ: Do you foresee any problems with Autodesk if you go ahead with LT Toolkit?
NV: I don’t think so. Autodesk would be pretty naive, with competing products around at a lower price than LT and with LISP built in, to think that they would gain any sales by blocking LT Toolkit. They would just be shooting themselves in the foot.

SJ: Autodesk has always been strongly opposed to products like LT Toolkit. Are you concerned about legal action from Autodesk?
NV: Well, people say that Autodesk has been against it, but I haven’t seen any evidence of that. When I spoke to the late Gary D’Arcy he told me that Autodesk had never once even contacted him to try to get him to stop developing it.

On Deelip’s blog there has been some discussion about resellers and what they should be allowed to do, so I asked some questions along those lines.

SJ: What is the relationship between CAD International in the USA and Australia?
NV: We’re an Austalian company, moving into the US marketplace for those people in the USA who want to buy our products. We don’t have offices in the USA, but we do have people on the ground.

SJ: Is CAD International an authorised AutoCAD reseller?
NV: No. We’ve been selling Autodesk products for 15 years without a direct relationship. We buy from Scholastic like everybody else in the same position. It’s not worth becoming a dealer; the obligations are too great and the margins are not worthwhile. We’ve been asked on several ocasions over the years and always said no.

[Note: I’ve since read (in something written well before this issue was raised here) that Autodesk Australia intends to tighten up the reseller situation in the very near future. These things go in cycles, and have for the last 25 years.]

SJ: Does Autodesk have a problem with you promoting competing products such as Bricscad?
NV: They have never spoken to us about it in the past, but as we don’t have a direct relationship with them it’s not surprising.

SJ: I see from your web site that you are selling DWG TrueView for $195. Isn’t that a free product?
NV: That fee is for supply services; research services if you prefer. People can download it from Autodesk if they like or get it from us. We just put it on the site as a trial to see if anybody wanted to buy it.  Nobody has, yet.

SJ: I can’t say I’m greatly surprised by that. Has Autodesk contacted you about this issue?
NV: No, we’ve heard nothing from Autodesk. They don’t really care about us, we’re a pretty small player in the market.

[Edit: the $195 price tag has since vanished from the site.]

More on drcauto, LT Toolkit and CAD International

Leave a reply

Things have moved on since my first post on this subject in which I passed on the information that Leonard Liang (a former drcauto employee) could help with codes for LT Toolkit orphans. In recent developments

  • In a comment in a WorldCAD Access post, Nigel Varley from Australian company CAD International stated that they had bought the intellectual property rights to the drcauto software, and that drcauto codes and software obtained from former employees are illegal.
  • Another comment on the same post from former drcauto employee Kevin J Secomb lamented the demise of Gary D’Arcy’s dream and criticised CAD International for indicating in an email to users that they would charge for authorisation codes.
  • CAD International created a web page describing the situation with regard to drcauto products, including a statement that it would “offer immediate assistance to those needing new authorisation codes”.
  • Deelip Menezes made a blog post on the subject, followed by another one containing a reaction from Autodesk’s Jim Quanci. Poth posts are worth reading, as are the comments from various observers. The first post went off at a bit of a tangent about Autodesk’s apparent benevolence towards resellers that don’t toe the corporate line (drcauto is still listed as an Authorised AutoCAD reseller a decade after being dropped by Autodesk). The second post included words from Jim that the late Gary D’Arcy was a great character, albeit a pain to Autodesk. Having met Gary many years ago and followed the story of LT Toolkit with interest, I can confirm the truth of both statements.

I thought I would have a chat with CAD International’s Nigel Varley to see if I could clear up the situation as he sees it. It was a very interesting interview, the results of which I will publish very soon.

Autodesk’s cloudy drawing offering

6 Replies

Autodesk’s Project Butterfly is its latest offering in the Cloud (Software as a Service, SaaS, web-based software, whatever) area. This is a Labs technology preview (i.e. it ain’t cooked yet) of browser-based drawing system based on Autodesk’s purchase of Visual Tao. The idea is that no software other than a browser is required to create, edit or just view drawings. To try it out, head to http://butterfly.autodesk.com/ and pick on Try Now. If you’re interested in going further with it, you will need to create an account, which is a quick and painless process. This account is separate from your Autodesk ID.

For more details, see Scott Sheppard’s posts here and here, the Project Butterfly blog, and the Project Butterfly page on the Autodesk Labs site, which includes a series of videos such as this one:

I’ve had a brief play with it and while it’s not as horribly slow as I had feared (the Ribbon is much quicker than AutoCAD’s, although that’s not difficult), it’s currently an extremely limited environment. Other than viewing and some very crude drawing operations, pretty much everything I wanted to do either couldn’t be done, or couldn’t be done in a satisfactory way. Once I had discovered how to get a drawing out of the clouds and in my own hands (it’s not Save As), the export crashed with an HTTP Status 500 error. Apparently, the server encountered an internal error () that prevented it from fulfilling this request.

Teething problems aside, it’s hard to imagine anyone accustomed to full-featured CAD software actually spending all day drawing with this mechanism. In fact, I can’t imagine spending more than an hour on it before tearing my hair out; a few minutes was enough. It’s perfectly adequate for viewing and marking up, but as a drafting tool it’s just a toy.

But it’s a start, and Autodesk is wise to get its head into the clouds. If SaaS really is The Next Big Thing in CAD, then Autodesk would have looked very silly if it had missed the boat altogether. I’m not convinced that SaaS is going to have the impact that some are predicting, but I’ll cover that argument in a separate post.

Hope for Autodesk FM Desktop orphans

1 Reply

For those of us who have been following Autodesk for decades, it’s a familiar story. Autodesk buys a company or its technology, makes an Autodesk product out of it, and initially promotes it as the best thing since sliced bread. Autodesk subsequently ignores it to death, before finally killing it off and leaving customers in the lurch.

Autodesk FM Desktop suffered this fate, and if you go looking for information about the product on the Autodesk site you’ll find only a few dregs left over from the days when this was a viable product. At least in this case Autodesk has belatedly arranged a path out of the mire for its customers. FM:Systems will be taking over Autodesk’s FM customers, and your Autodesk FM Desktop licenses can be converted to FM:Interact Workplace Management Suite licenses. There is no data transfer mechanism yet (other than a DWF import), but something is supposed to be made available in the next few months.

(Edit: Marty Chobot from FM:Systems informs me that they will help customers who need to transfer data immediately).

For more information, see www.fmsystems.com/fmdesktop, especially the FAQ.Edit:

Vernor wins (for now), customers don’t

1 Reply

Don’t get too excited, because I’m sure Autodesk will appeal, but as reported at Owen Wengerd’s CAD/Court, Vernor has won the right to resell his used copies of AutoCAD. While this is seen by some as a victory for customers, it isn’t. This doesn’t open up a brave new world in which we are allowed to sell the software we buy once we’re finished with it. If it had, I would be rejoicing as loud as anybody, because Autodesk’s ban on software transfers is an unconscionable restriction and deserves to die. But that’s not what this decision means. There are specific and paradoxical circumstances here, which allowed Vernor to win this case despite being morally wrong in my view, but will not benefit legitimate software users.

Vernor won (for now, and in one jurisdiction) because the court found he was not a party to the EULA. He didn’t read it, he didn’t click on anything to indicate his agreement to it, nothing. He just bought a bunch of books and discs and wanted to sell them on eBay. The fact that the item being sold is a remnant from software that had already been upgraded was not considered relevant. Neither was the fact that Autodesk is not obliged to provide the buyer of the discs with the codes they will need to make the software work.  The upshot is that this decision will allow a small number of people to buy and sell useless discs. What about the buyers of those discs who may not know they are useless until too late? Caveat emptor, I guess. Some other court can sort out that mess.

I agree with Ralph Grabowski that “software should be no different than any other consumer good: buy it, use it, resell it, or toss it”. I’d love to see Autodesk and other vendors forced to support a legitimate used software resale market (as they once did in pre-eBay days), but this decision won’t make that happen. It won’t help customers at all. If your firm has shrunk a bit and you have some spare licenses, you still can’t sell them because you are a party to the EULA (probably, although this area is still a bit fuzzy). But take heart! If you go bust, your creditors may be able to slip any discs left over from your upgrade history into a garage sale and hope that Mr. Vernor drops by. Mr. Vernor will be allowed to sell them, and the new buyers will be allowed to put them on their shelves and look at them.

Is that really a win for customers? I don’t think so.

Trusting Autodesk? Contemplating a new product

5 Replies

Last week, in my capacity as a de facto CAD manager for a large public utility company, I was having a chat with an Autodesk Australia person (he’s a nice guy and very honest, by the way). The topic of conversation moved to the new AutoCAD-based vertical, Plant 3D 2010. At that stage, I had not even installed the 30-day trial, but I still raised some of the issues that potentially stood in the way of the company adopting this apparently highly suitable product.

In a word, it comes down to trust. Each drawing used or issued by this utility is a legal document with a potentially very long life ahead of it. I showed the Autodesk person a drawing issued in 1901. The assets documented by that drawing are still in use today; indeed, many thousands of people daily depend heavily on them. Before we invest our money, time and training in Plant 3D, we need to know that the electronic drawings produced with it are going to be fully functional in the long term.

In terms of a new product like Plant 3D, can we trust Autodesk to do the following?

  1. Still be around and providing CAD software for many years?
  2. Go on supporting this new product for many years?
  3. In the event that the product is discontinued, provide an alternative, together with a migration path that retains full drawing intelligence?
  4. In the event that the product is discontinued, continue to provide ongoing support at least to the level of allowing the product to run and be transferred from one computer to another?
  5. Provide a product that works as well in real life as it does in demos?
  6. Provide a product that, from first release, works without crippling restrictions or bugs that render the product unusable?
  7. Include adequate support for national standards?
  8. Sell the product for a reasonable price on an ongoing basis?
  9. Provide Subscription for a reasonable price on an ongoing basis?
  10. Provide the product in such a way that we have flexibility in our use of network and standalone licensing long-term?
  11. Continue to allow the licensed use of earlier releases and use at home?
  12. Provide full API access to the custom objects, including ActiveX?
  13. Provide adequate object enablers for all recent AutoCAD releases and variants?
  14. Support the ongoing use of DWG files by other releases of this product freely up and down within a 3-release DWG version bracket?
  15. Provide full visual integrity, editability of proxy objects and round-tripping of intelligence, when saving to plain AutoCAD, including earlier releases?
  16. Provide mechanisms that allow any company-based custom work to be distributed easily to internal and external users and carried forward to new releases reliably?
  17. Avoid introducing problems and restrictions that would interfere with customisation and other aspects of CAD management?

Feel free to add to my list in your comments. If you go down the list giving a Yes, No or Maybe, how well does Autodesk do? Before looking at the product, I’ve got one Yes, a few Maybes and a very large number of Nos. That’s not based on paranoia or hatred, just on past history, including very recent history.

For example, can Autodesk be trusted to still be selling Plant 3D in a few years’ time? Ask the users of Autodesk FMDesktop. The same can be said of any of the other products in a long list of Autodesk abandonments that goes back to the dark ages. Generic CADD, anyone? What do I do with all my old Graphic Impact files?

Is it likely that Plant 3D will work properly in the real world in the first release or two? Ask the users of Civil 3D who tried to get any grading done for the first few releases. Very major and obvious problems in new products can go on for years before being addressed.

I’d be interested to hear how well you think Autodesk rates for new-product trustworthiness. There are other aspects to trusting Autodesk, and I will cover these in a future post. Please wait for that one before launching into any generic tirades; for now I just want to know about your level of Autodesk trust, purely in relation to new products and continued support for existing ones.

Ribbon acceptance in AutoCAD and Revit

24 Replies

AutoCAD Ribbon use (and non-use) may have been the hottest topic on this blog to date, but it’s a storm in a teacup compared with what has been going on between Revit users and Autodesk. More on that later, but for now I’d just like to pass on a statement made by Autodesk BIM Design Product Line Manager Anthony A. Hauck on the AUGI forums that:

Recent data on other Autodesk applications having both the new and “classic” UI show about a 2 : 1 split in favor of the new UI.

I would be interested to know the full details behind this assertion. Whenever I see a baldly-stated statistic like this, my first thought is “where did it come from?” Without full details of the data and how it was obtained, every statistic like this is suspect at best. It could just as easily be useless or misleading. I’m afraid I’ve become rather cynical whenever I see any kind of Autodesk statistic. When challenged in the past, Autodesk has consistently failed or refused to back up its marketing statistics (or even vague assertions that certain secret Autodesk-supporting statistics exist) by providing the comprehensive details required to make them useful. I’d love to be proven wrong in this case, but I won’t be holding my breath.

Instead, I’ll just ask you and we’ll see how the numbers compare. Over on the right, there are two new polls on Ribbon use; one for Revit and one for AutoCAD. If requested, I’ll do similar polls for Inventor and 3ds Max. Please add your vote and feel free to comment.

AutoCAD virus protection update

3 Replies

As I mentioned in my last post, I had some reservations about the code provided by Autodesk to deal with suspect acad.vlx and logo.gif files. Based on a suggestion from Jimmy Bergmark, I have written my own, safer version which you can download here: clean_virus_safe.lsp.

The comments at the top of the clean_virus_safe.lsp file explain what to do with it, but I will reproduce some of the relevant points here.

  • Purpose: Checks for existence of acad.vlx and logo.gif files, which are associated with virus AL/Logo-A, also known as ACAD/Unexplode, ACAD/Agent.A or ACM_UNEXPLODE.B. Written as a safer alternative to Autodesk’s code which deletes suspect files without prior warning. This code renames the files instead.
  • Legal: Provided as-is with no warranty whatsoever, use at own risk. May be distributed freely.
  • Usage: Append the contents of this file into a startup LISP file (e.g. acaddoc.lsp in your search path – create such a file if it does not exist). Autodesk’s suggestion to modify the acad20xx.lsp file should not be followed: this is bad practice. The acad20xx.lsp file is Autodesk’s file and any modifications you make to it are likely to be lost when updates and patches are applied.
  • Effects: Any and all files named acad.vlx and logo.gif and located in AutoCAD’s search path will be renamed, e.g. “acad.vlx” will become “[Suspected Virus] acad.vlx0”. The name will end in a number starting with 0. If other suspect files are later found in the same location, those files will be renamed to end with 1, 2, 3 and so on.

I don’t have a copy of the actual virus, and would like to get hold of one with a view to possibly improving this code. If you have a copy, I would be grateful if you could contact me so I can dissect it.

Another AutoCAD malware warning

2 Replies

Shaan Hurley has posted some useful information about another AutoCAD-based virus that is doing the rounds, and I strongly suggest you read it. However, I have some reservations about the solution that is posted there and in the Autodesk knowledgebase.

The LISP code suggested will delete any files called acad.vlx or logo.gif that are located in the current user’s current AutoCAD search path. There are a couple of problems with that.

  • The search path will change depending on the user, the profile, the startup folder and the drawing folder. That means you can’t just use the code once and expect the problem to go away; the code will need to remain in place permanently to ensure it does not recur. That may not be a huge problem, although it will have a performance penalty (particularly where the search path is long and/or includes network paths) and it is one more thing to remember to carry over to future releases.
  • More importantly, the code has no idea if the files it is deleting are legitimate or not. It is quite possible for a custom environment or third-party utility to make use of a file called acad.vlx, and there are all sorts of reasons you may have a logo.gif file floating around. The Autodesk code will just erase such files without prior warning, which is a bit naughty.

I commend Shaan and Autodesk for posting this information and proposed solution. However, I recommend caution before using this code as suggested. Check with your CAD Manager (if you have one) first to ensure there are no legitimate acad.vlx files in your environment. Do a search for these files yourself and see if there is a legitimate reason for them being where they are.

As with most malware attacks, taking care with incoming files is a very important part of the solution. Don’t just blindly use the contents of a zip file full of drawings, even from a trusted source. If somebody sends you a zip file containing an acad.vlx file, let the sender know about the problem and ask for an uninfected set of files.

The 12-month cycle and shipping software with known bugs

9 Replies

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 “bugs” and “known issues”. He states that if a bug is discovered and the software is then adjusted such that it does not abort the software in a badly-behaved way, and this is then documented, then the bug ceases to be a bug and becomes a “known issue”.

I disagree. Bugs can cause crashes or not; they can cause “nice” crashes or not; they can be known about prior to release or not; they can be documented internally or not; they can be documented publicly or not. As far as I’m concerned, if the software doesn’t act “as designed” or “as intended”, then that’s a bug. Here’s what Wikipedia has to say, and I concur:

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program that prevents it from behaving as intended (e.g., producing an incorrect or unexpected result).

That doesn’t mean that software that is “as designed” (free of bugs) is free of defects. Defects are things that make the software work in a way other than “as it should”. They can be bugs, design errors or omissions, performance problems, user interface logic failures, API holes, feature changes or removals with unintended undesirable consequences, and so on. Unfortunately, defining “as it should” isn’t a precise science. You can’t just compare the software to the documentation and say that the differences are defects. The documentation could be faulty or incomplete, or it could perfectly describe the deeply flawed way in which the software works.

While I disagree with Deelip’s definition of bugs, I couldn’t agree more with a more important point he makes in his blog post. That point is of a fixed 12-month cycle being the root cause of a plethora of bugs/issues/whatever making it into shipping software, and this being an unacceptable situation. This is a view I expressed in Cadalyst before I started participating in Autodesk’s sadly defunct MyFeedback program, and it’s a view I hold even more strongly today.

In conclusion, I would have to say that the fixed yearly release schedule is not good for AutoCAD. It is good for Autodesk, certainly in the short term, but that’s not at all the same thing as being good for AutoCAD or its users.

I’m not alone in thinking this. The polls I’ve run on this subject, discussions with many individuals on-line and in person, and many comments here and elsewhere, indicate that a dislike of the 12-month cycle is the majority viewpoint. For example, when asked the question, “Do you think the 12-month release cycle is harming the quality of AutoCAD and its variants?”, 85% of poll respondents here answered “Definitely” or “Probably”. In another poll, 71% of respondents indicated a preference for AutoCAD release cycles of 24 months or greater.

Somebody please tell me I’m wrong here. Somebody tell me that I’ve misread things, that customers really think the 12-month cycle is great, and that it’s not actually harmful for the product. Anyone?

* Or hundreds. Or thousands.

AutoCAD for Linux – another bad idea

31 Replies

I often see calls for Autodesk to support AutoCAD on Linux. Just like AutoCAD for the Mac, while I can sympathise with the users of that OS, I think a native port of AutoCAD for Linux would be a bad idea. Again, I think it would be bad for everybody: Autodesk, AutoCAD for Windows users, and most of all, AutoCAD for Linux users.

Why? First of all, for most of the same reasons I gave for the Mac port. Autodesk hasn’t just failed in the past with AutoCAD for the Mac, it has failed with AutoCAD for Unix, too. I remember Autodesk being very enthusiastic about the Sparc port in particular (AIX, too). I know personally of customers who were caught up in that enthusiasm and invested heavily in a Unix environment, only to bitterly regret it a few years later when Autodesk abandoned them. Would this happen again? Probably.

Second, the numbers just don’t add up. Current PC OS market share is running something like this:

Windows 88%
Mac OS 10%
Linux 1%

While the Windows share is currently falling (thanks, Vista) and the others are steadily rising, there’s a long way to go before Linux has the numbers to make the investment worthwhile. In any case, it is likely that most Mac or Linux users of AutoCAD wouldn’t be new customers, simply existing users using a different OS. Not much of a cash cow, is it?

I dislike the Windows monopoly and support the open source movement, so I would love it if Autodesk could just snap its fingers and provide all its software on whatever platforms the users want. Mac? Sure. Linux? Great, why not? The reality is that it’s not that easy. It’s expensive to do and expensive to go on supporting in the long term. Unfortunately, it just doesn’t make commercial sense, and wishing it did will not make it so.

Go and snag a free Snagit, quick!

1 Reply

For the next few hours, you can get a free registered version of the screen capture software Snagit from TechSmith. It’s a couple of versions old and not supported on Vista, but nevertheless is well worthwhile. No, the Print Scrn key isn’t the same thing at all; Snagit is much, much more useful than that. Try it for yourself, you can thank me later.

To get the freebie, first get a registration key by clicking here and then download your copy of Snagit 7.2.5 from here. Be quick, because this offer closes at 5 PM EST (9 PM GMT/UTC) today, 5 June 2009.

Even if you were planning on buying the latest version of Snagit, get this freebie anyway. As a registered user of Snagit, you automatically qualify for upgrade offers. This means you can get the latest Snagit for US$24.95 rather than US$49.95 (depending on location).

TechSmith has another screen capture utility, Jing. This is also free, with a more powerful version available at a cost. Which is the best TechSmith screen capture utility? Dunno, I’ve never used Jing. Grab ’em both and see what you think.

Source: mCADForums via SolidMentor.

Disclosure: at Autodesk University 2006, I was given free copies of Snagit 8.1 and Camtasia Studio 4.0 (thanks Shaan), both of which I still use regularly (i.e. it’s not shelfware). I was also given a TechSmith T-shirt, which I ruined within hours by spilling red wine on it.

Why AutoCAD for Mac is a bad idea

78 Replies

There has been a fair bit of open discussion from Autodesk lately on the subject of a possible future OS X AutoCAD version. The more I think about this, the more I am inclined to believe that this would be a bad idea. A very bad idea.

It pains me to write this, because I’m very much a user advocate and I’m arguing here against something that some users have been requesting for a long time. If you’re one of those users, I’m sorry, but I think this is one of those cases when giving you what you want would be bad for everybody, and bad for you in particular.

Now, this sort of platform discussion often degenerates into a quasi-religious debate, so let’s see if I can head it off at the pass. If you’re a Mac fan who wants to tell me the benefits of your chosen computer family and how inferior Windows is, save it. I’ll concede right here and now that you are probably right. My experience of Apple products has generally been very positive. They look good, they’re well made, they work well, the Mac OS has been shamelessly copied by Microsoft for decades, and so on, ad nauseam. Yup. Not disputed. Also, not relevant to the point I’m about to make.

Ever since the last multi-platform AutoCAD (Release 13), Autodesk has dedicated its primary product solely to Windows. Since then, the code base has been spreading its mass of roots deeper and deeper into the Windows soil. Any Windows-specific advantage the developers can take has been taken. Reversing or working around that process is a very substantial undertaking. If it were done, I think it would have the following outcomes:

AutoCAD for Mac would suck

The performance is likely to be poor, because all the Windows-specific stuff will have to be redirected, recreated or emulated. The stability is likely to be awful, because this will be new ground for almost all of the developers involved. Developers with AutoCAD experience are going to have little or no Mac experience and vice-versa. They would be trying to make significant changes to the code base at the same time that that code base is being modified for the next release. The bug level is likely to be abysmal, both for the above reasons and also because the number of pre-release testers available to Autodesk on this platform is likely to be relatively tiny. The user interface is likely to be an uncomfortable square-peg-in-round-hole effort, which will work badly and be derided by OS X users.

AutoCAD for Mac would be half-baked

Not just half-baked in the usual let’s-put-this-out-as-is-and-maybe-we-can-fix-it-later way, but half-baked by design. The Autodesk survey implies that serious consideration is being put into a version of AutoCAD that is missing some of the things that make AutoCAD what it is. Things like paper/model space functionality, the command line, 3D, LISP, the ability to use third-party apps… AutoCAD for Mac LT Lite, anyone? If the APIs are not all there, that means no OS X version of any of the AutoCAD-based vertical products, either.

AutoCAD for Mac would be bad for Mac users

Last time this was attempted, it was a failure. The early 90s attempt at AutoCAD for Mac lasted for two three releases: 10 to 12. Autodesk had little option but to pull the pin on a non-viable product, but the orphaned users weren’t happy. Fortunately, there weren’t that many of them.

Would this happen again? Yes, I think it probably would. Any Mac user with any sense wouldn’t touch the first new Mac release with a bargepole. That, of course, makes it much less likely that there would be a second or third release. Autodesk’s corporate culture (espoused very strongly by Carol Bartz, but dating back to John Walker) encourages brave attempts that may lead to failure. This policy has unfortunately left large numbers of orphans in its wake over the years. In the event of poor sales, Mac for AutoCAD users would just be another set of unfortunates to add to a long list.

AutoCAD for Mac would be bad for Windows users

The very substantial effort required to produce any kind of AutoCAD for Mac at all would be a major drain on very limited (and shrinking) development resources. That means Windows users of AutoCAD would look forward to a release (or more likely several releases) with fewer new features, less completion of existing undercooked features, and longer waits until bugs and other problems get fixed. This, in exchange for no benefit whatsoever to those users. In fact, the decoupling of Windows-specific calls and the likely introduction of extra bugs would probably make AutoCAD for Windows work less well than it otherwise would.

AutoCAD for Mac would be bad for Autodesk

Autodesk is currently trying to save money by closing down offices, dropping products, cutting down on expenses and sacking employees (some of whom were long-termers; irreplaceable sources of information about use of the product and why certain things were done the way they were). In such an environment, does it make sense to start up a new project with high resource requirements and limited potential benefits? Especially when it is just a repetition of a previous project that was a complete failure?

So, in addition to costing Autodesk a lot of money and harming the quality of its core product, a failed AutoCAD for Mac would leave behind more Autodesk haters and be rather embarrassing.

I must admit that a lot of this is based on guesswork, but it’s educated guesswork. I’ve been educated by history, if nothing else. Autodesk’s corporate consciousness has an occasional habit of ignoring the lessons of history and repeating old mistakes. I hope AutoCAD for Mac – The Sequel isn’t one of those occasions.

Autodesk’s Revit rebellion reaction

11 Replies

It’s time to examine how Autodesk has reacted to the widespread criticism of Revit 2010. Is Autodesk listening? To be more specific, is Autodesk’s Revit team listening?

The Good

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* R13, CUI *cough*) is generally absent. I’m not seeing Adeskers arrogantly accusing users of their criticism being based on a failure to understand the product. I’m not seeing asinine comments that infer that the negativity is simply a symptom of the critics’ resistance to change. Actually, I’ve seen one such comment, but it wasn’t from an Autodesk person.

Overall, the Revit team’s responsiveness, openness and level of public availability is impressive. It’s so good that it puts other Autodesk teams to shame. When was the last time you saw an Autodesk person respond to criticism of AutoCAD in the Autodesk discussion groups or AUGI forums? Revit people are doing quite a bit of it, and by looking back I can see that they have been doing it for a while.

There was one attempt at a traditional corporate “the product is great, we just need to review our communications” message. Unsurprisingly, it didn’t work (read the comments). Denial, spin, obfuscation; these things never convince the people who need to be convinced, so why bother? While it’s good to see a reaction from somebody pretty high up in the chain of command, the people lower down have been doing a much better job of communicating with their customers.

The Bad

The trouble with all this communication is that it’s a couple of years too late. It’s no good putting a huge amount of effort into something, introducing it to users, then discovering too late that the users hate it. No amount of communication after the fact can make up for that kind of blunder. Exposing an early design to a handful of people in restricted circumstances can be useful, but it’s nowhere near enough. Lots of people need to be exposed to a product for a long time (as the Revit team now acknowledges – see an interesting Autodesk blog post here). The earlier it’s done, the better the product will be. As a bonus in these difficult times, this will lower the overall cost of development, because problems get exponentially more expensive to correct as the development cycle progresses.

From the public comments I’ve read, the Revit Ribbon was presented to beta testers as late as January, and by then it was very much a fait accompli. There was little chance of making it work significantly better, and none whatsoever of removing a bad design from the product before shipping. This scenario is, unfortunately, confined to neither Revit nor this particular instance. Although I can’t comment on my own Autodesk pre-release experiences, if you have read enough public discussions over the years you will undoubtedly have seen this kind of conversation a few times:

Angry user: “This feature is useless! The beta testers must have been blind to miss this!”
Beta tester: “Actually, we did see it and reported it right away. Autodesk just didn’t fix it.”

I would like to expand on this, but I am somewhat restricted by NDA. I’m not complaining about that (it’s a voluntary agreement), just stating the position I’m in.

Another thing that belongs in this category is the Revit team’s apparent disdain for its users’ wishlists. AUGI Revit people are convinced that their wishlists are being ignored, and I can see for myself that Autodesk’s own Revit wishlist discussion group is hardly a hive of activity.

The Ugly

Autodesk showed the cloven hoof with its exclusion of Phil Read from Autodesk University.* This reflects extremely badly on Autodesk. See here, here, here and here. Almost everybody seems to think this crude and futile attempt at censorship was a deplorable move, and I agree. Besides this being an example of messenger-shooting at its worst, it’s not a good look for the AU event itself. When you pay your AU fees, are you hoping to see the most knowledgeable, enthusiastic, passionate and inspiring speakers available? Or just the ones with opinions that align with Autodesk?

* My reaction is based on the assumption that this exclusion did take place. It has been widely reported and condemned, but not denied by Autodesk, so I think it’s a pretty safe bet. The only comment from AU management is, “Speakers for AU 2009 will be announced around June 15 – I cannot comment before.”

Who is this person?

15 Replies

The first person to identify the pixellated personage below will win a virtual doughnut. Bonus sprinkles will be provided if anyone can identify the other people, the event, the location and the year.

Mystery person

Picture courtesy of Donnia Tabor-Hanson (CADMama), from this thread in the AUGI Coffee Without CAD forum. I encourage you to read that thread and see if you can contribute to the idea it is promoting, but not until you’ve had a guess here! Readers of that thread and the people appearing in the photo should recuse themselves. Over to you!

Edit: lots of right answers (which I’ve now unhidden). Well done, Owen!