Category Archives: Other Autodesk Products

MDT users and other Autodesk orphans, let’s have your good news stories!

I was going to ignore this subject, but I’ve changed my mind because it allows me to post something positive about Autodesk. After all, I do try to post positive things; it’s hardly my fault that Autodesk has a habit of making it difficult.

In upFront eZine #756, Autodesk’s Andrew Anagnost (or was it Clay Helm?) had the following to say, and must say I agree totally with the first sentence:

The best evidence is how we have behaved historically. When we included Mechanical Desktop with Inventor, the media complained that we were killing Mechanical Desktop; you were probably one of them. But we didn’t; we came out with six, seven more releases of it, completely free.

So, MDT users, you’re the poster child for how Autodesk looks after its customers. You’re also evidence for how wrong those nasty media naysayers can be. So here’s your opportunity to offer your gratitude to Autodesk for looking after you so well and giving you all that completely free software. Or perhaps you’re the user of another Autodesk product that fell out of fashion or was deemed a technological dead end (like desktop software, apparently). Let’s hear your good news stories about how well Autodesk treated you and your investment.

If you don’t want to add a comment, there’s a poll over on the right. I look forward to seeing the “Brilliantly” option show a near-100% rating!

Who is telling the truth in Autodesk’s Cloud PR trainwreck?

Does Autodesk intend to move all its applications exclusively to the Cloud? That is, online only and no longer available on the desktop? Autodesk people who say yes:

Carl Bass, CEO
Phil Bernstein, Vice President, Building Industry Strategy and Relations
Scott Sheppard, Autodesk Labs Software Development Manager (with private Cloud caveat)

Autodesk people who say no:

Kenneth Pimentel, Director, Visual Communications Solutions
Andrew Anagnost, Senior Vice President of Industry Strategy and Marketing
Clay Helm, Public Relations Manager for Manufacturing, Cross-Platform, Sustainability, and Consumers
Various other underlings who make reassuring but non-specific noises about expanded choice, or who admit to inconvenient impracticalities

There’s huge irony in the way Clay (or Andrew) attempts to paint the shafting of MDT customers as a we’ll-look-after-you example, but I think that’s a deliberate distraction tactic; other than this comment I’m going to ignore it. I’m ignoring, too, the spin about informal interviews, misinterpretation and the like. There’s a black-and-white contradiction here. Autodesk either intends to move all its applications online and away from the desktop, or it doesn’t.

Two men say they’re Jesus
One of ’em must be wrong
Dire Straits – Industrial Disease

So who do we believe? Last time I looked at an org chart, the CEO trumped the lot. The buck stops with Carl. So why is he letting his underlings go around undermining his Cloudy Vision? I see the following possibilities:

  1. Autodesk is going Cloud-only but it’s supposed to be a secret. Carl let it slip out and the underlings have been sent to try to cover the tracks by confusing and obfuscating.
  2. Autodesk is going Cloud-only, Carl had it right, but the underlings haven’t all been told yet and are incorrect in their “corrections”.
  3. Autodesk isn’t going Cloud only and Carl was just making stuff up on the fly. Why? To try to impress what he thought was a specific audience who wanted to hear that. It’s ironic that the nature of the Internet meant that the comments made its way to pretty much everyone, including the customers who ultimately pay his salary.

None of these options makes Autodesk look good. Is there an option 4? Feel free to speculate. Ultimately, the only chance of sorting this out is by Carl Bass himself coming out with a definitive and spin-free statement. Even then, will anyone believe him?

I have lost all trust I had in you
Opeth – To Rid The Disease

I can agree with one thing Clay (or Andrew) had to say; you will get the best idea of what’s to come by looking at Autodesk’s history. So if you’re concerned about Autodesk pushing you onto the Cloud against your will, don’t be. Instead, be afraid. Very afraid.

AutoCAD Help suckage to continue – confirmed

In a recent post on Between the Lines, Shaan passed on the following response from the AutoCAD Team:

There has been some recent discussions about the built-in help system in AutoCAD 2013, both positive and some criticism.  As our longtime users know, AutoCAD help has been through many evolutions.

We are particularly proud of the new AutoCAD 2013 online learning environment we recently released (AutoCAD Online Help Mid-Year Updates.) This update addressed several user requested fixes and changes, and we will continue to take our direction from our user’s feedback.

We do recognize that the online learning environment may not be the solution for every user, so while we are focused on creating a rich and personalized online experience, we will continue to maintain our current basic offline experience.

(The emphasis is mine). This statement, although couched in marketingspeak, confirms what I’ve had to say on the subject. Here’s my translation into plain English:

AutoCAD 2013 Help sucked, the customers said so, the recent update improved matters somewhat for online users, but the awful old system stays in place for offline users. The offline system is in maintenance mode, and the experience will continue to remain basic (i.e. it will suck long-term).

There’s no mention of correcting this situation; it’s clearly a matter of policy rather than some unfortunate accident.

Today, I was using Autodesk Navisworks Manage 2013. As you might expect from an Autodesk product, it’s powerful but unstable. In addition to the lockups and crashes, it has various bugs and annoyances. In looking for a way of working around one of the annoyances, I delved into the Help system. Strangely enough, this product (much younger than AutoCAD) uses something that looks remarkably like an old-fashioned CHM-based Help system. It worked offline. It was quick. It had contents, search and index tabs, and they worked on a Windows 7 64-bit system. It had a hierarchical structure and a breadcrumb bar that helped me understand the context of what I was reading. Using it was, in short, a breath of fresh air.

Memo to Autodesk: if you’re going to try to make online Help look good by mangling offline help, you’re going to have to do this to all your products at once to make it remotely convincing.

Trebling upgrade prices was not enough for Autodesk

A blog post from BIM person Gregory Arkin contains a number of confidently-made statements about what Autodesk intends to do with its upgrade and Subscription pricing model. If the information is correct, the news is all bad for customers. The prices for both upgrade and Subscription are getting jacked up substantially. In fact, for upgraders the pricing (70% of full whack for the cheapest upgrade) will be completely non-viable and you’ll effectively be forced onto Subscription. This goes beyond the trebling of upgrade prices that Autodesk’s Callan Carpenter spent some time defending here two years ago. The link in that post to the relevant Autodesk page doesn’t contain any pricing specifics other than the vague statement “save up to 20%”, but I’ll take Gregory’s word for it.

Gregory sees this business of upgraders being hunted to extinction as something that Subscription customers should have a good laugh about, but he’s wrong. Resellers can have a chuckle, but Subscription customers should mourn the lack of choice for customers. It means customers are no longer able to compare Subscription with any kind of sane upgrade pricing and make a decision about the best option for them. This lack of internal ‘competition’ is not even worth a snigger, because it inevitably means Subscription prices shooting up. Autodesk has racked up Subscription prices already and will do so again next year. For those customers who have fallen for the ‘free’ upgrade-to-suite offers, their Subscription prices will be higher again. With everyone on Subscription, Autodesk will just keep pushing up prices indefinitely. From Autodesk’s point of view, there is no down side to this; tie people in and the gravy train goes on for ever.

There are various terms in common use for this kind of thing. One is price gouging. Anybody who has ever booked a hotel near a big sporting event or bought drinks at a nightclub will be familiar with the realities of businesses doing this whenever they can get away with it. It’s part of the free market and generally perfectly legal, no matter how unpopular it makes the business. However, it only works when competition is effectively absent and customers are left with no realistic alternative but to pay up. Autodesk obviously thinks it is in such a position. Is it right? Sadly, history says it probably is.

Edit: This post originally stated that Gregory is a reseller. He has informed me that this is no longer the case and I have edited the post accordingly. My apologies to Gregory for the misstatement.

Autodesk edges towards taking money for Cloud services

In an email to Subscription customers, Autodesk made several announcements about its Autodesk 360 Cloud services.

  1. Subscription users now get 25 GB per seat of Cloud storage, up from 3 GB. Non-Subscription users who create an Autodesk 360 account get 3 GB. The intent here, as with the trebling of upgrade costs, is to get you hooked on Subscription so you become a permanent revenue stream.
  2. More services are now available, apparently, but the list of services looks about the same to me. The table that lists which services are available for which products can be found here. If you’re an AutoCAD user, the only service available is Autodesk 360 Rendering.
  3. The services are now metered. You get a certain number of “cloud units”, and these are eaten up as you use the services. A standard AutoCAD user (with Subscription) gets 100 units. Each render costs you 5 units, so effectively you get 20 on-line renders per seat. That’s enough for a taster, but if Cloud rendering is as brilliant as Autodesk says it is, you’ll soon use that allocation up.
  4. The metering doesn’t mean anything – yet. If you use up all your units, it doesn’t matter. You can go on using more of them as long as you’re on Subscription.
  5. This free lunch will end as soon as Autodesk says so, or as soon as it puts a mechanism in place to charge you for units. No news yet on when that might be, but as parting you from your money is obviously the whole point of the exercise, I can’t imagine it will be too far in the future.

Autodesk reserves the right to change all of this without notice, and to terminate access to Autodesk 360 services at any time and for any reason.

Cloud concerns – security again

It’s probably worth pointing out that if you you have no problem emailing your designs around the place without some form of protection or encryption, there’s little point in getting all worked up about Cloud security. Email isn’t remotely secure. FTP isn’t exactly watertight, either. If you’re still interested in Cloud security issues, this post includes some relevant links you might like to peruse.

First, here’s what Autodesk’s Scott Sheppard had to say about Project Photofly (now 123D Catch Beta) security last month: Project Photofly FAQ: What about the security of my data? This covers some of the same kind of stuff I’ve already discussed, but from an Autodesk point of view (albeit a pretty transparent and honest one, as you might expect from Scott). Here are some selected quotes:

In essence, we don’t want to accept liability when we don’t take money…

We intend to have a reasonably secure service, better than email, but less secure than a bank account.

We store your files on Amazon’s S3 service, and they maintain their own physical and data security policy that is considered robust.

Next, here are the 123D Terms of service, which raise many of the same alarm bells I mentioned before. Selected quotes:

We reserve the right to change all or any part of these Terms, or to change the Site, including by eliminating or discontinuing the Site (or any feature thereof) or any product, service, Content or other materials, and to charge and/or change any fees, prices, costs or charges on or for using the Site (or any feature thereof).

By uploading, posting, publishing, transmitting, displaying, distributing or otherwise making available Shared Content to us and/or any Users of or through the Site you automatically grant to us and our sub-licensees…the worldwide, perpetual, royalty-free, fully paid-up, irrevocable, non-exclusive, sublicensable (through multiple tiers) right and license to have access to, store, display, reproduce, use, disclose, transmit, view, reproduce, modify, adapt, translate, publish, broadcast, perform and display (whether publicly or otherwise), distribute, re-distribute and exploit your Shared Content (in whole or in part) for any reason and/or purpose (whether commercial or non-commercial) by any and all means in any and all media, forms, formats, platforms and technologies now known or hereafter devised, invented, developed or improved.

Please note that with respect to Non-public Content, we will not authorize your Non-public Content to be made available to others on a public section of the Site, although we cannot guarantee complete security (e.g., of cloud servers).

Moving on to another Cloud security-related issue, something that Owen Wengerd raised on Twitter was the idea that:

…once data is on the cloud, it can never be deleted.

Deelip Menezes thought this whole idea somewhat loopy:

Actually I’m implying that it is ridiculous to even start thinking along those lines. 😉

However, I see Owen’s point. Once your data is on someone else’s server, you have no control over it. You have no idea where it lives, how often it is backed up, what happens to those backups, and so on. Let’s say you place some highly sensitive design data on the Cloud. It might be commercially sensitive, or about something that represents a possible terrorist target, or just something you don’t want certain parties to know about, ever. A week later, you delete the design data. Now, is it really gone? Any responsible Cloud infrastructure vendor must regularly take multiple backups and store them securely. So you now have multiple copies of your “deleted” data floating around, who knows where? What happens to old servers when they die? Where do backup hard drives, tapes, etc. go? If backups are stored off-site, how are your files going to be permanently removed from the media?

While there may be policies, procedures and ISO standards in place, we’re dealing with humans here. If one backup copy of your data ended up in a country where a rogue employee decided to better feed his family by selling off old hard drives, your nuclear power plant plans could end up not safely deleted at all, but instead delivered into the hands of some people you’d really prefer not to have it.

This may sound like paranoid nonsense, but risk from non-deleted data is real. There was a local case where a company was illegally siphoned of funds and went bust. The company’s old internal email servers were supposedly wiped and sold off. Somebody bought them, undeleted the data and was able to pass on incriminating emails to the police. While that ended up being a good thing in terms of natural justice and it’s not even a Cloud issue, it illustrates that making sure your stuff is properly deleted can be very important. This is related to something that Ralph Grabowski mentioned on Twitter; the “right to be forgotten”. Here is a Google search that includes various links that touch on some of the struggles related to this issue.

Finally, here’s something related to the possibility of the data being accessed illegally while it’s up. You put it up there, somebody copies it, you delete it, it’s not really gone and you are none the wiser. Is that something that only tin foil hat wearers need worry about? Have a read of this article before answering that one: Cloud Services Credentials Easily Stolen Via Google Code Search. Selected quotes:

The access codes and secret keys of thousands of public cloud services users can be easily found with a simple Google code search, a team of security researchers says.

Now the team is offering one word of advice to companies that are considering storing critical information on the public cloud: Don’t.

…an attacker who knows Google and some simple facts about cloud services authentication can easily find the access codes, passwords, and secret keys needed to unlock data stored in public cloud services environments such as Amazon’s EC3.

We found literally thousands of keys stored this way, any one of which could be used to take control of computers in the cloud, shut them down, or used to launch attacks on other computers on the same service.

Here’s a PDF of the presentation, if you’re interested.

Autodesk Cloud-based structural engineering software review

As I’ve already discussed, one of the areas where CAD on the Cloud shows potential is in handling specific tasks that require performing intensive calculations that are suitable for sharing among many processors. That sounds great in theory, and a lot of Cloud marketing (e.g. Virtually Infinite Computing) emphasises that point.

OK, that sounds promising, but how does it pan out in real life? One problem dissuading me from finding out is that Autodesk is being very restrictive with access to many of its Autodesk Cloud products (I’d probably throw a few sample render jobs into the Cloud and compare the performance, but I’m not the right kind of Subscription customer so I’m not allowed). Another problem is that I’m not qualified to review things like structural engineering software where the greatest computational potential appears to lie. Fortunately, Alex Bausk is qualified, so it was interesting to read his review of Autodesk’s Project Storm software.

It’s important to point out here that anything Autodesk with ‘Project’ in the name is not a finished product. It’s an Autodesk Labs thing, designed to attract feedback rather than use in production. I very much approve of this process. It’s one area in which I’m happy to endorse the way Autodesk is approaching the whole Cloud thing, and has several benefits over the flawed private Beta process that Autodesk uses for its mainstream products such as AutoCAD.

The downside for Autodesk when it comes to doing pre-release things publicly is that the criticism can be public, too. For example, selected from Alex’s review:

…the product is, for reasons unknown, available only in selected countries…

…utterly meaningless popups…

Options for analysis settings are, to put it short, appalling.

Project Storm is nothing more than a web envelope for our good old ARSA package. It is basically the same “Robot link” that reviteers have already had for quite a long time…

But the software’s practical use is extremely tiny, to the point of no use at all. You may surely forfeit all hope to do anything with it that would even remotely be relevant to all the “cloud analysis” hype in videos, intros and announcements.

I was unable to make any use of Storm with the sample models that come packed with Revit Structure and Robot Structural Analysis. To feed these default, Autodesk-made models to Storm, some really disruptive editing had to be made that involved deleting whole parts of the model, rendering it practically useless, only able to demonstrate how the process is meant to work.

Ouch! OK, so far it’s mainly just pointing out how half-baked the product is at this stage. Given that it’s a Project and not a finished product, that’s not so bad. It’s shipping products and features that are half-baked that I object to, and Autodesk has certainly produced a few of those. Anyway, here’s the bit I found particularly interesting:

Analysis speed, to a surprise, isn’t looking any good compared to desktop. The Storm’s cloud web analysis is extremely slow, likely because the server would yield a tiny fraction of its resources to your particular task.

In other words, the cloud speed and resource claim in case of Project Storm is no more than a standard cloud computing mantra.

…cloud calculations took around four minutes for this simple model, compared to fraction of a second using desktop…

What does this all mean? It could mean that Alex forgot to turn on the Ludicrous Speed toggle. It could mean that Autodesk is doing this experiment on the cheap and hasn’t paid for enough resources to make it work well. If so, that would be pretty short-sighted, and if Carl wants this Cloud thing to impress people he should sign off on a bunch more cash for Scott’s server farm budget. It could mean that this type of calculation is unsuited to parallel processing, in which case it’s probably not a great candidate for a Cloud product. Or it could mean that the calculation parts of this software haven’t been done properly yet, and everything will fly like the wind as soon as the developers get the hang of things.

Or maybe, just maybe, it means that the reality of Cloud computing isn’t quite as infinitely powerful as the hype makes out.

Autodesk Cloud interview May 2010 – Part 3

Steve: Another issue I have with Cloud-based environments is the lack of customisation. One of the things that makes AutoCAD so efficient for people is that they can get it exactly the way they want it. With a browser-based environment, we’re pretty much stuck with what you guys decide to give us. Can you see any solution to that in the longer term?

Tal: From a pure technical point of view, there’s not a lot of difference in terms of the way you can customise an application on the desktop versus customising it on the web. I think AutoCAD, having a very mature application has a lot of functionality which has built up over the years to provide customisation capabilities to the nth degree. So I think it has less to do with the platform of your choice and more to do with the maturity of the solution and how much customisation the people who designed the product wanted to put in there.

Steve: I guess you have the issue of where does that customisation live? Does it live on the PC or on the Cloud?

Tal: A good thing about moving it to the Cloud would be that if you moved to another computer, the app would still be customised to your needs.

Guri: I was going to say the same. It’s actually an advantage to store it in the Cloud because regardless of where you are accessing it from, you can still have your customisation go with you wherever you go.

To address your previous question about customisation, I think it’s a pretty relevant request to be able customise this application. But at the same time, remember who is the target audience for that. If you are an AutoCAD user, we assume you have AutoCAD with all the advantages that come along, but if you are not an AutoCAD user, you are somebody downstream that just wants to look at a document and collaborate on it, then you’re probably less sophisticated from that perspective and you will probably require have less customisation needs. Nevertheless, I do believe that the request to add customisation to this product is completely relevant.

Steve: As well as user customisation, there are third party developers wanting to be able to add their own value to the product. Do you see that being available in the longer term, that you will provide an API for third party developers, whether they are commercial developers or in-house developers for large organisations to do their thing with it?

Guri: We are considering it.

Steve: That’s tricky, isn’t it? It’s more difficult than if you have a desktop environment. How do people provide their add-ons to customers, or to their internal users?

Tal: I’m not sure. If you look at the major web platforms of today, look at the social ones such as Facebook, third party integration, customisation of that, that can be taken to the nth degree. I think a lot of the time, for organisations to deploy customisation on the web where you don’t even have to go to the PC and configure a customisation for a user, for that to be available centrally on-line, and to know that when you move to a different computer for example, all those extensions and all that configuration, all that good stuff, goes along with you, it’s actually an advantage. You can do a lot of the things around customisation and configuration of the product on line, that would be harder to do sometimes on a desktop.

Steve: There are a limited number of DWG object types that are currently supported. I assume you’ll be adding to them over time. What about 3D objects?

Tal: Butterfly supports all AutoCAD 2D objects that are supported by horizontal or vanilla AutoCAD at this time, so you can view that, and you can have drawings from vertical versions with proxy graphics that will be displayed. So for 2D I think you have probably full and complete support for 2D data types. Before we move on to 3D, we want to make sure we nail the experience just right. You say you have a list of things you’d like to see us improve in 2D, and we’d like to be able to go and work on as many of our users’ lists for 2D before we head on over to 3D, because at the end of the day it’s all about nailing the experience just right rather than just adding a lot of the functionality to the product which is not fully mature and fully complete, and as a result of that, not add value to our customers.

Steve: I guess people may be concerned with losing data because you’re not supporting the full set of object types. Is round-tripping fully supported?

Tal: I can rest your mind at ease on that point. When you upload an AutoCAD drawing to Butterfly, that file is not converted, and resides in fully original form on the server. And when you make changes, for example on line, those changes are then injected into the drawing using authentic genuine DWG technology, so when you download that file back to your computer, you maintain full integrity of it. There’s no conversion process, no data loss, and you get a very strong experience on that front. So users should not have any concerns at all concerning that.

Steve: So round-tripping works with everything; is that true? For example, you may have a Civil 3D DWG that you modify using Butterfly. Does the drawing return fully intact, including the Civil 3D objects with all their intelligence?

Tal: That Civil 3D object is intact in the same way that if you take that Civil 3D drawing, and open it in AutoCAD LT and manipulate geometry. All your Civil 3D objects remain intact. It’s the exact same experience. That data is not modified, it’s not converted, it’s not lost. While Butterfly may not be able to edit the contents of those Civil 3D objects in the same way that AutoCAD LT or AutoCAD vanilla does not enable you to, it still maintains full data integrity and there is no data loss.

This post concludes this interview series. Links to part 1 and part 2.

Autodesk Cloud interview May 2010 – Part 2

Steve: Autodesk is currently giving away these Cloud-based services, Butterfly for example. Presumably you’re not going to keep doing that for ever. Are you going to start charging for these services eventually?

Guri: Again, you’re pushing us to talk about future. Currently, for as long as this is in a Labs environment, we’re encouraging users to use it and we’re giving it free in the Labs environment and we’re not putting any limits on it during the Labs experiment. Once we make it a commercial product we may change that.

Steve: I put a poll on my blog asking readers what they thought about CAD on the Cloud, and most of them are either concerned or frightened. Solidworks users are in revolt about what they see as being forced onto the Cloud. Why do you think there is this fear or apprehension of CAD on the Cloud?

Guri: I’m not sure. I’m curious myself about this type of reaction. Maybe it’s fear of the unknown, it’s a new environment, maybe there is some fear about security of documents while they are in the Cloud, it’s just “it’s a new thing”. We believe the approaches we are taking in providing a complementary product to the desktop environment which takes advantage of the latest and greatest web technology and enables those advantages to the user actually will make them feel more at ease. We’re not changing their normal CAD tools, we’re adding to them by enhancing them to take advantage of the capability of infinite storage and infinite CPU that the Cloud brings to them. So in a way, it’s a mixed environment. It’s probably easier to think about moving from desktop only to a mix of desktop and Cloud rather than a step-function where you move entirely to the Cloud.

Tal: Yeah, and when moving to a new platform, you probably know, even when moving to PCs say 10 or 15 years ago, there was a lot of apprehension and whenever you move to a new platform (and rightly so), you’re going to see a lot of concerns being raised by users and it’s our responsibility to provide our users with a very gradual and easy migration path which enables them to pick which components, which things, which processes they would like to do on the desktop and which make more sense to be able to do on the web.

Guri: Steve, you’ve been around CAD for many, many years. You know that CAD users usually worry about a few things. They worry about their documents and drawings. They have a lot of investment in archives of documents and drawings, they want to know that whatever changes happen in the future in the world, will enable them to keep using those drawings as usual. The other thing they worry about is their own training and experience, the way they work every day. They have a lot of habits and practices that they develop over the years and they want to know that they don’t have to retrain themselves or any other new users into new ways of doing things. And what we’re proposing is addressing both. You can use your drawings, this is still DWG, these are still AutoCAD documents, you don’t have to change, every drawing that you have that is created now or 10 years ago is still going to be useful.

So that’s one comment and the other is you can still use AutoCAD; that’s your tool of choice and whatever you do in the Cloud we purposely keep very simple so learning it and training it is really a very, very simple task.

Steve: I think you raised a valid point there about people being afraid of “what’s going to happen to my drawings”; people are concerned that if they move completely to the Cloud then they’re handing over control; they no longer have control of their documents. Do you think that’s a valid concern?

Guri: Well, I think that’s a concern, and people who have it will probably have it for a long time. What we want to do is let them choose how to deal with that. So we are not forcing anything here; we’re letting them keep their drawings on the desktop if they want, we’re letting them upload to the Cloud if they want to take advantage of it, so it’s entirely up to the user what to do. What we’re trying to do is show them that if they want to move to the Cloud, the advantages are the same advantages as photography sites such as Picasa. If you upload your family photos to the Cloud, somebody has done the backup for you; somebody has put security on it that is probably even better than you can do yourself, you can share it easily with others, provide access to your family without sending attachments and stuff like that. So there is a lot of advantages. We’re telling users it’s completely up to you; there are advantages that come along with moving stuff to the Cloud, if you’re not confident with that, that’s perfectly fine, stay on the desktop. So we’re letting the user do it at their own pace.

Steve: Can I share some of my experiences with using Butterfly? Perhaps I was using it wrong; I was trying to draw with it! As you’ve indicated, that’s maybe not what it’s really there for. I found that it wouldn’t open some drawings that I tried to upload. The display was a bit fuzzy, particularly on text, particularly when it was selected. A big issue I have with it is that I have two great big screens here in front of me and because Butterfly is confined to a browser window, it’s only using one rectangle. With AutoCAD, I can grab various bits and pieces of the interface and drag them over to the second screen, so I find Butterfly rather limiting. There also seems to be a lot of wasted space in the Butterfly environment. I can get AutoCAD to use about 91% of the screen space for drawing area; with Butterfly it was about 53%. So you’re working in a tiny little window. People pay lots of money for these big screens, and because you’re working within a browser, and because within that there’s a lot of wasted space, a lot of that investment is wasted. I’ll stop there before I confuse you all, but I have a great big list here of stuff that I found difficult to live with.

Tal: I’d love to have that list. We get a lot of requests from users, and a lot of different things bother different people. You know, we get a lot of requests that are the complete opposite, like I have a laptop with a small screen so I want to be able to optimise, I use Butterfly on the go, I need to have Butterfly optimised for that kind of resolution. But if you have a list of things we’d actually love to see it, and a lot of the times when you’re connected to a product designer on our team and have you talk to him and really go through the things that bother you, because at the end of the day it’s really our job to be able to do a good job and provide the tools which a user loves and delights users, and be able to focus on the things that are important to the majority of users and really do a good job of nailing those experiences. So if you have a list we’d love to have it and engage with you on it and see what makes sense for us to put in there and what we feel is not the highest priority for us feature-wise right now.

Steve: I’m sure you’re working on printing/plotting, because it’s pretty terrible at the moment. I’m sure I don’t need to tell you that’s a priority.

Tal: Basically it does not plot right now. It enables you to print your screen, but not plot. I wouldn’t say it’s bad plotting, it does not plot right now. If you want a quick printout of whatever you have on screen, it will do the job. Plotting is one feature that is definitely very interesting to us, it’s important to a lot of users, and we’re definitely looking into it, and providing hopefully in the future a better experience revolving around that.

Steve: And the limitation of selecting more than 30 objects; is that going to go away at some stage?

Tal: I believe you’re going to be seeing a lot of improvements in that area relatively shortly.

Links to part 1 and part 3.

Autodesk Cloud interview May 2010 – Part 1

On 26 May 2010, I had the opportunity to ask Autodesk some questions about the Cloud in general and what was then Project Butterfly (now AutoCAD WS) in particular. The Autodesk people were:

  • Guri Stark,Vice President, AutoCAD & Platform Products
  • Tal Weiss, R&D Center Manager (Israel)
  • Noah Cole, Corporate Media Relations

The interview was conducted by phone conference with no prior notice of the questions. Here is the first part of the interview, which I will be posting in three sections.

Steve: Guri, are you responsible for all of Autodesk’s Cloud-based offerings?

Guri: Tal and I are responsible for Butterfly, that’s the only Cloud-based offering that we are responsible for.

Noah: Steve, you can put the cloud-based offerings into three categories, those that are related to current products and therefore come out of the same organisations and divisions that those products come out of. So Butterfly which is related to AutoCAD so it’s coming out of the AutoCAD group. Similarly what you’d see happening with manufacturing and those projects. You also have the more emerging Cloud solutions like Dragonfly was (that’s now Homestyler) that’s coming out of Labs. So you see projects coming out of either the divisions if it’s related to product or the Labs group if it’s more forward-looking.

Steve: Can you give me a one-sentence summary of each of the Cloud-based offerings and what market it’s intended to fill?

Guri: Butterfly is one we’ll talk about in more detail in a minute. One we just launched as a product is Autodesk Homestyler (previously Project Dragonfly). It’s a SaaS-based offering done completely in a browser, targeting the home improvement market. It’s free to the end user so users who want to redecorate or remodel their kitchen or their living room can access this product, do a layout, place in it different types of furniture from libraries, and see how physical spaces fit together in this 2D and 3D type of product which is a completely SaaS-based offering.

The end user for this is not traditionally an engineer or CAD user at all, it’s more like the person at home; a typical user would be a 35-year-old lady who is interested in home decoration. The libraries in the product are either generic libraries or branded vendor-provided libraries from a variety of vendors in this space. That’s another type of product using SaaS technology that enabled us to get into a market that we’re currently not in.

There are other projects going on under the umbrella of taking existing products and trying to run them in a Cloud environment, and measuring the performance that they give us. All of them are experimental; some of them are on Labs already with some limitations of distance. So if you are in the California area you can try and use, mostly for trial and evaluation, some of our products such as AutoCAD or Inventor even, in this type of environment. You don’t need to install anything because the application runs in the Cloud; you have full access to the full application for a trial perspective.So there are different approaches to the Cloud. One approach is starting from scratch, developing something like Butterfly or Homestyler from scratch in the cloud to try and target a new market possibly. Another attempt is to take an existing application and try and run them centrally in the Cloud and see whatever performance it gets. Currently our intent is to use it for product evaluation.

Steve: The existing products running in the Cloud in the geographically restricted trial, is it just AutoCAD and Inventor?

Noah: AutoCAD, Inventor and Maya are the only ones currently running. There are also two recent technology previews happening in Manufacturing for Centaur and Cumulus which are different, but that involves Inventor and Moldflow.

Steve: With my experience with Project Butterfly, I agree that as a collaboration and review and viewing/markup tool it’s excellent, but it seems to me that it’s also being promoted as a drafting tool; that people will actually draw with it. It doesn’t seem so strong to me, for that. What is Project Butterfly now, and what is it going to end up being?

Guri: Steve, we’re not promoting this as a drafting tool, we say that the real authoring tool to create drawings is AutoCAD on the desktop. This enables you to upload a drawing that was created using AutoCAD to the Cloud, and in addition to review it and annotate it and share it; you can also make changes to it, to edit it. So what we’re providing in Butterfly is editing tools, not really drawing creation tools. I can tell you we have a free product called Autodesk Design Review, this product has only viewing and annotation capabilities. What a lot of users there are asking for is some basic editing tools where they want to make some local changes, and that’s what we are providing. The editing tools are intended for users that are not necessarily AutoCAD users, we keep them simple for that purpose.

Steve: So it’s not intended to be a drafting tool and you never intend it to actually become one in the end; is that correct?

Guri: I’d rather not comment on future direction. I can tell you right now that the positioning of the product is as a web accompaniment to AutoCAD, in a way similar to Microsoft’s Office Online in the most recent Office application is doing, in which an author on the desktop using Microsoft Word can upload it to the Cloud, view it, share it, edit it. So we are enabling editing of documents in the Cloud.

Tal: Just to add to that, we have different platforms, the desktop and the web. Each platform does certain things very well. So authoring, for example, on the desktop is something that is great, it’s mature and you can do a lot of amazing stuff there. What we want to focus on in building a tool for the web is leverage what the web can do for our users. Stuff like being able to access from anywhere, design timeline, collaboration, sharing; really hitting all those sweet spots instead of trying to imitate what’s already up there on the desktop and is working well. That’s why you see the different focus on the different platforms trying to do that thing it can do best.

Links to part 2 and part 3.

All major Autodesk products on the Cloud by 2014?

As reported by multiple on-line news outlets, Autodesk just announced that it is increasing its research and development budget (having slashed it last year), and increasing the percentage of that budget on the Cloud. Carl Bass:

When there are technology transitions in place, you better be more mindful of that, or you become roadkill.

That’s fair enough. Autodesk would be stupid to ignore the Cloud, and needs to bet at least some of its cash on anything that stands a significant chance of being important. This quote from Autodesk spokesman Paul Sullivan gets more specific:

We are devoting a larger percentage of our R&D budget to cloud computing, with a significant portion of our new product investments going toward products that are cloud-enabled. We expect that all of our major products will be available in the cloud within the next three years.

Now “available” can mean various things. The restricted trial of Cloud-based AutoCAD, Inventor and other products is already year-old news, but that fits the “available” bill. So does a situation where the product is exclusively available on the Cloud and you can no longer buy standalone software. Between those two extremes, there are a variety of possible definitions of “available”. So we’re not that much wiser as a result of that statement.

However, one thing is clear. Autodesk is spending up big on making this Cloud thing happen, so traditional software is going to suffer from a comparitive lack of investment. Autodesk customers, you’re the source of all that cash. How do you feel about subsidising the move of your software tools to the Cloud?

Cloud concerns – terms and conditions

I just used Autodesk Cloud Documents for the first time, and was asked to confirm my acceptance of the Terms of Service. Fair enough. But just what is in those terms, and what do they mean to you if you are dubious about using the Cloud? Will you be reassured by what you find there? Maybe not. Here are a few clauses that might make you go hmmm…

The terms applicable to a particular service may vary.

Translation: Autodesk can move the goalposts.

Autodesk has the right (but not the obligation) to monitor Your usage of the Service to verify compliance with these Terms.

Translation: Autodesk can keep its eye on you.

You acknowledge and agree that: (a) You will evaluate and bear all risks associated with Your Content; (b) under no circumstances will Autodesk Parties be liable in any way for Your Content, including, but not limited to, any loss or damage, any errors or omissions, or any unauthorized access or use; and (c) You (and not Autodesk) are responsible for backing up and protecting the security and confidentiality of Your Content.

Translation: whatever happens, it’s your problem, not Autodesk’s.

Third Party Content and services may be made available to You, directly or indirectly, through the Service (including Content shared by other users of the Service, through Forums or by any other means). In some cases, such Content and services may appear to be a feature or function within, or extension of, the Services or the Autodesk Software. Accessing such Content or services may cause Your Computer, without additional notice, to communicate with a third-party website … for example, for purposes of providing You with additional information, features and functionality.

Translation: Autodesk and others can use the service to advertise to you.

Autodesk reserves the right to delete inactive accounts or purge related Content (and all backups thereof), without further notice and Autodesk Parties shall have no responsibility or liability for deletion or any failure to store Your Content.

Translation: don’t just leave your stuff up in the clouds and expect it to still be there a few years later.

You acknowledge that Autodesk may use third-party service providers in connection with the Services, including without limitation the use of cloud computing service providers which may transmit, maintain and store Your data using third-party computers and equipment in locations around the globe.

Translation: it’s not just Autodesk here, there is a chain of responsibilities and vulnerabilities.

THE SERVICE OFFERING IS PROVIDED “AS IS” AND “AS AVAILABLE.” AUTODESK PARTIES MAKE NO, AND HEREBY DISCLAIM ALL, REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF ANY KIND…

YOUR USE OF THE SERVICE OFFERING IS AT YOUR OWN DISCRETION AND RISK.

AUTODESK PARTIES DO NOT WARRANT THAT THE SERVICE OFFERING WILL PERFORM IN ANY PARTICULAR MANNER AND HEREBY DISCLAIM LIABILITY FOR NEGLIGENCE AND GROSS NEGLIGENCE.

Translation: Autodesk lawyers LOVE SHOUTING. Whatever happens, including gross negligence on Autodesk’s part, it’s still all your fault and you’re severely out of luck.

…for all Service Offerings accessed as part of Subscription, these Terms and Your access to the Services will terminate when Your Subscription (and the Subscription Program Terms applicable to Your Subscription) terminates or expires.

Translation: here’s a further disincentive to ever dropping out of Subscription once you’re on it.

It is Your responsibility to retain copies of Your Content. Upon termination Autodesk shall have the right to immediately delete, without notice, Your Content, if any, and all backups thereof, and Autodesk Parties shall not be liable for any loss or damage which may be incurred by You or any third parties as a result of such deletion.

Translation: don’t rely on the Cloud alone.

Autodesk reserves the right, from time to time in its sole discretion, to (a) modify or release subsequent versions of the Service, (b) impose license keys or other means of controlling access to the Service, (c) limit or suspend Your access to the Service, and (d) change, suspend or discontinue the Service at any time.

Translation: Autodesk can do pretty much whatever it likes, including killing the whole thing.

I don’t think any of this means Autodesk is evil. Looked at from the point of view of a corporation that needs to cover its backside and reduce risks to itself, it’s quite understandable. Much of it is just very sensible advice. You can expect similar conditions from other companies providing Cloud services. But what if you’re not happy with using a Cloud service that has such conditions attached? Well, you can use it anyway and keep your fingers crossed, or you stay away from it altogether.

How do you see this? Assuming you were happy with everything else about the Cloud, would clauses like those above be a dealbreaker?

Edit: this post is also being discussed on the Dezignstuff blog.

Note: the above clauses are Autodesk copyright, reproduced here under fair use (comment and criticism).

Autodesk Cloud – don’t panic, business as usual

Autodesk recently made a big announcement about its Cloud initiatives, and reactions have been all over the place. Some people can barely contain their breathless excitement while others are outraged to the point of passing out the pitchforks. Why? It’s pretty much business as usual.

It’s nothing like Dassault’s disastrous we’re-moving-you-to-the-Cloud FUD campaign against its own product, SolidWorks. There’s no hint here of AutoCAD (real AutoCAD, I mean, not “AutoCAD” WS) being moved to the Cloud, or anything as radical as that. (Yes, I know there’s a limited experiment along those lines but that’s nothing to do with this announcement). It’s just a collection of relatively minor changes to Autodesk’s existing on-line services, collected together to make a newsworthy press release.

(As an aside, I must say this was a much more worthwhile announcement than the ridiculously over-hyped DE8.16N thing. So I was supposed to get excited about a routine upgrade of a product I have already been using for months, on an OS I don’t use, when the upgraded product is still half-baked just like the first underwhelming effort? Fortunately, I didn’t get sucked in by the pre-announcement build-up so I wasn’t disappointed, just amused when the truth was revealed. Autodesk PR, please don’t cry wolf so often; keep the hype in reserve for the hypeworthy stuff.)

Back to the Cloud thing, and putting aside hype and horror, here’s the stuff that has just happened:

  • Autodesk Cloud documents lets anybody store up to 1 GB documents on-line, or 3 GB if you’re a Subscription customer. This isn’t new, but until recently it was an Autodesk Labs project called Nitrous. The infrastructure is provided via Amazon and Citrix.
  • AutoCAD WS has been updated to integrate its storage with Autodesk Cloud documents. Remember, WS isn’t anything like real AutoCAD, but rather a limited on-line DWG editing tool. There’s a WS iPhone app, but that’s not new.
  • There’s an Autodesk Design Review iPhone app for reviewing DWF files you’ve stored in Autodesk Cloud. It won’t do DWG; use WS for that.
  • There are several cloud-based services that are available “free” to Subscription-paying users of a small subset of Autodesk software, mostly Revit and Inventor-based suites. They are: 
    • Inventor Optimization
    • Cloud Rendering
    • Green Building Studio
    • Conceptual Energy Analysis
    • Buzzsaw (now bundled with Vault Subscription)

    AutoCAD users need not apply for any of these services.

So some of Autodesk’s on-line services are now being provided only to Subscription customers, and one is offered in improved form for Subscription customers. There are two obvious reasons for this: tie-in and revenue.

First, Autodesk wants its customers tied to the Subscription gravy train, if you’ll excuse a fairly awful mix of metaphors. Offering Subscription benefits like this is preferable to some of the much less pleasant arm-twisting that has been happening recently (e.g. trebling upgrade prices). Is it too much to hope that Autodesk has learned that offering carrots to its customers is a better strategy than threatening them with sticks?

Second, Autodesk needs to start making money out of this stuff somehow. For some years, it has spent several fortunes on buying and developing on-line services and then given them away for nothing, usually as Labs projects. This obviously can’t go on for ever, but just slapping a charge on these services wasn’t going to fly. Bundling Cloud services up with Subscription is a way of easing people into paying for them, and this is something I expect to be expanded in future, for example with AutoCAD WS. Once that’s been established for a few years, it wouldn’t surprise me to then see Subscription for at least some of the services split off, so you’re paying for Cloud services explicitly. By then, enough customers may consider them to be worth paying for and they may therefore survive beyond the short term.

Will it work? I’m not sure. Time will tell which of these services will thrive and which will die, and such uncertainty is one of the many reasons real-world customers aren’t excited about getting their heads in the Cloud. I don’t intend to make use of these services (I’m not even allowed to), so I’m not too bothered what happens to them. Like the vast majority of Autodesk customers, I will just carry on using conventional software in that old-fashioned 20th century way that just happens to work very well. Autodesk will go on providing its software in that way, because that’s what most customers will want for at least a while yet, and Autodesk can’t survive on wisps of Cloudy revenue.

Move along, people, nothing to see here.

AutoCAD 2012 – Autodesk adds an uninstallation analgesic

One of the more painful aspects of dealing with installations of recent releases of AutoCAD and related products is that although you might run a single setup routine to install what you think is a single application, the end result is a mass of different components being installed. Each of these components is considered a separate program by Windows, and needs uninstalling separately. Frankly, this is manifestly antisocial behaviour.

I have complained to Autodesk about this ever since it started happening, but the number of sub-installations has been getting greater rather than smaller. Now Autodesk has provided an uninstallation tool, which you can find here. If you download and run psebuninstalltool.exe, you will be provided with a list of applications to uninstall.

This is a move in the right direction, but it’s still far from ideal. You still have to choose which applications to install and which to leave alone because they’re in use by some other application, and because of the possible complexities you’re not likely to know. Get it wrong and you can break other applications in a way that’s not immediately obvious. Also, it uninstalls English language products only and is provided “as-is” as an unsupported tool.

This is a welcome kludge to help with a problem that shouldn’t exist. Users simply shouldn’t have to deal with this nonsense. If you install one application, you should be able to just uninstall one application and it should be gone, without breaking anything else. Autodesk, thanks for this interim assistance, but I look forward to the problem being removed in future releases, rather than partially patched over.

Installation tip – save time and space

If you download AutoCAD or other Autodesk products from either the trial or Subscription sites, the executable you get (e.g. AutoCAD_2012_English_Win_32bit.exe) is actually a self-extracting archive rather than a real installer. When you run it, you are prompted for a destination folder, with a default location such as this:

C:\Autodesk\AutoCAD_2012_English_Win_32bit

The actual installer (setup.exe) and all of the files it needs are then unzipped and placed in a folder structure in that location. When the extraction is finished, the self-extracting executable automatically runs setup.exe and the installation proper can begin. Once the installation is complete, the extracted files are left in place.

You can take advantage of this simple knowledge in various ways:

  • Sometimes, you may you need to run the installer more than once on the same PC. For example, you might need to uninstall/reinstall AutoCAD, or you might be a CAD Manager who installs AutoCAD for on your own PC and later creates a deployment for the other users. Or you might start installing AutoCAD, cancel it for whatever reason, then come back to it later. If so, don’t just run the downloaded executable again. Instead, locate the actual setup.exe installer that has been left behind and run that instead. That cuts out the extraction step and saves time.
  • If you’re going to do standalone installs on several PCs rather than making a deployment, don’t go through the extraction process again and again. Instead, do it once and then copy the extracted folder to a location that can be used from other PCs. This might be a USB drive or DVD, which you can store safely for later reinstalls. If you are going to install to the other PCs from a network drive, during the first install you can directly specify that as the destination folder and cut out the manual file copying step.
  • If you think it’s unlikely you’re going to need the extracted files again, you can delete or move them and recover the space. If you download a product and install it, you end up with three copies of the product files using up your space; the self-extractor, the extracted files and the installed product itself. It probably doesn’t all need to be on your C: drive. Although bulk hard disk space is plentiful and cheap, it’s becoming more common to use a small high-speed drive or SSD as the OS/program drive drive, and you might have a significant portion of it given over to a bunch of files you don’t need. Because Autodesk products are increasingly (and sometimes completely pointlessly) bloated, you might be surprised at how much space you can recover.
    However, as Chris Cowgill has pointed out, you may need to have the “media” available when you install Updates, etc. Keeping a copy of the extracted files on a DVD or USB key should do the trick if you’re hard up for hard disk space.

Note that this applies to the Windows downloads only; I know nothing about the mechanics of Autodesk’s Mac installation downloads.

3DConnexion device support in AutoCAD

Do you have a 3DConnexion device (3D ‘mouse’) and use it in AutoCAD or AutoCAD-based products? What do you think of the way it works in the most recent releases of AutoCAD?

From AutoCAD 2011 on, Autodesk provided built-in support for these devices. Has that made things better or worse than in earlier releases? If you’re having problems, exactly what are they and how does it affect your ability to work with AutoCAD in 3D? Is the 2012 support any better than 2011? How does AutoCAD’s support for these devices compare with that of other products?

AutoCAD 2012 – Autoloader mechanism for plug-ins

One of the less obvious features introduced by AutoCAD 2012 is the Autoloader mechanism that has been provided to make installation of plug-ins (current standard Autodeskspeak for add-ons, apps, utilities, routines, etc.) easier for both developers and users. It may not be immediately obvious, but it’s a useful and important addition.

This mechanism has nothing to do with the AppLoad command, the Startup Suite, acad*.lsp, the (autoload) function or anything else that existed in earlier releases. This is completely new, it has not replaced or broken any of the existing loading mechanisms, and is, in short, A Good Thing. Developers don’t have to use it, but those who do, and their customers, will have certain advantages. I have used it for the ClassicArray loading mechanism, and I expect to see it used by more and more plug-ins over time. It works fine with all of the usual AutoCAD add-on APIs, including LISP.

User perspective
As a user, what this means is that for AutoCAD and related applications from 2012 on, there is a standard loading mechanism for plug-ins. The installation should be straightforward, with no multi-step processes to go through for different AutoCAD variants and releases. The result of the installation should automatically present itself in a standard way, with a short-lived welcome bubble, an extra panel in the new Plug-ins Ribbon tab, plus any other interface additions the developer wants to provide. If you subsequently install another AutoCAD variant or release, the plug-in will automatically appear in that variant with no further user action required, as long as that AutoCAD variant is supported by the plug-in.

Developer perspective
What this means for me as a developer is that I have much less to worry about in terms of installation. All that needs to be done to make the loading happen is for a folder full of ‘stuff’ to be copied into a certain location. (There are actually two possible locations, but more on that later).

In Betas of ClassicArray, I just provided the folder, plus instructions that asked the user to copy that folder into place. I could have simplified that further by providing batch files that did the copying. In the end, I created setup executables using the free Inno Setup utility, but that was a much easier job that it would have been if this Autoloader mechanism didn’t exist. I didn’t have to worry about discovering what releases were installed, deciphering Registry entries, creating user installaton scripts, or issuing instructions to users to edit files or mess with the AppLoad command. I don’t have to worry about what happens if the user subsequently installs another AutoCAD variant.

Of course, for developers who support releases prior to 2012, there is no less work to do than before, and some time needs to be spent to learn and implement the new mechanism. In the case of ClassicArray, that was not an issue because it’s only needed and supported in 2012. I expect this is one of those problems that will resolve itself over time as developers adopt the new mechanism.

The bundle folder
So what is this ‘stuff’ that needs copying into place? It’s called a bundle folder. It’s just a folder with a name that ends in .bundle (e.g. ClassicArray.bundle), and it typically contains the usual files needed to run your add-in, often tidied up within other folders. The only new thing that it needs to contain is a file called PackageContents.xml. That XML file is the key to the Autoloader mechanism. AutoCAD finds the file, reads it, and acts accordingly in terms of version support, loading program files, partial cuix files and so on.

Bundle folder location
So where does this folder with its XML file have to go? There are two possible locations. If you want the plug-in to be available to all users on the computer, you place it in the Autodesk\ApplicationPlugins folder underneath the system’s ProgramFiles folder. For example, ClassicArray usually gets put here:

C:\Program Files\Autodesk\ApplicationPlugins\ClassicArray.bundle

If you only want the plug-in to be loaded for the current user, it goes in the Autodesk\ApplicationPlugins folder underneath the system’s AppData folder instead, for example:

C:\Documents and Settings\[login]\Application Data\Roaming\Autodesk\ApplicationPlugins\ClassicArray.bundle

in XP or

C:\Users\[login]\AppData\Roaming\Autodesk\ApplicationPlugins\ClassicArray.bundle

in Windows 7.

Describing the contents of that all-important XML file is beyond the scope of this post, but I may do a follow-up post if there is enough interest. In either case, the reference material is available in the AutoCAD Help, under Help > Customization Guide > Introduction to Programming Interfaces > Install and Uninstall Plug-In Applications > PackageContents.xml Format.

AutoCAD 2012 – Putting things back to “normal”

Edit: If you’re running a more recent release of AutoCAD, have a look at the post AutoCAD 2017 – Putting things back to “normal” instead.

The most popular post on this blog, in terms of both hits and comments, is AutoCAD 2009 – Putting things back to “normal”. This is followed by AutoCAD 2010 – Putting things back to “normal”, with AutoCAD 2011 – Putting things back to “normal” not too far behind. As it seems many people find these posts useful, here’s an updated version for the latest release. Much of this post is based on older versions, but there are many additions and differences in this year’s “keep off my lawn” post.

One thing that’s regularly asked whenever a new AutoCAD release hits the streets is how to make it work like earlier releases. As I stated in my original post, I think you should give any new features a fighting chance before turning them off or ignoring them. But it’s entirely your choice. We should be grateful that in AutoCAD 2012 at least (unlike some Autodesk products), you do still have that choice. At least, you have a choice in most cases.

Let’s assume you’ve made the decision to put your environment back to AutoCAD 2008 or earlier; how do you do it? I’ve arranged these items in alphabetical order:

  • Aerial View. The DSVIEWER command appears to be gone, but it’s just hiding. It has been undefined. You can use REDEFINE DSVIEWER to turn it back on, or just enter .DSVIEWER (with a leading period). It may not work perfectly on all systems under all circumstances.
  • Array dialog box. The excellent new associative array features of AutoCAD 2012 have come at the cost of the Array dialog box. While you can use the Ribbon or the Properties palette to modify arrays, if you want to create one you have to go back to the future with a Release 14-style user interface. Using -Array doesn’t give you a dialog box, just the old-style command line. There’s nothing available in standard AutoCAD 2012 to give you a dialog box interface, which is why I created ClassicArray™. It also makes it easier to create non-associative arrays, if that’s what you prefer. This plug-in has the further fortunate side-effect of acting as a workaround for several of the new Array command’s various bugs, limitations and design issues.
    Edit: Applying SP1 to AutoCAD 2012 adds an ARRAYCLASSIC command that restores the previous dialog box. This does not provide access to any of the new features; you will still need ClassicArray for that.
  • Autocomplete. Old-timers may well find this feature useful, but if it’s getting in your way, turning it off is as simple as AUTOCOMPLETE OFF. There are a variety of settings you can selectively turn off individually if you prefer.
  • Blips. The BLIPMODE command has been undefined, but you can use REDEFINE BLIPMODE to turn it back on, or just enter .BLIPMODE (with a leading period).
  • Classic commands. If you prefer not to leave the various new palettes on screen all the time, old versions of various commands are still available: ClassicLayer, ClassicXref and ClassicImage. (Autodesk deprecated these commands in 2011 and 2012, which I think is a really bad idea). There is also a system variable LAYERDLGMODE, which when set to 0 will make the Layer command work in the old (and faster) modal way. If you use this setting, you can still access the new modeless layer palette with the LayerPalette command. Going back further, there are command-line methods of using these commands: -Layer, -Xref, XAttach, -Image and ImageAttach. For 2012, Autodesk has removed the Group command’s dialog box interface. If you want the dialog box, you now need to use the ClassicGroup command instead.
  • Crosshairs. Want 100% crosshairs? Many people do. As before, use the Options command’s Display tab and look towards the bottom right, or use the CURSORSIZE system variable.
  • Dashboard. The AutoCAD 2007/8 Dashboard is gone, but you can have a vertical Ribbon instead. If the Ribbon is not visible (it won’t be if you just selected the AutoCAD Classic workspace), enter Ribbon to bring it back. In the tab title row (the bar with the word Home in it), right-click and pick Undock. Now you can place and size your Dashboard-like thing as you see fit. As before, you can right-click on things to change the various settings. However, getting the contents exactly the way you want it usually involves using CUI, and that’s well outside the scope of this post.
  • Dynamic Input. If Dynamic Input slows you down, you can turn it off with the status bar toggle or F12. If you like the general idea but don’t like some parts of it, there are lots of options available in the Dynamic Input tab of the DSettings command to enable you to control it to a fine degree. You can also get at this by right-clicking the Dynamic Input status bar button and picking Settings… As an example of the sort of thing you might do in there, the default of using relative coordinates is difficult for long-termers to get used to. To turn it off, pick the Settings… button in the Pointer Input panel, pick Absolute coordinates, then OK twice. There are a whole range of DYNxxx system variables for controlling this stuff.
  • Graphic Background. Autodesk has half-listened to users’ pleas for a black background by giving you a nearly black one (RGB 33,40,48 rather than 0,0,0), in model space only. Many of you will want a real black background to provide better contrast. To do this, invoke the Options command (right-click on the drawing area and pick Options… or just enter OP), then pick the Display tab. Don’t be tempted to choose Color Scheme and set it to Dark, because that just changes the appearance of various user interface elements. Instead, pick the Colors… button. This will put you in the Drawing Window Colors dialog box. On the left, choose a context you want to change (e.g. 2D model space), choose the appropriate background element (e.g. Uniform background) and choose the particular shade that takes your fancy. There is a Restore Classic Colors button, but that only takes you back to AutoCAD 2008 with its black model and white paper space. If you want a black paper space background too, you’ll have to pick the Sheet / layout context and specify that individually. You may wish to put the Command line > Command line history background setting to white, too. When you’re done, pick Apply & Close, then OK.
  • Grid. I generally prefer the new line-based grid. If you use isometric snap and grid, you will find that AutoCAD 2012’s line-based isometric grid is still as broken as it was in earlier releases, so you’ll need to use dots. If that applies to you or you just don’t like the lines, right-click on the Grid status button and pick Settings…, which will take you into the Drafting Settings dialog box, which you can also get at with the DSettings command, or DS for short. In the Snap and Grid tab, the grid is controlled by the options on the right. If you want your dots back, turn on the toggles in the Grid style section. This can also be done using the GRIDSTYLE system variable. If you don’t like the fact that the grid is now on by default in new drawings, this is set on a drawing-by-drawing basis and is therefore controlled by your template drawings. If you use AutoCAD’s supplied templates, you will need to open them individually and turn off the grid in each one.
  • Hatch dialog box. If you want the Ribbon on but prefer the old Hatch dialog box, set HPDLGMODE to 1.
  • Hatch double-click. If you’re not using the new Ribbon-based hatch editing feature, you will probably want to invoke the HatchEdit command when you double-click on a hatch object. Doing this involves braving the CUI interface, but I have gone into step-by-step detail of that process here. In short, you need to drag and drop the Hatch Edit command from the bottom left CUI panel onto the double-click action for Hatch in the top left panel, replacing the default action (Properties).
  • Help. If you want your Help to work with adequate speed and reliability, or to work at all in some proxy server environments, you will want to turn off AutoCAD 2012’s online help. Go into Options > System, then look in the bottom right pane to turn off the Use online help toggle. Even with online help turned off, you’re stuck with the unfortunate new browser-based AutoCAD Exchange interface for your Help. There is no sign yet of Autodesk coming to the rescue with a set of CHM-based Help files as was done for AutoCAD 2011, which is a real shame. The VLIDE Help is still partially broken, because Autodesk doesn’t care about customers who use LISP for development. While you’re in Options, you may also wish to turn off AutoCAD’s insistence on firing up Internet Explorer, that is if you dislike IE or have security concerns.
  • Initial Setup. Don’t bother looking for this, it has been removed from the product. Can’t say I’m heartbroken about that.
  • Line Smoothing. If you don’t like the anti-aliasing feature that attempts to make your graphics look less jaggy, this is controlled by the LINESMOOTHING system variable. It’s also available via the GRAPHICSCONFIG command or Options > System > Graphics Performance.
  • NavBar. If you like the new NavBar feature as much as I do, you’ll want to turn it off. You can close it easily using the little X in its top left corner. Alternatively, control it with the NAVBARDISPLAY system variable (0 for off, 1 for on)
  • Pull-down Menus. Enter MENUBAR 1 to turn pull-down menus on. To turn them off again, enter MENUBAR 0.
  • Ribbon. You can close the Ribbon with the RibbonClose command. If you ever want to turn it back on, enter Ribbon.
  • Screen menu. The SCREENMENU command has been undefined, but you can use REDEFINE SCREENMENU to turn it back on, or just enter .SCREENMENU (with a leading period). However, you can’t access the screen menu section in CUI any more, so if you want to maintain your screen menu you will need to do it in an earlier release.
  • Selection Cycling. Depending on your preference and/or system graphic performance, you may wish to turn off selection cycling (set SELECTIONCYCLING to 0), or at least the list that appears when selecting objects that lie on top of each other (set SELECTIONCYCLING to 1).
  • Selection Preview. This feature annoys some users, adding as it does an unfortunate degree of stickiness and working inaccurately when Snap is in use. This is controlled in the Selection tab of the Options command. Turn off the toggles in the Selection preview panel on the left (these control the SELECTIONPREVIEW system variable). If you dislike the coloured boxes you get while doing a Window or Crossing, pick the Visual Effect Settings… button and turn off the Indicate selection area toggle. This controls the SELECTIONAREA system variable.
  • Snap. AutoCAD 2012’s snap no longer works while there is no command active. There is no setting available to turn this feature off. If you want to move your cursor around and see the cursor snapping to precise locations to see if objects line up (e.g. in schematic diagrams), you will need to invoke a command first (e.g. L [Enter]) and ignore the command as you’re moving around on screen.
    Edit: Applying SP1 to AutoCAD 2012 adds new system variable (SNAPGRIDLEGACY) that allows you to have your snap active at the command prompt.
  • Startup performance. You may have noticed that AutoCAD 2012’s Ribbon switching performance is finally as it should have been from the start; practically instantaneous. You may also have noticed that when you start AutoCAD, the cursor is sticky for a while after the Command prompt is available. These two items are not unrelated; AutoCAD is loading Ribbon components in the background. If you would prefer this not to happen, set the RIBBONBGLOAD system variable to 0.
  • Status bar. Right-click on a status bar button, turn off Use Icons and your old text-based status bar buttons will return. If you have no use for some of the new status bar toggles, right-click on one, pick Display, then turn off what you don’t need.
  • Toolbars. In AutoCAD 2009, you could turn individual toolbars on and off by accessing a menu obtained by right-clicking on the QAT. Autodesk somewhat vindictively removed that option in 2010, and it’s still gone in 2012. That toolbar-toggling menu is still available if you right-click in an unused docked toolbar area, but if you have no toolbars visible there will be no such area available. What to do? Turn on one toolbar at the Command prompt, then you will be able to access the menu by right-clicking on the blank area to the right of it. The following command sequence will do it:
    _.-TOOLBAR ACAD.Standard _Top 0,0
    Paste this into AutoCAD’s command line area and the Standard toolbar will be turned on above your drawing area. This will leave a grey area to the right that you can right-click into. The other toolbars will be in sub-menus under that, with the main set of default ones in the AutoCAD section. Note that this will only work if you have the acad.cuix file loaded (or partially loaded). This is the case in vanilla AutoCAD and some verticals, but it may not be the case in other verticals. As I don’t have access to such verticals, I’m afraid I can’t offer much advice here.
    If you’re like me, you may well discover that this is moot because AutoCAD 2012 automatically turns on a full set of toolbars, in addition to the Ribbon, the second time you run AutoCAD. This bug occurs when there’s another release already installed and you don’t use Migration. It’s easily fixed (that is if you want to fix it) by switching to the workspace of your choice (see below).
  • Tooltips. Excessively intrusive and oversized tooltips were a “feature” of AutoCAD 2009’s revamped UI design, and we’ve been plagued with them ever since. I’m glad to see that many of them have had their verbosity somewhat curtailed in 2012, but they still annoy the heck out of me, particularly by obscuring what I’m trying to see in dialog boxes. To kill them with fire, see Options > Display and start turning off toggles about half way down the left side.
  • Trace. The TRACE command has been undefined, but you can use REDEFINE TRACE to turn it back on, or just enter .TRACE (with a leading period).
  • UCS Icon. Don’t like the new simplified UCS icon? Sorry! While you can use the UCSIcon command’s Properties option to change the appearance of the icon in various ways, there’s nothing to restore the UCS Icon’s appearance from previous releases with its little arrows pointing the way. This information isn’t totally useless, because at least it will save you the time and effort involved in finding this out for yourself.
  • Vertical variants’ AutoCAD profile. Apparently, some AutoCAD 2012 vertical variants don’t have a shortcut for running them as AutoCAD. If you want to make one, first check in Options > Profiles to see if there is a profile called “AutoCAD” or similar. If not, you will need to create one, reset it, and hope for the best. Sorry, I don’t have all the variants to check. Now, make a copy of your AutoCAD variant’s desktop shortcut and rename it as something like “AutoCAD 2012”. Then right-click on the copy and pick Properties. In the Target edit box, check to see if there is a /p switch followed by a profile name inside quotes. If there is, replace the existing profile name with “AutoCAD” or whatever the profile name is that you discovered or created in Options. If there isn’t a /p switch, add one. The end result should look something like this (there may be extra switches):
    "C:\Program Files\Autodesk\[product name]\acad.exe" /p "AutoCAD"
    Once you have ensured there’s a /p “AutoCAD” (or similar) on the end of the Target, pick OK. You should then be able to start your vertical variant as AutoCAD.
  • ViewCube. I like the ViewCube concept, and I think it’s a great piece of interface design. But not everybody agrees. It has caused performance issues and it’s not very useful for 2D users. If you want it gone, that’s a surprisingly difficult thing to find out about. The simplest way to remove it is by clicking the [-] button in the top left corner of the drawing area and tuening off the ViewCube toggle there. If you want more control, it’s handled using the Options command, in the 3D Modeling tab, in the bottom left corner. Turn off those toggles that don’t make sense for you. There is a related set of system variables called NAVVCUBExxx.
  • Workspace. In vanilla AutoCAD, you can restore much of the user interface by just switching workspaces. The main Workspace control is now located near the top left corner. If you have turned this off (right-click, Remove from Quick Access Toolbar) or if you just prefer working with interface elements in the same place year by year, there is another Workspace control in the bottom right corner. This is a little button that looks like a gearwheel. In either case, click on the Workspace control and pick the item called AutoCAD Classic. This will perform some of the steps described above, but not all of them, so I suggest you skim the whole lot to see what else you might want to do. If you’re using a vertical variant of AutoCAD 2012, this workspace may not be available, or it may only be available if you when using an “AutoCAD” profile (see above). If it’s not available at all, you’ll need to make your own classic workspace by manually setting up your interface the way you like it, then saving it as a Workspace using the Save Current As… option under one of the Workspace controls.
  • Xref fading. Don’t like your xrefs looking different? Use the Options command’s Display tab and look at the Xref display slider on the bottom right, or use the XDWGFADECTL system variable.
  • Zoom Animation. If you prefer your zooms to be instant rather than progressing from one view to another in an animated series of steps, you can turn off that feature using the VTOPTIONS command or the VTENABLE system variable.

If you have allowed AutoCAD to migrate your settings (I never do), some of the above will already be done for you, but by no means all of it. If past experience is anything to go by, the job done by Migration will probably be imperfect.

Once you’re happy with your new environment, I suggest you save your workspace under a name of your choosing (Save Current As… under a Workspace control), then export your profile in the Options command’s Profiles tab. Keep a safe copy of both your exported profile and your main CUIX file (acad.cuix by default), because that is where new workspaces are stored.

All of this advice is offered on an as-is, try-it-yourself-and see-what-happens basis. Unfortunately, I can’t check to see which parts of this post relate to AutoCAD for Mac (when the 2012 version arrives), AutoCAD LT (much of it will be the same), the various AutoCAD-based vertical variants (almost all of it should be the same). AutoCAD WS is, of course, nothing like real AutoCAD so none of this post will be relevant. Please comment to let me know if you find something you think I should modify or include.

Let me just end by saying that Autodesk generally does an excellent job of keeping long-term AutoCAD users happy by allowing them to keep working in the way that they prefer. There are exceptions, and this record has been damaged slightly by 2012, but conservative users are still better off with new releases of AutoCAD than they are with, say, Microsoft Word.

Is AutoCAD stability getting better or worse?

The term “stability” is sometimes used as a euphemism to refer to how many bugs a program has. I don’t use the word in that way. To me, stability is a measure of a program’s basic ability to keep functioning without crashing or corrupting data. A program can have a thousand tiny irritating bugs and still be very stable. Another program might have only one bug, but if that causes it to crash a dozen times a day, taking down your data with it, then that is very unstable.

So, given that definition, how stable is your AutoCAD, or vertical AutoCAD variant? How often does it crash, or mess up your drawings? How does that stability compare with your experience of earlier releases? How does the stability of plain AutoCAD compare with that of its vertical siblings?

Please add your comments. If this proves a popular topic, I may run some polls.