Category Archives: Autodesk

Revolt of the Revit Ribbon Renegades

I hesitate to cover this subject because my understanding of Revit is very close to nil. I’m going to cover it anyway, because it relates to the Does Autodesk Listen? theme that I’ve discussed here in the past.

Revit 2010 has appeared with a Ribbon interface, and many users don’t like it. Some well-known Revit users, including bloggers, former Autodesk employees and Revit founders, have railed against the new release. Autodesk has been accused of ignoring long-standing wishlists and pre-release feedback. Autodesk has (it is said) wasted precious development resources by introducing a badly-designed and poorly-performing pretty new face at the expense of solving long-standing and much-requested improvements to the core product. The main complaint appears to be that Autodesk didn’t do much with this release, other than introducing an interface that doesn’t work as well as the one it replaced.

All this will sound very familiar to AutoCAD users, but there are some significant differences between the AutoCAD 2009 situation and the Revit 2010 one. First, I think it’s fair to say (even based on my limited knowledge) that the old Revit interface was in some need of attention. It was basically an old NT-style interface that had been left neglected for some years. Revit users may have been mostly happy with the way the interface worked, but the way it looked must have been a bit embarrasing, especially for Autodesk. Second, AutoCAD 2009 left the old interface in place for those people who wanted or needed to use it; with Revit 2010 it’s Ribbon or nothing. There is no transition strategy.

I’m not qualified to make a judgement on whether the complaints about the usability of the new interface are justified. I should also mention that not every Revit user hates everything about Revit 2010, and there are positive comments from some about the new interface. However, I can say that the anti-Ribbon arguments have been expressed not only passionately, but also intelligently and persuasively. It’s not so much a matter of “change is bad”, but more “this change is bad, and here’s why”. Here are some examples:

One More Thing…
One More One More Thing…
A Well-Intentioned Road Paving
Don’t Confuse Change with Progress
Autodesk Bob
Humpty Dumpty Sat On a A Wall…
Dear Autodesk
Revit 2011 – the most significant release EVER

Some of the threads from the AUGI Revit – Out There forum (requires free AUGI membership sign-up to view):

Revit 2010 – New Ribbon UI
1st impression from Revit 2010…
What is your official opinion of 2010?
Who do we complain to?
2009 vs. 2010
Revit evangelist fatigue

Finally, here’s a Dilbert cartoon that was somebody else thought was a relevant comment on this situation.

In a future post, I’ll discuss how Autodesk’s Revit people have reacted to this criticism. Is Autodesk listening? Is it issuing corporate feelgood drivel? Is it circling the wagons and shooting the messengers as they ride by? Or is it doing all of the above?

Network/standalone clash is confined to Raster Design

Autodesk has been in touch to confirm that the failure to allow a mixed network/standalone environment is confined to Raster Design. I haven’t yet tested this myself, but I’ve been told unequivocally that you can mix standalone and network license models for the major products.

Here is the official Autodesk response to the issue:

We are very aware of the issue currently relating to the co-existence of an AutoCAD SLM (stand-alone license) and AutoCAD Raster Design NLM (network license) configuration. This was not an intentional “change of licensing policy” as expressed in some blog posts this week, but an unfortunate side effect of updating our licensing technology for SLM (stand-alone) seats to be in sync with our NLM seats for all AutoCAD-based products. We can only apologize for this new behavior experienced by customers upgrade to 2010 version products.

We are currently pursuing a couple of options to rectify this situation. We do intend to provide a solution in the very near term and I hope you will join me in helping mitigate the frustrations expressed in various blogs this week.

We have also heard of speculations that this issue also impacts side-by-side installations of different AutoCAD desktops. This is not the case. Both software development and QA have successfully installed many different AutoCAD-based 2010 desktops side-by-side in mixed SLM and NLM configurations without any issues.

Should you read software license agreements?

Evan Yares has raised an interesting point about the insolvency clause in Autodesk’s End User License Agreement. Please read the whole thing, but the gist is that there’s a clause where if you get into financial difficulties, Autodesk will do its bit to help you out in times of trouble by taking away your software licenses.

This clause extends as far as making an arrangement with your creditors, which is a common enough phrase but can mean several things and isn’t defined within the agreement. So, if your cash flow is a bit tight and you have to ask your phone company for another month to pay your bill, you’ll be sure to stop using all your Autodesk software, won’t you? Never use it again, because otherwise you’ll be a thief.

OK, maybe that’s a bit extreme, but I’m sure it could be interpreted that way by an aggressive and/or inventive lawyer, and Autodesk doesn’t appear to be short of those. Who knows? Why would Autodesk put that kind of thing in its EULAs if there is no intention of ever using it?

That’s an interesting aside, but it’s not my main point. Autodesk EULAs have traditionally contained unreasonable, unconscionable and arguably unenforceable clauses, so there’s nothing particularly remarkable there. My main point relates to reading EULAs in general, not just Autodesk’s. As a general rule, should you do it?

Looking at the polls I’ve done on this subject, lots of you don’t read them. In fact, over two thirds of poll respondents either never read them, or rarely do so. It would be interesting to find the reasons behind that. Do you not have the time? Is it pointless because it’s all legal gobbledygook? Do you trust the software maker to be reasonable? Do you consider click-throughs to be unenforceable? Or are there other reasons? Please let me know. I may do another poll once I have a reasonable set of choices to offer up.

There’s an argument that can be made that you are actually better off not reading these “agreements”. According to this argument, if you don’t read it, how can you have agreed to it? There’s no meeting of the minds. Better still; get somebody outside your company to do the installation for you. That person has no authority to bind your company to anything, so no agreement exists.

Or does it? Is this a valid argument? Until there’s either well-established case law or unambiguous legislation, it’s anybody’s guess. Even when the answer is known, it’s highly likely that the answer will vary depending on your location. Even if the agreement states that it is based on California law, what if the local law establishes that no obligation exists that binds you to that agreement?

What’s the best thing to do? I honestly don’t know. You could do an R. Paul Waddington and make a public repudiation of any obligation to abide by Autodesk’s EULAs, and continue to use the software. You could do what I suspect a large number of people do, which is the same kind of repudiation, but a silent one. You could attempt to negotiate a modified EULA with the software vendor, but I don’t fancy your chances. You could stop using software with unreasonable EULAs, but what kind of choice is that? It may not be possible at all for your business. Finally, you could just put up and shut up, either agreeing unreservedly to accept whatever is in the EULA, or crossing your fingers in the hope that the software vendor will do the right thing.

What choice have you made, and why?

Autodesk Assistance Program and the educational watermark

You have probably seen blog posts about the Autodesk Assistance Program (see the FAQ PDF), promoted as a hand-up for the less fortunate who find themselves unemployed as a result of the current financial environment. The Autodesk PR makes it clear that the free software on offer is a 13-month student license. However, the consequences of using such software are not made clear, so I’ll spell it out here.

If you use Autodesk educational software, you are not supposed to use it for commercial purposes. So, if you’ve just lost your position and were hoping to set yourself up with a few odd jobs here and there, building yourself up to a full-time drafting and design shop, don’t use the Autodesk Assistance Program software to do it. It’s useful only to help you keep your skills up to date, nothing else.

What happens if you do use it for real work? Bad things. If Autodesk finds out, it might set a pack of rabid lawyers on you. How might Autodesk find out? Through your clients. Why would your clients tell Autodesk? Ah, that’s where the educational watermark comes into it.

Every DWG file saved by the educational version of AutoCAD is invisibly stamped, recording that fact. That includes blocks extracted using Wblock, of course. If such a drawing is ever plotted, even by a normal, fully-paid-up AutoCAD, a text stamp will appear along all four sides, proclaiming that the drawing is For Educational Use Only.

Trouble is, the invisible stamp passes from drawing to drawing like a virus, particularly among users of older releases. If somebody uses the educational version to just look at a drawing and happens to save it, that drawing is indelibly stamped with the mark of the Beast. If any part of that drawing is ever inserted into another, it carries the infection with it. It has been possible for companies acting totally honestly to end up with a large number of infected drawings, only to discover the extent of the disaster when plotting out a drawing set.

This has been less of an issue in recent years, because in AutoCAD from 2004 on, there’s a warning issued in the non-student versions of AutoCAD if an infested drawing is inserted or opened. It’s also possible for users of AutoCAD 2000 to 2002 to receive such a warning, using the EDU-Scan utility from ManuSoft.

Despite misinformation about this from Autodesk (e.g. “There is no way to circumvent the plot stamp” from here), such drawings can be cured. Innocent victims of the infestation can apply to their AutoCAD dealers for a special utility, time-limited to 15 days, to fix up the drawings. A DOS utility is also available that can identify the infected drawings. You may be asked to identify the source of the drawings before being provided with anything.

Alternatively, users of the non-student version can clean up infected drawings easily enough with an option of a very commonly used AutoCAD command. No, I’m not going to tell you which command, and please don’t email me to ask. I can tell you it was the first thing I tried when I came across such a drawing, and it worked perfectly. If you’re an innocent party in that unfortunate situation, a few minutes experimentation should see you right.

I wonder if an unintended side-effect of the Autodesk Assistance Program is going to be a rise in the incidence of educationally-tainted drawings. For those who ever receive drawings from other parties (probably most of us), it’s something to keep an eye out for. For those who intend using the Autodesk Assistance Program software, it’s a good idea to make sure you keep a tight rein on any drawings you produce with it. Because distributing student-stamped drawings is likely to do your future employment prospects no good at all.

Guillermo Melantoni’s 3D blog

What a Mesh is another new Autodesk blog, this time from Autodesk 3D guru Guillermo Melantoni. You may remember Guillermo mentioning his forthcoming blog in my A gaggle of geeks video, and now it has arrived. You can also see Guillermo in action in several videos about AutoCAD 2010’s new 3D mesh capabilities on AutoCAD Exchange.

Guillermo is very, very smart, he expertly uses the products he develops (the building on the AutoCAD 2010 packaging was done by him), and it’s great to see him interacting with users in this way.

New Autodesk blog for AutoCAD support

I’ve added a link to Without A Net, a new blog on support issues, technical solutions, fixes, and tips for AutoCAD. It’s run by Tom Stoeckel, global technical lead for AutoCAD product support. In my limited experience, I’ve found Tom to be a fine fellow with his customers’ needs at heart. This blog promises to be a worthwhile addition to the existing AutoCAD support mechanisms, and I commend Autodesk and Tom for introducing it.

More on ODA, Autodesk and click-through agreements

Evan Yares has provided more information on the incident I mentioned in my last post. Here it is:

It was years ago. My guess was that the person who did it was just trying to spider the website pages, for marketing research, and didn’t realize he got all the libraries too.

In any event, I said hey you did this, they said no we didn’t, I produced download logs, they said there was no agreement and even if there was we hereby cancel it, I said if you want to see our libraries I’ll send ’em to you no strings, they said no thanks, then I just let it drop. Of course, I’m paraphrasing.

I wasn’t going to get in a fight with Autodesk. Trying to trick them into joining the ODA would have been both futile and dumb. I’d been trying for years to get them to join (I was an optimist, once upon a time), and it caused no damage for Autodesk to be able to see the ODA libraries. There wasn’t anything in them that they didn’t know better than we did.

Don’t read too much into Autodesk’s belief in the enforceability of click-through agreements based on this incident. I knew the guy who downloaded the files, and knew that he didn’t have the authority to bind Autodesk to an ODA membership agreement (it would have taken at least a VP to do that.)

This is interesting for more than just the amusement factor; it raises a serious point about the enforceability of click-through agreements. In this case it was a web-based membership agreement, but I’m more interested in software license agreements.

In most cases, the person doing a software installation is unlikely to be a Vice President or higher. It’s quite possible that the installer doesn’t even work directly for the company that is supposedly agreeing to whatever terms may be hidden behind the “I Agree” button. In fact, that’s the situation I’m regularly faced with when I install software for a client. The client certainly doesn’t view the “agreement” and may not even know that it exists. The client hasn’t authorised me to negotiate a contract with anyone, only to get some software working. There’s no “meeting of the minds”. The software vendor may think that the client is bound up tight by the terms of the EULA; the client hasn’t agreed to anything and either doesn’t know the EULA exists or doesn’t consider it to have any validity.

Does it matter? Maybe not. It only really matters when one party or the other doesn’t do the right thing. Fortunately, I have honest clients and I’m confident that they will act in an ethical way on an ongoing basis. But will the software vendors do likewise? I don’t know.

Evan Yares, ODA, Autodesk and click-through agreements

I’ve always found it entertaining when the lawyers of CAD companies do their best to make their clients look like total jerks. The opening shots as presented by Evan Yares in his proposed ODA class-action lawsuit indicate that there is another rich source of recreational reading on its way. I’m sure it’s no fun for the lawyer-paying people involved, though.

You would think that Autodesk would be rubbing its corporate hands together at the prospect of the ODA being distracted like this. Or maybe not, if the bunfight throws up more little gems like this:

Autodesk had at least once gone to the ODA website, agreed to the click-through membership agreement, received their access password via email, downloaded each and every library on the ODA’s website, then denied they did it. (The ensuing conversation about this, between the ODA and Autodesk, was pretty interesting, to say the least.)

If that’s true (and I would welcome evidence from either party) it certainly puts an interesting slant on what Autodesk thinks about the enforceability of click-through agreements.

On a related subject, see the polls on the right. There has been one running for a while about whether you even read such “agreements”, and I’ve added two more. They ask if you feel morally and legally bound by the terms that lie under that “let me get on with the installation” button.

AutoCAD 2010 – Turning off InfoCenter

I generally avoid the still-awful Autodesk discussion groups these days, but I do hop in from time to time in the vain hope of seeing some improvement. In doing so, I occasionally pick up a gem, and that happened today. I think this one deserves a wider audience, so here it is.

In AutoCAD 2010, you can disable the InfoCenter toolbar by opening the
registry, and going to the following key:

HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R18.0\ACAD-8001:409\InfoCenter

In that key there’s a value with the name “InfoCenterOn”.

Changing that value from 1 to 0 will disable the InfoCenter toolbar.

Source: Tony Tanzillo in this thread. Note that the “ACAD-8001” part will be different if you use a vertical variant of AutoCAD.

Why would you want to do this? To improve startup times and reduce annoyance. Autodesk should have provided a better mechanism for doing this. The absence of convenient, designed-in off switches for new features is something I’ve complained about on many occasions over the years. Autodesk’s response has been patchy.

Edit: I just noticed Owen Wengerd has posted about this, including a LISP routine to simplify the process of turning it on and off.

Autodesk to more than triple upgrade prices

As reported at Revit3D.com, next March will see a major change to the way Autodesk prices its upgrades. All upgrades will cost 50% of the full retail price rather than the much smaller percentage that is currently charged. If you upgrade yearly, that means the cost of doing so will be about 3.35 times greater than it is now. Clearly, Autodesk doesn’t want you doing that, and would much prefer you to be tied into the Subscription program, and is introducing some subtle encouragement to nudge you in the right direction.

Here is the rationale according to an Autodesk spokesperson:

I can confirm that after March 16, 2010, a streamlined upgrade pricing model will go into effect–all upgrades, cross-grades, and retroactive Subscription fees up to three releases back will be priced at 50 percent of a full license.

We are doing this to better match the needs and buying behaviors of our customers. A significant number of our customers have already moved to Autodesk Subscription. Only a small percentage of customers who do not have Autodesk Subscription purchase upgrades every year. Most of those customers upgrade every three years.

We believe that simple, straightforward pricing will help make it easier to do business with us. We also believe the new policy will make it more convenient and cost-effective for customers to keep their Autodesk software up-to-date.

So now you know, it’s being done for your own good. Happy?

Some thoughts on AutoCAD Exchange

I’ve added a link to Autodesk’s new AutoCAD community site, AutoCAD Exchange. As with most things Autodesk, there are pros and cons. Here are my first impressions.

I think it looks good in a Vista-black kind of way. I know some of you don’t like the black look in software, but I do. The layout looks a bit cluttered and confused at first, but I’m sure visitors will quickly get used to where to find things. The site appears to be designed around 1024-wide resolution. If you have more than this, as most CAD users do, then there are wide areas of wasted space either side of the good stuff.

The front page is basically a teaser. To get to the useful content or do pretty much anything, you need to register or sign in. I don’t particularly like this, and it gives the impression (false or not) that Autodesk wants to own and control you, even if you’re just viewing a site. The registration process is the same as for other Autodesk sites such as the discussion groups, so if you have an Autodesk identity, you’re already registered.

As it is a “community” site, on first sign-in you are invited to fill in more details, provide an avatar and so on. Some people might not like this, but it’s optional and Autodesk knows where I live so it makes no difference to me. I know where Autodesk lives, too. It has yet to be seen if Autodesk manages to develop a real community on this site, and if so, how open that community is allowed to be.

Autodesk is encouraging bloggers to add an Autodesk Exchange widget to their blogs. I won’t be adding one in a permanent position because this is my blog and not Autodesk’s. I kind of like my independence, and if a company wants space on my blog they can pay for it. Anyway, the widget is available in three sizes and here’s what the largest one looks like:

I’m likely to appear in one of those little interview videos soon, as they were shot during the bloggers’ visit to San Fransisco in early February. When you do get to see it, yes, that’s really me (and Melanie Perry) saying nice things about AutoCAD 2010, it’s not computer generated. Except for the background, that is, which is computer generated. It was bright green in real life. Other than that, no deception, lies, arm-twisting or bribes were involved. Oh, unless you count the free trip to San Fransisco as a bribe. I interviewed Autodesk, they interviewed me, and I actually had positive things to say about AutoCAD 2010. More on that later.

AutoCAD Exchange is an important and potentially very useful site for AutoCAD users. Check it out, and if you feel like it, report back. You can pretty much say what you like here.

Bartz the blogger

Autodesk’s Executive Chairman of the Board (who has one or two other little jobs, too) has made a Yahoo! blog post in which she promises to kick a donkey, or something.

Yahoo! if of only tangential interest to me; I don’t particularly care if it thrives or if it dies. However, it’s good to see Carol communicating directly in this way, and it’s good to see her emphasise the importance of looking after the customer, placing emphasis on efficiency over innovation for innovation’s sake, and promising to do better at listening. Welcome to the blogsphere, Carol.

A gaggle of geeks

Time to lighten things up a bit, I think. While attending the AutoCAD 2010 product launch in San Francisco on 5 February 2009, I conducted a series of micro-interviews with a collection of AutoCAD bloggers and Autodesk employees. One geek asks 14 other geeks if they are geeks; nothing too serious here. I hope Shaan enjoys my tabloid journalist editing job right at the end.

YouTube link.

Thanks to all the interviewees:

Heidi Hewett, Autodesk blogger
Lynn Allen, Autodesk blogger
Melanie Perry, blogger
Robin Capper, blogger
Brian Benton, blogger
Todd Shackelford, blogger
Jon Page, Autodesk person
Matt Stein, Autodesk person and personal blogger
Shaan Hurley, Autodesk blogger
Donnie Gladfelter, blogger
Ellen Finklestein, blogger
David Cohn, blogger
Mark Douglas, blogger
Guillermo Melantoni, Autodesk person (still waiting for that blog, Guillermo!)

What is the collective noun for geeks, anyway?

Autodesk answers – 4 of 4

The final question is from metis:

Q: why is program size increasing and performance dramatically decreasing as hardware specs dramatically increase? as features “improve” and are added functionality should not be removed, and code should be streamlined.

seriously aren’t there any real programmers out there anymore? this thing isn’t written in java by a bunch of scriptkiddies (although 2009 sure is skinned like it was).

A: We made a number of performance improvements in AutoCAD 2010 over the previous release, and would appreciate hearing from you if you are encountering significant performance slowdowns with this latest release. If so, please send us details on what you were doing at the time, sample files if possible, and details on the machine you are using. This will help us improve performance further in upcoming releases of AutoCAD.

Autodesk answers – 3 of 4

The third question, courtesy of Earl Kubaskie, is:

Q: I would ask why there seems to be so little cooperation between the development teams. Vanilla, Map 3D, Civil 3D, each seem to be separate little empires. ACA might be in there, too, but I don’t use it, and thus I don’t apply for the betas.

I would think that closer interaction (and consolidation of beta testing teams) would smooth out the process – and maybe help get Matt his wish re bonus packs.

A: This is an ongoing area of focus for us, and this year we are making further changes that we believe will help bring the AutoCAD family of products closer together. In this release you’ll see consistency between the user interface as well as some of the new features, such as hatch enhancements, that behave similarly across AutoCAD products.

Autodesk answers – 2 of 4

In a comment on the first of these posts, Ralph G raised the possibility that these answers have been edited by marketing people. I have checked with Eric Stover and he assures me these answers come direct from the program managers concerned and are unmassaged by marketers. That ties in with the partial email trail that came with the answers. It also ties in with the impression I have formed recently that Autodesk is starting to open up a bit. That’s a trend I’m happy to encourage.

There’s one thing that clinches the marketing-interference matter for me. Despite Eric being on vacation when I sent in the request, the answers came back in days rather than weeks or months.

Enough of that, here’s the next question, courtesy of Matt Stachoni:

Q: Why haven’t the latest Subscription Bonus Packs been released for AutoCAD Architecture Subscription customers?

A: This year was the first time we released bonus packs continuously throughout the year to AutoCAD subscription customers, and we had a lot to learn about how to best deliver the bonus packs, and how often to release them. Based on our learnings from this year, our plan for the coming year is to ensure that AutoCAD Architecture (and other AutoCAD vertical product) subscription customers also receive any AutoCAD updates and bonus packs we deliver.

Autodesk answers – 1 of 4

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 a new release for a time, to spend an entire release cycle working on improving/restoring functionality of existing features and fixing bugs, why, or why not?

A: With any given release, we aim to deliver a healthy balance of new features & functionality along with improvements to existing functionality, so we can help enable new ways of doing design, but also provide more efficient ways of working the way you do today. We plan to continue this balancing act for future releases, but have also started delivering regular product updates (formerly known as ‘service packs’) throughout the year. So, rather than requiring you to wait for a new release of the product to get product improvements, this year we delivered 3 product updates that included hundreds of bug fixes to existing AutoCAD features and functionality.

Vernor v Autodesk – why I think Autodesk is right

Well, there’s a statement I wasn’t expecting to make. Let me preface these comments with a disclaimer. I have no legal qualifications whatsoever. I make no claims of knowing who is legally right in this David v. Goliath legal battle; that’s for the courts to decide. When I make the statement that I think Autodesk is right, I don’t mean legally right, I mean morally right.

I have been following this fight with interest, but only in a half-baked way, third-hand via commentators (like myself, now). Based on my skimming of that commentary, my natural inclination to support the underdog, and my general dislike of of Autodesk’s previous and current legal adventures, I had been of the firm but privately held opinion that Vernor was right and Autodesk was wrong.

Today, after noting that new filings had been made, I had a proper look at some (not all) of the actual court documents themselves (thanks to Owen Wengerd’s CAD/Court), and surprised myself by coming to quite the opposite conclusion. I am now convinced that I was totally wrong.*

Until today, I was hoping that the court would support Vernor’s assertion that the First Sale doctrine applies in this case. Why? Because I feel that Autodesk is morally wrong in attempting to prevent the transfer of its software from one party to another.** At one time, Autodesk allowed AutoCAD to be resold (despite the EULA of the time saying that it wasn’t allowed) and indeed actively supported the transfer process. I felt at the time that Autodesk’s introduction of this restriction of a customer’s ability to resell AutoCAD was morally wrong. I still feel that way.

I also feel Autodesk is morally wrong in geographically restricting the sale of its software, and in several other areas of its EULA. I would be quite happy to have a court find that Autodesk is legally wrong in those areas, too. Despite that, I feel that it would be A Bad Thing if Vernor won in this case.

Why? Because Vernor was selling software that effectively didn’t exist. He was selling used copies of Release 14, when those copies had already been upgraded to AutoCAD 2000. To me, that’s clearly morally wrong.*** If the court finds that First Sale applies here, then that opens the floodgates to allow anyone to sell old copies of any software that has been upgraded, and keep using the new stuff. I really don’t think that would be good for anyone.

Those of you who have been upgrading AutoCAD for the last 25 years, I hope you held on to all your old copies, because you could be sitting on a gold mine. Of course, unless the court is going to compel Autodesk to acknowledge all these new “owners” of AutoCAD and support them with the various magic numbers required to keep them alive, there are going to be a lot of disappointed buyers around, the word will get around, and the bottom will quickly drop out of the market.

* This is not a first, I assure you.

** It has been stated elsewhere that Autodesk can actually be persuaded to allow the transfer of its software outside the usual restricted areas of merged companies, deceased estates and so on. This may be so, but it’s not something I would rely on.

*** This is a quite different moral proposition from somebody continuing to use an old version of software after upgrading, alongside the new version, on the same computer. That’s something I find entirely morally acceptable, whatever any EULA may stipulate.

AutoCAD 2010 release date

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 accidentally. It’s a planned date and may yet change subject to various circumstances. It applies to AutoCAD and probably AutoCAD LT; the vertical variants of AutoCAD will have later ship dates, probably in mid-April.

Interestingly, in a conversation with an Autodesk Australia person today, I was told that the 2010 launch dates are staggered across the globe. (That’s launch dates, not ship dates). So although everybody in Australia with an Internet connection already knows what’s in AutoCAD 2010, Autodesk Australia itself is apparently not allowed to disclose any information about it until Monday, 23 March 2009. That’s kind of bizarre if true, and I suspect it may be based on some kind of misunderstanding, but that’s what I was told.