Category Archives: Performance

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 6, future proofing

This is the sixth and final post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post explains why adding a copy of BricsCAD to your stable of AutoCAD licenses is a good thing for your future and that of your company.

A CAD Management thing I did a few years ago was to examine the options for replacing AutoCAD and other Autodesk products. I was an AutoCAD loyalist (albeit a somewhat critical one) with over a quarter of a century invested in it. I was looking after the deeply entrenched and very heavily customised CAD environment of a major public utility company that had been using AutoCAD as its primary CAD system since the late 1980s. Hundreds of custom commands were in place and providing priceless productivity benefits. Hundreds of thousands of DWG files were on file, with thousands more coming through every month. The inertia behind AutoCAD was very, very strong. Looking outside the cage was a pretty radical step to take. What led me to that point?

  • Autodesk business policy. Autodesk has become increasingly anti-customer over the years in ways that will be familiar to all readers of this blog. I won’t rehash them here. This leads to…
  • Increasing costs. Autodesk software is expensive and getting more so. Autodesk has made no secret of its intention to move to an all-subscription (rental) model. This is an attempt to treble the ongoing income Autodesk receives, in return for doing as little as possible. Which leads to…
  • Lack of progress. It had become clear that the days of AutoCAD seriously improving from release to release were over, never to return. This isn’t because there is no room for improvement, it’s because Autodesk doesn’t want to improve AutoCAD. AutoCAD won’t be permitted to become too capable because that would just eat into sales of Autodesk’s other products. You’re not going to see 3D parametrics or sheet metal capabilities in AutoCAD: buy Inventor instead. You’re not going to see BIM capability: buy Revit. Beyond the internal competition issue, some years ago, Autodesk leadership lost interest in what it perceived to be an old-fashioned dead-end product. The income from AutoCAD customers is being diverted to fund purchase and/or development of more fashionable and interesting products.
  • Frustration with Autodesk’s Beta program. The goings-on within the Autodesk Beta program must remain private, so what I can say here is limited. I can say that I spent many years contributing large numbers of hours to that program in order to attempt to improve the product. As time went on, the positive results that emerged from that effort decreased; that much is no secret because it is apparent in the product. I felt I was fighting against Autodesk to try to improve the product, and losing. There were a few final incidents that persuaded me to stop bashing my head against that particular wall. I wasn’t the only one. I stuck it out for years longer than many very valuable people who had already given up before me.
  • Proxy server issues. Over the years, Autodesk’s habit of attempting to do sneaky things to access the Internet had caused a variety of problems in a secure proxy server environment. This caused several things not to work, and harmed performance severely in some places. As Autodesk’s developers turned over, things that worked in one release would not work in the next. Attempts to get this addressed as a support issue would result in the environment being blamed. These problems increased over the years as Autodesk threw in more and more connectivity-requiring features. There was a non-zero and ever-increasing possibility that one day, Autodesk would screw things up altogether and leave us with non-functioning software. That has already happened for some people, and although the stoppage has generally been temporary, it is important to have redundancy.
  • Poor performance. AutoCAD has been getting bigger and slower. Downloads are huge and Autodesk does its best to make them as difficult as possible. Installations take an age, as do uninstallations. Startup times are terrible and getting worse. My users were complaining – a lot – and there wasn’t much I could do about it.

That’s what moved me to take a very, very serious look at alternatives. Your motives may differ. Just the desire to have a Plan B in case of disaster might be enough.

If you don’t feel moved to investigate, you may eventually be faced with no option. Sooner or later, the person who holds the purse strings at your company may point to this year’s much bigger Autodesk invoice and ask, “What are we getting for this? How can we reduce our costs?” When that happens, you don’t want to be scrabbling round for answers before that invoice needs to be paid. Look into the options in advance. Are you really wedded to AutoCAD or are you actually tied to DWG?

Days of Future Past

Here’s my suggestion. Examine the available alternatives to AutoCAD and the other Autodesk products you use. Do it sooner rather than later so you get the chance to determine the answers to non-trivial questions like these:

  • Capability. Does the alternative product do everything that AutoCAD does, that your users need it to do? Does it do other stuff that AutoCAD doesn’t that you might find useful? What’s the performance like? How does it work on the hardware you have? Does it have user interface elements that don’t just look good but work productively in practice?
  • Compatibility. You will almost certainly demand extremely good DWG compatibility, but this question goes well beyond that. Will your LISP work? How about DCL? ActiveX support? DOSLib? Other programming languages? Can you carry over your customisation files? Can you make the interface look the same? If you have custom toolbars, or ribbon, or even image menus, do they carry across? Can your users carry across their skills without downtime, extensive training and a productivity hit? Can AutoCAD and the potential replacement coexist without issues? Can you use a common set of custom support files pointed at by both products? Will it work well on your hardware?
  • Add-ons. If you’re using third party products on top of AutoCAD, or if you’re using an AutoCAD-based vertical, is that product or an equivalent available? Does it work well? What do the objects they create look like in plain AutoCAD? Can you round-trip through AutoCAD and back and retain your intelligence? You’re probably going to have to test this with evaluation software and your own data.
  • Licensing options. Is perpetual licensing available? Can you stick on a release for a few years and still purchase upgrades later? Has the company committed to providing you with licensing options or has it made noises about going all-rental? Is network licensing available? Does it coexist problem-free with Autodesk’s network licensing software?
  • Costs. Compare the likely costs for all your options over several years. You’re going to have to make some assumptions. It can be difficult to work out what they should be.
  • Track record. Has the company been around for a while? What reputation does it have? Does it treat its customers with respect? How good is the support?
  • Future prospects. Is the company likely to be around long-term? Is it actively developing the product you’re interested in? Is it innovating? Is it merely following AutoCAD at a distance or charging ahead? Is the product going to be limited by Autodesk-like internal competition?

I went through all of these questions and settled on BricsCAD as the best option in my company’s case. In fact, several aspects made it really the only viable option. The product impressed me with high performance, capabilities well beyond AutoCAD in several important areas, a very high degree of compatibility (particularly LISP but also other customisation files), the availability of perpetual licensing and much lower ongoing costs. The company impressed me with its honesty and attitude toward customers.

Most of all, I was won over because I could see that the product had a future. Subsequent improvements have only strengthened that view.

Obviously, you need to make your own judgement based on your own circumstances. I would suggest looking at all the options, including sticking with AutoCAD permanently, with or without subscription or maintenance. Maybe you can use my investigations as a starting point, but I encourage you to start investigating now rather than when you’re under time pressure and don’t have time to do a thorough job.

It will cost you a few minutes to download and install of an evaluation BricsCAD and start preparing for the possibility of a different future. Maybe it won’t turn out to be part of your company’s future, but it could still be part of your future.

Options are good. Learning is good. Best case scenario, your knowledge is going to save your company money and improve its productivity, and you will end up smelling of roses. Worst case scenario, you’re going to spend some very justifiable time doing something new, different and interesting. I recommend it.

Other posts in the Why every AutoCAD CAD Manager should have a copy of BricsCAD series:

Part 1, fixing drawings
Part 2, 3D operations
Part 3, parts on demand
Part 4, efficiency
Part 5, LISP

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 5, LISP

This is the fifth post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about BricsCAD being better than AutoCAD at the one thing that made AutoCAD win the race against its competitors back in the 80s – LISP. That is, AutoLISP (added fully to AutoCAD in Version 2.18) and Visual LISP (fully integrated with AutoCAD 2000).

If you’re a good AutoCAD CAD Manager, you’ll already know the reasons LISP is an extremely important tool, so I won’t cover them here. I may explain those reasons in a later post, but that would distract us from the main point. Why is having a copy of BricsCAD useful to a CAD Manager?

  • BLADE. I’ve covered the BricsCAD LISP Advanced Development Environment in various posts already, and I intend to go into greater detail in future posts. There are enough advantages over VLIDE to warrant an entire series of posts. This is simply the biggest advance for CAD LISP in 20 years; if you’re doing any reasonably complex development in LISP and you’re not BLADE, you’re wasting time and money.
  • Performance. Because BricsCAD’s LISP engine is much more modern than AutoCAD’s, the performance is much greater. In my experience, it’s about three times as fast. Some function calls are as much as 30 times as fast. If you have a user who’s complaining that your routine is taking an age to process in AutoCAD, try it in BricsCAD instead. I once saved a user half an hour in processing time for one polyline by using BricsCAD. Another aspect that will benefit you when programming and testing is BricsCAD’s generally superior performance. Got nothing running and want to get programming in the next 5 seconds? Fire up BricsCAD. Want to do a complex process on a big drawing that makes AutoCAD run out of RAM? Try it in BricsCAD.
  • Licensing. While you’re developing in BricsCAD, you’re not using up an expensive AutoCAD license. You’re using a cheaper (or even free, while you’re evaluating it) BricsCAD license. Also, it’s a perpetual license so if you ever stop paying, you can keep developing as long as you like. Oh, and it’s not going to flake out on you on those days where Autodesk’s subscription licensing server has a meltdown.
  • Extra functionality. BricsCAD’s LISP has the AutoLISP and Visual LISP functions and then some. Some of the DOSLib functions are available without even needing DOSLib, but if you need the full set of DOSLib functions they can be loaded, as per AutoCAD. A range of extended functions are available with the vle- prefix, and the LISP Developer Support Package documents these and provides the source code so you can also use them in AutoCAD.
  • Platform independence. AutoCAD for Mac has severely restricted LISP capabilities, making it unsuitable for use in a professional, efficient custom environment. BricsCAD for Mac and BricsCAD for Linux both provide practically identical functionality to the Windows version. Yes, BricsCAD for Mac really is significantly more AutoCAD-compatible than AutoCAD for Mac.

I do my LISP development in BricsCAD these days, and can attest that it’s well worth the investment in time to get the hang of BLADE.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the LISP situation for yourself.

Edit: it’s not just LISP. See James Maeding’s comment below about .NET, too.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 4, efficiency

This is the fourth post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about BricsCAD being more efficient than AutoCAD for some of the things a CAD Manager might need to do. What do I mean?

  • BricsCAD starts up and closes down faster than AutoCAD, much faster in some environments. If your AutoCAD starts up slow (e.g. in some secure proxy server environments), pretty much any job you need to do to a user’s drawing that involves getting in, doing something quick, saving and getting out again is likely to be finished in BricsCAD before AutoCAD is even open.
  • If you perform a more complex operation on behalf of a user that is likely to take a while, there’s a better-than-even chance that BricsCAD will do it quicker than AutoCAD. In some cases it will do it much quicker (e.g. drawing compare).
  • BricsCAD tends to be able to cope with large drawings while using less memory than AutoCAD. If you have a user with a huge drawing who can’t work with it any more in AutoCAD and you need to split, purge or simplify it before it is usable, the very process of doing that in AutoCAD can itself be unworkably slow. Try the same thing in BricsCAD and there’s a good chance you’ll get the job done in a fraction of the time and without the same level of frustration.
  • If you perform a batch process that operaties on a set of drawings, under most circumstances it will be finished in BricsCAD well before the same thing is done in AutoCAD. Maybe this means you can process a set of drawings over lunch rather than wasting all afternoon on them or waiting until home time before setting the batch going. Plus you’re occupying a cheap BricsCAD license rather than an expensive AutoCAD one. Also, because BricsCAD uses much less RAM than AutoCAD while running, you can run your batch processes on that old PC sitting in the corner rather than having your top user sitting around watching your top spec PC grind away.
  • Certain user interface structures in BricsCAD are much more logically arranged and efficient to use than the AutoCAD equivalents. For example, if you have a drawing with an obscure setting that needs changing, unless you have an impeccable memory, you’ll find that setting much more quickly using the BricsCAD Settings command.

As I mentioned in my last post, this series is all based on stuff I’ve done in real life as a CAD Manager for a primarily AutoCAD-using company. Feel free to add your comments with your own experiences, even if they differ from mine.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the performance and efficiency for yourself.

Bricsys shows Autodesk how to do mid-term updates – again!

BricsCAD V18.2 for Windows is out. The new stuff in this mid-term update is again showing up Autodesk’s lack of progress with its once-flagship product, AutoCAD. I’m sure Autodesk would love customers to accept that there’s only so much anyone can do with a DWG-based CAD product once it reaches a certain level of maturity. Customers should get used to nothing of significance being added year after year. Diminishing returns, and all that. Pay to continue using the product, but don’t expect it to get better.

What a shame for Autodesk, then, that Bricsys exists. By consistently providing a raft of significant improvements with each full and mid-term release, Bricsys shows up that idea as nonsense. It’s perfectly possible to keep improving CAD at a very rapid rate, particularly if you’re not worried about competing with other products in your range. There’s a reason AutoCAD’s parametrics are restricted to 2D, and BricsCAD’s 3D parametrics in a DWG product proves that the reason isn’t technical. It’s strategic. Also strategic is cutting the guts out of an already much-weakened AutoCAD team, because you would really prefer your customers to be using your trendier and/or more expensive products.

I should point out that BricsCAD V18 customers who have a perpetual license, even without maintenance, will be receiving V18.2 with all its improvements free of charge. Contrast that with Autodesk, which is, despicably, withholding even bug fixes from selected customers. Autodesk’s attitude to customers who aren’t constantly paying up front is one of utter contempt. Autodesk feels entitled to your money; Bricsys wants to earn it.

So what’s Bricsys done to earn your money with BricsCAD V18.2?

Mostly, it’s lots of relatively small-sounding things that add up to significant productivity enhancements. There are several items that are playing catch-up to AutoCAD, such as long-overdue in-place text editing. There are big performance improvements in drawings with PDF underlays due to a smart multi-resolution cache mechanism. The 3D-to-2D generation mechanism has also been significantly sped up. Constraints (2D and 3D, unlike AutoCAD) are easier to create. Several 3D direct modeling operations have been made easier. That also helps with sheet metal design, which has seen other improvements.

In Bricsys BIM V18.2, a lot of smarts have been added. The mechanism for converting CAD models (including those made in BricsCAD Shape) to BIM models, BIMIFY, already did some fascinatingly clever things, but that’s been improved further particularly in the areas of structural member and room recognition. For those of us in Australia, support for our steel sections is very welcome.

For me, that’s not the big news. Oh, no. The big news for me is a thing called BLADE – the BricsCAD LISP Advanced Development Environment.

If you’re a CAD Manager or in-house developer and you’ve been waiting until BricsCAD had VLIDE, wait no longer. But this isn’t just catch-up. This is a big leapfrog over Autodesk’s sadly neglected IDE for CAD’s primary user programming language. There’s so much good stuff in BLADE that I can’t hope to do it justice here, so I will be covering it extensively in future posts. For now, here’s a statement for you:

If you program in AutoLISP or Visual LISP, you should be doing it in BLADE.

It’s that good. Really. Watch this space for details.

The download is small, the install is fast, it won’t harm your AutoCAD installation, and you can evaluate it free for 30 days. Links:

What’s changed at blog nauseam and why

Last week, blog nauseam died. This post explains the background to that. You’re probably not that interested, so feel free to skip to the dot points that list the changes that have resulted.

The problem was a faulty WordPress installation was using excessive resources. This caused severe performance issues and resulted in the server software stepping in to throttle the site to prevent more widespread problems. The trigger for the WordPress fault has not been determined and may never be. This is somewhat akin to an old AutoCAD drawing suddenly going bad for unknown reasons. The problem may date back years but only recently became critical.

In discussions with my completely blameless web host, Saratoga Hosting, we determined the best course of action was to create a new, clean WordPress site and transfer over as much as possible from the mortally wounded old installation. This is similar to copying and pasting or inserting valid entities from a bad drawing to a clean one, and this is what we did.

I say ‘we’ because Dave from the most excellent Saratoga did a huge amount of work for me to ensure things went as smoothly as possible and with the best result. This is not the first time I have received quite outstanding above-and-beyond customer service from Saratoga in return for the few measly bucks a month I pay for hosting. Thank you, Dave!

Doing things this way provided opportunities for several improvements to both blog nauseam and its parent site, cadnauseam.com. These include:

  • Improving performance. A clean install that’s not generating many errors per second will load much faster than one that isn’t, just like a small clean program like BricsCAD will perform much better than an old bloated mess like AutoCAD that’s attempting to do hundreds of things a second even when sitting there doing nothing.
  • Upgrading site security. In addition to various unseen improvements including upgraded protection against hackers and better backups, the site now uses https SSL security, which is the way things are going to have to be in coming years. You may have noticed that the URL now starts with https:// and displays a little closed padlock, indicating this is a secure site.
  • Integrating cad nauseam with blog nauseam. My old cad nauseam site was a bunch of hand-coded HTML pages that were real cool in the 90s but which have been neglected for years. It’s now part of the same WordPress installation as the blog, which avoids duplication of various things and is much easier to maintain. It also makes sense for me from a business point of view to have my business site more closely associated with a successful blog.
  • Modern full-screen interface. The integration of cad nauseam and blog nauseam didn’t work well with the old Tempera site template, so I took the opportunity to switch to a cleaner, more modern looking template, Fluida. In addition to being very configurable, this template does all sorts of fancy hover-over stuff that some of you will undoubtedly hate, but in my tests it performed well and didn’t get in my way. The best thing about it is that it’s now full-width: Tempera was not. Some of you won’t like that change either, but I always dislike using a web site that confines itself to a narrow stripe in the middle of a high resolution CAD screen. Now I don’t have to dislike my own site.
  • I’ve redesigned the favicon to reflect the dual cad nauseam / blog nauseam nature of the site.

I have now restored the polls and image galleries. The automated redirection of old URLs to the new location should now be working. The downloads page is still a work in progress and will remain hidden for a while, but that’s mostly of historical interest anyway.

Again, my apologies for the breakdown and the inconvenience of change, but I’m glad that there have been quite a few positives arising from a bad situation.

If there are things about the site you don’t like now, feel free to let me know.

Bricsys shows Autodesk how to do mid-term updates

BricsCAD V17.2 is out. Although there’s nowhere near as much new and useful in this mid-term update as in the full upgrade from V16 to V17, there’s more here than in Autodesk’s last mid-term update, AutoCAD 17.1. There’s even arguably more than in the uninspired AutoCAD 2018 upgrade, including those 17.1 features.

But that’s not the main reason I say Bricsys is schooling Autodesk in how to do mid-term updates. While Autodesk is restricting such updates (including the bug fixes and security updates included in those updates) to subscription and maintenance customers, Bricsys is doing no such thing.

BricsCAD V17 customers who have a perpetual license, even without maintenance (called All-In by Bricsys), will be receiving V17.2 free of charge. Bricsys still considers such users as customers who have paid good money and still need to be looked after, rather than a non-paying irritant, which appears to be Autodesk’s attitude.

Oh, and you don’t have to install some piece-of-junk automatic updater or malware-like download manager to get the software. You just do a straightforward browser download of a small file (by Autodesk bloatware standards) which is the entire product, and install over the top of your existing installation, effortlessly preserving your settings. If you’re doing a new install of V17.2 from scratch, you just install from that downloaded product. No need for multiple downloads and multiple-step installations. No need to have every PC in your fleet nagging your users and downloading the same huge files.

Autodesk isn’t in the hunt here for ease of maintenance. Not remotely in the same league. Seriously, go home and start again, Autodesk. Your ideas are bad and your execution is worse.

Here are some links to information about the V17.2 update (not neutral sources, obviously):

I will be benchmarking BricsCAD V17.2 and AutoCAD 2018 with great interest. In my preliminary tests, BricsCAD V17.0 performance walked all over AutoCAD 2018 in most areas, but commands involving object selection were the exception, with AutoCAD significantly quicker there. Bricsys is claiming large improvements in that area, but we’ll see.

BricsCAD’s LISP kicks sand in the face of AutoCAD’s

If you’re a power user or CAD Manager transitioning from AutoCAD to BricsCAD, one of the things you’ll like is that almost all of your LISP routines will just work. That’s not an statement that can be made about various Autodesk products that bear the AutoCAD name, such as AutoCAD 360, AutoCAD LT and AutoCAD for Mac.

It’s not just simple old AutoLISP code that runs in BricsCAD, but complex dialog routines that use DCL, and Visual LISP stuff that uses ActiveX. Yes, even on the Mac and Linux platforms. Some DOSLib functions are built in and the rest can be loaded, as with AutoCAD. Even OpenDCL is supported. It’s a quite astonishingly high level of compatibility.

But it’s not 100%. There are minor incompatibilities, system variable and command-line differences that cause problems in a handful of cases. It’s often possible to work around these and still retain the same code that works in both AutoCAD and BricsCAD. Reporting LISP bugs and incompatibilities to Bricsys generally gets them fixed super-quick.

Also super-quick is the speed at which your code will run. It’s immediately noticeable when running any LISP code that needs to do a bit of processing that it just gets done faster in BricsCAD than AutoCAD. Fast enough to extract the following comment from one of my AutoCAD users trying out a linework cleanup routine in BricsCAD:

Wow.

 
User impressions are one thing, but how about measurements? Today, I had a support job to do that involved running one of my LISP routines. I ran it on both AutoCAD 2017 and BricsCAD V17 on the same PC. AutoCAD took 2970 seconds (about 49 minutes), BricsCAD 1030 seconds (about 17 minutes). Over half an hour saved on one operation. That’s 2.88 times faster, which is consistent with my previous observations with a variety of routines.

Upshot: if you’re doing work where there’s a lot of LISP processing going on, switching to BricsCAD is going to save you a shedload of time.

There is a downside to BricsCAD’s LISP, and it’s a big one; no VLIDE. No equivalent, either. There are various programming editors around that can help with editing code, but no substitute for integrated debugging. It means if you’re a power user, CAD Manager, developer or support person, you’re probably going to have to keep one working copy of AutoCAD around even after you’ve completed the transition to BricsCAD.

Because VLIDE has been in maintenance mode for over 15 years it remains virtually unchanged year after year (including ancient bugs). So it doesn’t matter that much which AutoCAD release you have hanging around. Assuming you’re a perpetual license holder, when you drop the maintenance contract on one of your AutoCAD licenses, you’re entitled to keep using the software as long as you wish, albeit only the current release at the time the contract ends. How long the software will keep working is another matter, depending as it does on factors not entirely within your control.

This is an imperfect solution. Even keeping a copy of AutoCAD around won’t help much if you’re debugging a problem caused by something specific to BricsCAD. Filling the VLIDE hole is something Bricsys needs to work on.

AutoCAD 2013 – Using Help in anger

Trying to be fair, I decided to put aside my initial hostility to the AutoCAD 2013 Help system and use it for real. I used it in a realistic situation, to find out how to work with something new or changed (model documentation) as I was working through it with my own example drawing. Try as I might to give it a fair go, I could only get so far before I got irritated. Using it in anger might not be an entirely appropriate phrase for it, but it’s not that far off. Using it in annoyance, perhaps? Here’s how it went.

I hit F1, wait for it to finish loading itself, click in the search box (because that’s not where the focus is to start with), type ‘model documentation’ and pick Search (because Enter doesn’t work). I then wait again, for about 10 seconds, even though I’ve configured it for offline use. Eventually, there is a huge mass of results displayed, almost all of which are totally (totally!) irrelevant to model documentation. Most of them are relevant only to ARX programmers dealing with completely unrelated matters.

If I use the “phrase” option rather than “and”, the list is much shorter and has a much higher proportion of results that have some relevance, but there are still completely pointless results. For example, the 4th result is About Performance Considerations (AutoLISP), which does not contain the phrase at all. It does contain the words ModelSpace and Document, but not together. It does not contain any information remotely related to model documentation. Didn’t Autodesk buy a search technology company a while back? If that company’s technology is in use here, then Autodesk bought a dud.

At least the top two results directly relate to what I need, so I’ll move on with those. They are Commands for Working With Model Documentation Drawing Views and About Model Documentation. The content of the former page is OK; it’s just a list of commands. There is some pointlessly wasted space at the top of the page that means I have to scroll down to see the bottom of the list, but other than that it serves as a useful reference. The latter page is also fine. It’s an executive summary of the feature with a few relevant pictures, followed by a decent set of links pointing to relevant pages that expand on the subject and explain how to do various tasks associated with it. Now I have overcome the inadequacies of Search and determined that useful Help content is all there, that’s all good then, isn’t it? Not really, I’m afraid.

If Help was being run from a real browser, I’d be able to keep both of those starting pages open with their useful links, then middle-click on each of them as needed to open each useful page in a new tab. However, Help isn’t being run like that. It’s being run from inside Autodesk’s pseudo-browser thing, which only allows one page at a time to be displayed. To be fair, this restriction also applies to the old CHM-based Help to some extent. However, the old CHM Help is split into multiple sections, and it is possible to have multiple CHMs each open in their own windows. For example, I can have the AutoCAD 2010 main Help and Developer Documentation open at the same time, something that’s very important for my productivity and which I would find extremely difficult to give up.

To work around the tabless nature of 2013 Help, I need to choose one particular page and stick to it. When I need another page, I need to navigate back up to one of the original links pages and then back down again. That would be bad enough if navigation within the pseudo-browser was good, but unfortunately it isn’t. Despite what looks like a breadcrumb feature at the top of the page, this is non-functional because of the lack of a hierarchical structure to the content. It just keeps taunting me by saying ‘Home’ and nothing else, pointlessly wasting a swathe of vertical space. There are back and forward buttons in that space, but the back and forward mouse buttons I can use everywhere else do nothing in this browser. You can use Alt+Left and Alt+Right to back and forward. Don’t go too far back, though! If you do, the Search panel goes blank and can’t be restored by going forward again, or by switching between Favorites and Search. To fix this, you can close and restart Help , or pick the Home button and wait about 6 seconds for it to get its act together and restore the Search panel. Then you’ll be at the home page, which may not be where you wanted to go back to.

All right, so I have chosen the single page I’m allowed to have open and I want to use the features it describes. This test PC only has a single 1280 x 1024 screen so there really isn’t room for both AutoCAD and Help at the same time, a situation that will be familiar to users of notebooks. I click on the AutoCAD drawing area behind the Help window, expecting AutoCAD to come to the top and to go behind it. Nothing happens, other than Help losing focus. Help stays on top, obscuring the drawing area. If I click the main AutoCAD taskbar button (this is in XP), that minimizes both Help and AutoCAD. Restoring AutoCAD also restores Help, so it still obscures the drawing area. The two windows are linked, and not in a good way for somebody with one screen. I guess some users will want Help to stay on top, but there are plenty of others who won’t, so what could Autodesk have done to keep everybody happy? Made it configurable, obviously.

Eventually I worked out that I could work on AutoCAD if I explicitly minimised the Help window, so away I went. I used the Commands for Working… page, then the VIEWBASE page to start my model documentation experiment. I then picked another link from the VIEWBASE page, the Drawing View Creation Ribbon Contextual Tab page. Having finished with that, I wanted to get back to the Commands for Working… page, so instead of picking multiple Back buttons (which as noted above is fraught with danger if you do it too often), I clicked on that result in the Search panel on the left. Did this take me back to the Commands for Working… page? No, it did not. It did nothing at all. To make it work I had to click another search result first, and only then the one I really wanted.

One saving grace is that I discovered that if I right-clicked on a link in Help, I could copy the URL and then paste it into a proper browser. This works both on and offline, and allowed me to work around many of the problems noted above. This kludge doesn’t work for search results, though, only for links in pages.

I’ve given AutoCAD 2013 Help a decent go, as much as the average reasonable person would before giving up. Maybe more so. I feel pretty comfortable about giving it what I consider a fair assessment. The content of the Help pages itself looks pretty good to me, at least for those pages I visited and the context in which I was using them. If you already know what command you’re supposed to be using, you just hit F1 from within that command to get at the page you want and you don’t need to go any further, you could well be satisfied. But if you’re using the system in any other way, there’s no getting away from it, it’s a crock. The content is not the problem, it’s the loss of structure to that content, and the browser thing being used to present that content. That loss of structure was A Bad Idea and the browser is a very poor effort. The system as a whole should not have been inflicted on customers.

As a courtesy, Autodesk should do what it did following the 2011 Help debacle and provide a CHM solution for customers to download. It should then go on providing a CHM solution indefinitely, until it can come up with something that is of comparable quality. People are already talking about making their own 2013 CHMs. Autodesk, please do the right thing and save them the bother; let us all know that you’re going to provide CHM as a workaround and get it to us as soon as you can. Don’t worry about losing face by admitting that the 2013 Help isn’t up to scratch. It’s too late for that; we’ve already noticed.

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.

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.

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.

AutoCAD 2012 – Massive download bloat

Note: this post is not an April fool’s joke. It may be ridiculous and hard to believe, but unfortunately it’s all true.

After I managed to overcome Autodesk’s obstructive download manger and download AutoCAD 2012, it became available on the Subscription site (when that site wasn’t running unusably slowly). Or it became kind-of available. Here’s what is actually available:

  • AutoCAD 2012 Multilingual 32 bit
    Download File Size: 2,080,558,319 bytes (1,984.2 MB)
  • AutoCAD 2012 English Korean Traditional-Chinese Simplified-Chinese Win 64bit
    Download File Size: 2,240,915,999 bytes (2,137.1 MB)

These file sizes are roughly double those of the AutoCAD 2012 English files I’ve already downloaded from the trial page and installed. The 32-bit English file is 1,144,011,680 bytes, or 55% of the size of what the Subscription site is trying to offer me.

Why? Because the Subscription downloads contain three bonus Asian language packs. It has apparently escaped Autodesk’s notice that Australia is an English-speaking country, and that the ability to install a Korean version of AutoCAD 2012 isn’t going to be spectacularly useful here. Duh!

There was a a distribution fiasco last year when Autodesk couldn’t make up its mind which AutoCAD 2011 language variant Australian users were supposed to use. This resulted in weeks of delays, uncertainty and disrupted shipments. This year, there’s less uncertainty. Somebody has made a firm decision about what we’re getting, right from the start. What a shame it’s the wrong one, and it makes Autodesk look utterly clueless.

Just in case you’re wondering, the AutoCAD 2012 English from the trial page installs and works fine, correctly detecting that I’m in Australia and presenting the correct legal information. The installation also registers and authorises correctly using the serial number provided on the Subscription site. No problems there, then.

What, then, is the reason for the massive download bloat? Is it really just stupidity, or is there some legitimate reason for it? I’m informed that installing the English version of 2012 in Australia may cause some problems with Migration when upgrading to 2013. I am unconcerned about this for two reasons. First, I’m sure migrating from 2012 English to 2013 English will work just as well here as it does elsewhere in the world. it’s not as if the Migration utility has to invert the bits or anything for Down Under users. Second, I have avoided Migration anyway since AutoCAD 2006, when “improvements” rendered it effectively unusable to me.

AutoCAD for Mac in Beta

Disclaimer: I have absolutely no access to inside information about this Beta. Even if I had, I would not reveal anything that I had learned as a result of such access. This post discusses only information that is already public knowledge.

The native Mac OS X AutoCAD port that Autodesk has been foreshadowing for some time is now in Beta, it seems. The Italian Mac community is getting particularly excited about the leak, but it’s also a popular subject of discussion on at least one English-speaking forum. The Autodesk codename is Sledgehammer, and it’s currently 64-bit only. If this is a subject that interests you, with a bit of sniffing around you can easily find screenshots, a video and you can apparently even download it via torrent if you’re feeling particularly brave/stupid.

If you’re interested in trying it out, it would be much better to apply to join the Beta program. That way, you will stay legal, you won’t download a trojan and you will contribute towards improving the product. Autodesk will probably need such contributions, because the early Beta allegedly runs like “a sewer” with huge performance issues. That should not be a surprise at this stage, but it should give you some idea of how much work Autodesk has ahead of it before it has a product that is fit for human consumption.

Oh, if you do join Autodesk’s Beta program, please be a bit more careful with the software than the guy who thought it would be a cool thing to hand out to his friends.

Edit: Ralph thinks it’s fake. I really don’t think it is, but must acknowledge the possibility that I’m wrong.

Edit 2: More discussion and screenshots at SolidSmack.

AutoCAD 2011 online Help changes – a curate’s egg

As announced by Shaan Hurley, Autodesk has made some changes to the AutoCAD 2011 online Help system. Please check it out and see what you think. After a short time with it, here are my experiences using IE6 (yes, I know). As this is a dynamic system and dependent on browser characteristics, Internet connectivity and any changes Autodesk may make between me writing this and you reading it, your mileage will vary.

There are some cosmetic changes,  including a fixup of the Autodesk logo in IE6 that was done a couple of weeks ago. Sadly, my pink Comic Sans logo has not been adopted.  As I can’t do a direct side-by-side comparison with the pre-change setup under identical conditions, I can’t make a definitive statement about performance. I can say that it does appear to have improved somewhat. It now takes about 3.5 seconds from hitting F1 to seeing a complete landing screen. Once cached, I’m seeing it in come up in just under 2 seconds.

The main change from a usability point of view is that the Search facility now defaults to searching All Books rather than whatever document you happen to have highlighted over on the left sidebar. That’s welcome. Also, the searches generally appear to give better results. For example, a simple search for LINE in the original 2011 online system gave a list of 199 results, of which the actual LINE command was 26th! Now, a search for LINE puts the LINE command third in the list; much better. The results come up faster than before (2.5 seconds in this example), but I have seen widely varying search times reported so I would be interested to hear about your experiences.

The way the search results are presented is now significantly different. Instead of a single line for each result, 4 lines are now used. There is a descriptive hyperlink line, a line containing sample of text from the page the link points to, a spelled-out link line and a blank line. The second line appears to be randomly chosen. In our LINE example, the text starts with “If the most recently drawn object is an arc…”, which is a fairly long way down the LINE command page itself. The third line’s only function appears to be to waste space. I can right-click on the main link if I want that information. I can’t even copy and paste that third line; attempting to click and drag in the search results pane selects the whole lot.

Because of the newly verbose display format, it obviously doesn’t make sense to display 199 results, as there would be too much scrolling. What is now displayed is 8 results, with links to another 7 pages (I’m not sure what happened to the 199 – 64 = 135 other results). If your desired result is in the first 8, that’s fine. If it’s not, then you have a harder job now to find what you’re after. You can’t use your browser’s find feature to look for a specific word among the full set of results. You will have to click on each page in turn and wait for it to appear before scanning the results. Fortunately, each page comes up fairly quickly (about 1 second), but I would much prefer to have the option of seeing more results displayed on each page. I suspect things have been arranged this way to improve performance (fair enough) and make it work better on mobile devices. While that’s all nice and cool and trendy and geeky and everything, I don’t intend to ever use AutoCAD on an iPhone. I would much prefer it if Autodesk prioritised its user interface design based on what the vast majority of its users are going to be using when they need the documentation.

Choosing a different page within the search results and then using the Back button takes me back to the main landing page rather than my previous results page. Using the Forward button to try to get back where I was, just puts me back on page 1 again. This is obviously not good.

That’s enough of the changes in isolation, how does today’s system compare with what went before? I did a quick test to see what was involved in finding out about a given command. I chose the WBLOCK command. Other commands and other users may give better or worse results.

AutoCAD 2010 CHM Help
Method: F1, type W, double-click on WBLOCK
Time taken: 2.6 seconds

AutoCAD 2011 offline Help (as shipped)
Method: F1, click in search box, type W, Enter, click on W commands, click on WBLOCK, click on Write Block Dialog Box
Time taken: 12.1 seconds

AutoCAD 2010 online Help (as at 12 May 2010)
Method: F1, click in search box, type W, click outside search box, click on search arrow, click on W commands, click on WBLOCK, click on Write Block Dialog Box
Time taken: 16.0 seconds

Given those results, it would be pretty hard to argue that the new system is more efficient for users. Again, this is just a sample command and method, and if you can find a different one where the new stuff works better than the old, I’m all ears. The method I ended up using for testing the 2011 online search actually required a fair bit of trial and error. Here are some things I tried first:

  1. F1, click in search box, type W, autocomplete gives me ‘wireless’ (left over from some other search I used on an unrelated site), Enter, nothing happens
  2. F1, click in search box, type W, click outside search box so I just have W, Enter, nothing happens
  3. F1, click on search arrow, click in search box, type W, it gets added to the end of the word Search, giving me ‘SearchW’!

A few minutes after my tests, I tried again to see if there was a better way. What I found was that the W Commands link I needed was completely absent from the search results!

Look, no W Commands!

W System variables, check. W Methods, check. W commands? Nope. Not on this page. Not on any of the other 7. Where did it go? Will it return one day? Who knows?

One of the risks of online-based software is that it can be a moving target. Stuff that you used in the past may not be there the next time you need it. It’s easy to see users getting confused and frustrated by this kind of stuff. After all, it’s supposed to be Help, not Hinder.

In summary, some of the changes are welcome, but the system is still a long way short of being anywhere near as efficient or friendly as the one it replaced. The performance is better than it was, but still slow. The interface contains some clangers that tell me that user feedback has been absent, inadequate and/or ignored.

I suggest this system be withdrawn, and soon. AutoCAD 2011 Update 1 should contain a complete and properly integrated CHM-based Help system, and Autodesk should go back to the drawing board with the whole browser-based Help idea.

If, after due consideration and extensive user consultation, Autodesk still thinks that online Help is a good idea, it should spend the time required to make it work properly, introduce it only when Beta testers are satisfied that it is at least as good as what it is replacing, and then introduce it alongside the CHM system. The two systems should be run in parallel for as many releases as it takes to convince the vast bulk of users that online is best, at which point the losing system can be discarded.

Right now, it’s abundantly clear which system should be ditched, and it’s not the CHM one.

How is your AutoCAD 2011 hatching?

Hatching is the poster child for AutoCAD 2011’s 2D drafting feature changes (although there are several other significant ones), and also for demonstrating the advantages of providing a contextual interface via the Ribbon. It looks great at first glance when working with simple demo drawings, but how are things going in the real world? I’d be interested in hearing about your experiences.

  • Is the hatch Ribbon tab snapping into place and going away quickly enough, both the first time it is used in a session and subsequently?
  • Is the Ribbon interface easy to use, efficient and complete?
  • Does the hatch preview always match what’s actually hatched when you accept the preview? If not, how often is it wrong?
  • Are you happy with the new default double-click hatch action? (If not, see the Hatch double-click section of my AutoCAD 2011 – Putting things back to “normal” post).
  • Does the hatch preview work quickly and accurately in simple areas? How about more complex areas? How about areas bounded by complex polylines with lots of vertices?
  • Is the performance up to scratch when creating and editing both associative and non-associative hatches? How about when grips are visible on complex bounding areas? How about when you make changes to hatches using the Properties palette?
  • Is boundary detection working reliably in finding and filling a closed hatch area? Even when using a solid or gradient hatch pattern?
  • How is your zoom and pan performance in drawings with a lot of hatching?
  • Have you noticed any problems with the new transparency and background features?
  • Have you experienced any hatch-induced crashes or lockups?
  • Are any of your hatch problems new to 2011, or do they also exist in earlier releases on the same PC when using the same drawings?

If your hatching performance is poor, have you tried changing the values of system variables to turn off features to see if the problems persist? Try HPQUICKPREVIEW = 0, HPDLGMODE = 1 and SELECTIONPREVIEW = 0. Also, if you are having display performance issues, try VTENABLE =0 and check using 3DCONFIG to see if your graphics card/driver combination is certified.

AutoCAD 2011’s new Help system – what do you think?

With all this talk of clouds in the air, it is interesting to note that Autodesk has moved AutoCAD’s Help system to a browser-based format, with online access as the default. So, how has Autodesk done with this first dipping of its toes into the cloudy waters with its primary mainstream product? I’ve already had a couple of unsolicited comments on the subject, and I’d like to hear from you. How do you rate the following, compared with previous releases?

  • Performance (online)
  • Performance (offline)
  • Search results
  • Content completeness and accuracy
  • Ease of manual browsing
  • Efficiency of user interface
  • Concept of online Help
  • Anything else you want to mention

Please comment to express your views and use the poll on the right to provide an overall rating of the new system.

AutoCAD 2009 & 2010 users – out of memory errors?

Some of the users I support have repeated out-of-memory errors while editing fairly simple drawings. I have some 2010 users who suffer from this problem while others using the same drawings on the same hardware get by without ever seeing it. When swapping users to differerent PCs, the problem seems to follow the user. Despite various experiments, I have no idea what is going on here.

Is this happening to you or anybody you work with? Have you managed to work out if there is something that triggers it? Is there a user interface setting or method of drawing that you suspect of being the culprit?

Does your AutoCAD get its wrods worng?

A problem I’ve seen affecting keyboard users (particularly fast ones) in recent AutoCADs (since 2006) is that the characters entered into the command line are not always the ones you typed. Or rather, they are the ones you typed, just not in the right order. In particular, I’ve seen the first couple of characters get messed up, so you might get ILNE instead of LINE. In addition to the annoyance factor, this is something of a productivity killer.

Has this happened to you? If so, please comment. Any comment is welcome, but it would be great if you could provide the following information:

  1. AutoCAD (or vertical) release(s) where you have seen this happen. Also mention any recent releases where you have seen it not happen.
  2. Command line status when you have seen this happen (docked, floating, off, all of the above).
  3. Dynamic input status when you have seen this happen (on, off, on but with some options turned off, all of the above).
  4. Screen configuration when you have seen this happen (single, dual, either).
  5. AutoCAD main window status when you have seen this happen (maximised, floating, either).
  6. Other than this problem, does AutoCAD’s general response to input seem “sticky”? Sticky keyboard, mouse, or both?
  7. Other than AutoCAD, do any other apps give sticky response on the same PC?
  8. General PC stats (OS, CPU type and speed, RAM size, graphics card).

Please add anything else that you think might be useful in tracking this down or working around it. If I learn anything that might be useful, I’ll report back in a later post.

Why AutoCAD for Mac is a bad idea

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.