Category Archives: AutoCAD

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.

AutoCAD for Mac review in Cadalyst (circa 1989)

3 Replies

A comment from Kal on Between the Lines mentions an AutoCAD Release 10.5 for Mac. My memory of ancient and useless AutoCAD trivia is usually pretty good, but this time things are a bit foggy and I need some help. I definitely remember there being some kind of half-release of AutoCAD for Mac*, but I’m not sure it was an official designation.

I do remember a Cadalyst review at the time, possibly by Art Liddle. I would estimate it to be from 1989, give or take a year. The then-new Mac release reviewed was some kind of hybrid between R10 and R11 (I think), with most of the feature set of one release and the DWG format of another. I had thought the product was called R11, but I could be wrong about that and maybe it was 10.5.

Is there anybody out there with a complete set of Cadalyst issues that goes back that far? Mine only goes back to mid-1995. If so, can you locate that review?

* Two decades ago, with a much smaller and simpler code base that was already non-platform-specific, Autodesk had to cobble together a hybrid release to provide native Mac support. How much harder would that task be today?

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.

AutoCAD 2009 Update 3

6 Replies

Update (nee Service Pack) 3 for AutoCAD 2009 is now available. See Between the Lines for full details. As always, read the readme first. Here are the links:

Readme
AutoCAD 2009
AutoCAD LT 2009
AutoCAD 2009 for Revit Architecture
AutoCAD 2009 for Revit Structure

No word yet about related updates for the vertical products.

While I’m not convinced by some aspects of the recently introduced multiple-update-per-release regime, I do approve of Autodesk continuing to maintain 2009 after 2010 has been released. People have complained about this not being done in the past, and on this score at least, I have to say that Autodesk has listened.

What do you think about these updates? Do you use them? What about CAD Managers using deployments; do you deploy the updates? Is it too disruptive? Does it cause problems with the deployment no longer matching the installation, for example when attempting a repair install? Any other issues?

Network/standalone clash is confined to Raster Design

4 Replies

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.

AutoCAD’s magic vanishing attachments

1 Reply

There are now quite a few file types that you can attach to an AutoCAD drawing as a reference, in the same way that you can attach other drawings as xrefs. We’ve been able to attach other drawings since Release 11 (1990) and images since Release 14 (1997), but every release since 2007 has introduced a new kind of attachment. In AutoCAD 2010, you can now also attach PDFs, MicroStation DGNs (v7 and v8), DWF and DWFx files.

But should you? Maybe not. It depends who is going to use those drawings after you. If you know for certain that every user of that drawing is going to be using 2010 and later, that’s no problem. But if there is the possibility of earlier releases being used, your fine-looking attachments could vanish silently in the night. Attach a PDF to your drawing in 2010, give it to a user of last year’s AutoCAD 2009 (you’ll need to save it as a 2007 DWG) and what will he see? Nothing. There is no text-screen warning, no bounding box, no piece of text indicating the file name, nothing. Just a blank space where there should be useful drawing content.

This problem isn’t new to 2010, because there are similar problems with the other recent attachment types. Let’s examine them one by one:

  • PDF – visible only in 2010 and later (except for the special case of 2009 with the Subscription-only Bonus Pack 2).
  • DWFx – visible only in 2009 and later.
  • DGN v7 – visible only in 2009 and later.
  • DGN v8 – visible only in 2008 and later.
  • DWF – visible only in 2007 and later.

It’s important to note that the attachments don’t actually disappear from the drawing. They are still stored there, even if you save to an earlier DWG format like 2000 or 2004. The attachments survive the round trip to an earlier DWG format intact; they will reappear just fine if reopened in 2010. (Round-tripping of new object types is something that Autodesk has done extremely well over the years).

In most cases, the objects are stored invisibly as proxy objects (object name ACAD_PROXY_ENTITY, known in the early days as zombies). In some cases, they are listed as special Underlay objects (e.g. DGNUnderlay, DWFUnderlay). In 2000 to 2006, they all list as proxies. How can you list these objects in earlier releases when you can’t see them? With a bit of LISP, or old tricks like LIST ALL Remove Crossing.

The moral of the story for drawing creators is to look before you leap whan attaching new object types. For drawing recipients, it’s something to carefully watch out for. If you’re the customer and you use an earlier release, you may even wish to include a don’t-use-this-attachment-type clause in your specifications.

Autodesk plans to fix Raster Design licensing SNAFU

3 Replies

I have been in touch with various people at Autodesk about Raster Design 2010’s failure to work in a mixed standalone/network environment. These people have all been suitably apologetic, they assure me it wasn’t a deliberate move on Autodesk’s part, and that moves are afoot to provide a solution fairly soon. For example:

Our intention was never to cause such inconvenience for our Raster customers with the licensing change. We are currently working on a solution and hope to have more information in the coming weeks.

And:

…we are very aware of the issue currently relating to the co-existence of an AutoCAD SLM and Raster Design NLM. This was not an intentional “change of licensing policy”, 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. I 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 (fix if you will) in the very near term…

The jury is still out about whether this problem affects only Raster Design or is a general problem that prevents a mixed standalone/network environment of AutoCAD and vertical products. If it’s a general problem, it would be an unmitigated disaster for the 2010 product range. I’m getting mixed messages about this from the Autodesk people, but I don’t want to make an issue of that because the people involved are trying to help by providing what information they have as quickly as possible. As soon as I have accurate information available to me I will pass it on.

I know of at least one person who is unable to get a mixed AutoCAD and Revit MEP environment working. If you have tried to get AutoCAD 2010 and another 2010 vertical product working side by side where one is standalone and the other network, please add your experiences to the comments here.

Autodesk messes up Raster Design 2010 licensing

10 Replies

I was horrified to learn (in this Autodesk Discussion Group thread) that Autodesk has changed the rules as far as the way Raster Design licenses are handled. It’s quite possible that Autodesk has also done this with other products that I’m not yet aware of. If so, please comment and let me know.

If you’re not familiar with Raster Design, it’s an Autodesk add-on that adds raster handling capabilities to AutoCAD and AutoCAD-based products. The change that has been introduced is that the licensing method of AutoCAD and Raster Design now has to match. That is, if your AutoCAD is standalone, the network version of Raster Design won’t run on it, and vice versa.

Why does this matter? Let’s say you’re a CAD Manager in this scenario:

You have a hundred AutoCAD users, half of which are full-time users with standalone licenses and the other half who are mainly part-time users with network licenses. Let’s say that some of those users (of both types) have a very occasional need to use the features in Raster Design. You bought one network license of the product a few releases ago and have everything on Subscription, just the way Autodesk wants it. So far, you’ve been able to provide the Raster Design option to all of your users. Only one user at a time can use it, but as use of the product is pretty rare, this hasn’t been a problem to date. If demand increased, other licenses could be added as needed.

Now, with Raster Design 2010, this is no longer possible. Your network license will not be available to your standalone users. You have the following options:

  1. Buy 50 standalone licenses of Raster Design 2010 for your standalone AutoCAD 2010 users, i.e. spend a huge amount of money on software that will go unused more than 99% of the time. Oh, and commit more money to maintaining that software with Subscription.
  2. Convert all your AutoCAD licenses from standalone to network. This is not a free service. Last time I looked, it cost about 20% of the retail price of a new seat. That means you will need to waste a huge amount of money changing your AutoCAD licenses to work in a way that is an inferior match with the way you do business. If you’ve already provided AutoCAD 2010 to your standalone users, you’ll need to uninstall them all and reinstall them as network versions. Won’t that be fun?
  3. Upgrade neither AutoCAD or Raster Design to 2010 and stick with the release you’ve got, i.e. waste a large amount of pre-paid Subscription money.
  4. Do without Raster Design altogether, i.e. waste the money you’ve spent on the product purchase and Subscription. In this case, you’ll probably need to put some time, effort and further expenditure into investigating and buying third-party alternatives that have a sane network licensing policy. Who said Autodesk is hard on its third-party developers? Look, it’s actively drumming up business for them!

Wow. This, in an environment where people are looking to save money. It doesn’t matter what efforts the Raster Design developers have put into improving the product. Raster Design could do twice as much stuff, twice as well, in half the time, while looking prettier and playing a tune. For many customers, this licensing decision has rendered the product unusable, so none of that stuff will matter. Why did you bother, people?

It’s such a spectacularly stupid move that it’s hard to comprehend that anybody within Autodesk could even seriously contemplate the idea, let alone allow it to get through to the finished product. Here are my top ten reasons why this is dumb even from Autodesk’s point of view:

  1. It adds another unnecessary pain point to CAD Managers. These are generally the people who are currently working out whether to upgrade, pay for Subscription, or stick with what they have and pay Autodesk nothing, so they are the people Autodesk should be most careful to avoid hurting.
  2. It will discourage some people from using the current release of the products.
  3. It will discourage other people from keeping their Subscription current.
  4. It will encourage some customers to ask for their money back for Raster Design, Subscription or both. If this is refused, it could even lead to another bad-publicity court case.
  5. It is a negative example people will use when deciding whether Autodesk can be trusted to do the right thing by its customers, once they are all tied into Subscription.
  6. It will discourage people who may have been interested in Raster Design from buying it.
  7. It will discourage people from investing in any other Autodesk add-on software in future.
  8. It will increase the perception that Autodesk doesn’t care about its customers and is always looking out for sneaky cash grabs.
  9. It will increase the perception that Autodesk is clueless about how its products are used in the real world.
  10. It distracts from the generally positive news about the AutoCAD 2010 product family. I’ve got some nice things to say about AutoCAD 2010, but I’m writing this instead.

Autodesk, this is a particularly nasty anti-customer move, and that’s the polite way of putting it. I stongly advise you to reverse this decision. I don’t care if you’ve made it technically difficult for yourself to do so; just do it. Please.

Disclosure: the above scenario is not a million miles from the situation in which I find myself. So it’s something that directly affects me. But it’s something so dumb and annoying that I’d still be ranting about it, even if that were not the case.

Autodesk Assistance Program and the educational watermark

2 Replies

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

Leave a reply

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

Leave a reply

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.

AutoCAD 2010 – Turning off InfoCenter

6 Replies

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

10 Replies

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

1 Reply

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.

A gaggle of geeks

6 Replies

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

8 Replies

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

Leave a reply

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

2 Replies

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

16 Replies

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.