Autodesk remotely killswitches AutoCAD licenses – again

Following the AutoCAD 2019 rollout disaster, where subscription users found their AutoCAD 2018s were broken by an Autodesk licensing system meltdown, Autodesk CEO Andrew Anagnost issued an apology. He also assured customers on Twitter that it wouldn’t happen again: While I welcomed that, I did have this to say at the time: I don’t think such a guarantee is realistic, given that the nature of subscription software is to only work when it knows you’ve paid up. At least it demonstrates that the desire is there right at the top to try to prevent such debacles from occurring in future. …

AutoCAD 2019 rollout disaster

If you’re an AutoCAD user, you may have been intrigued by the news about the new way Autodesk is bundling up AutoCAD 2019 with various verticals (perpetual license owners need not apply). This is Autodesk’s latest attempt to promote its subscription model and raise prices again. 7% this time, but much more to come. But never mind that, the main point is that you’re getting a whole lot of stuff, and who could say that’s not a good thing? So it’s most unfortunate for Autodesk that the AutoCAD 2019 rollout has been an unmitigated disaster. My own experiences in trying …

CAD Nostalgia Video

For the first video in the new cad nauseam YouTube channel, I’ve had a bit of fun. I unearthed a bunch of my old stuff to show you. Does any of this take you back? Enjoy!

Why digitally sign your LISP files?

After I mentioned in an earlier post that I had digitally signed the sample LISP file I had provided, this generated some interest. In this post, I’ll explain why you might want to sign your LISP files. In a later post, I’ll explain how to do it. These days it is standard practice for developers to digitally sign their code. Operating systems and applications are displaying increasingly scary warnings when coming across unsigned code. Here is an example of the sort of message you get when you load an unsigned LISP file into AutoCAD from a location that has not …

When spambots get it wrong

I’ve posted before about the amusement that can be had at the expense of the clueless spammers who set up their bots with poorly written strings. Thanks to the various anti-spam tools now protecting this blog, there are few comments appearing in my spam folder. There was one today though, and the cluelessness reached new heights. The dolt writing the spambot was too dumb to set it up correctly to spew out a series of inane generic comments from a list, but instead put the whole lot of the comment strings in a single self-contradictory comment! Here it is in …

First 2018.1-broke-my-AutoCAD reports coming in

Thanks to R.K. McSwain for pointing out that at least one user has reported unexpected shutdowns from AutoCAD (Architecture, probably) following installation of the 2018.1 Update. The problem went away following uninstallation of the update. Caveat updator. Anybody else have any issues or are you all waiting for the early adopters to find out for you? Edit: it turns out the crash occurs when opening 2013 DXF files. Edit 2: a hotfix has been posted here.

AutoCAD 2018.1 released, but only for some

Autodesk has released the AutoCAD (and LT) 2018.1 Update, not to be confused with the earlier ill-fated 2018.0.1 Update. It’s only available for currently-paying subscription and maintenance customers. The “non critical” bug fixes in this Update (by Autodesk’s definition) are being withheld from Autodesk’s other customers. Those of you who have allowed your maintenance to expire due to Autodesk’s development inaction and unjustified price increases can consider yourselves duly punished for failing to fall into line. If you have the execrable Autodesk desktop app installed (not recommended) and it works as expected, this update will present itself to you. Otherwise, …

Autodesk Senior Vice President tells it like it is

I didn’t expect to see any comment about the policy of denying bug fixes to some customers from any Autodesk high-ups, but I was mistaken.

Here’s a quote on just this subject from Autodesk Senior Vice President1, Buzz Kross:

It’s just bad business. Why would you not want to take care of your customers? I would never do that. Come on, we all make mistakes. All software has bugs and as a developer, I have an obligation to provide fixes to all my paying customers, whether they are on subscription or not. Customers on subscription have the advantage of getting access to new stuff. That’s fine. But denying them access to bug fixes is just not right.

Buzz Kross, Senior Vice President, Autodesk1
9 April 2010


Photo: Autodesk

It’s not often I so completely agree with an Autodesk executive1, but I can find no fault in his logic. Thank you, Buzz.


1. Although Buzz is still listed as a SVP in some Autodesk online materials, he’s no longer with the company.

Autodesk confirms its own unconscionable conduct

It took several attempts over a period of months and was like pulling teeth, but Autodesk has now confirmed that it is deliberately withholding bug fixes from some of its customers. Autodesk has taken customers’ money and in return has provided defective software (OK, that happens). It has fixed some of those defects (that happens too, sometimes). But it’s limiting distribution of those fixes to those prepared to pay Autodesk further (that has never happened before). Just let that sink in. Autodesk broke stuff you paid for, could easily fix it, but won’t do so unless you pay more. If …

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 …

Automated .NET 4.7 update kills AutoCAD pre 2017

Thanks to Robert Green for pointing this out: Microsoft is installing .NET 4.7 as part of their auto updates and it is causing many legacy Autodesk applications to crash on any ribbon interaction. Touch the ribbon, away goes your software. If you can keep from installing the 4.7 framework do so. If the damage is already done then uninstall .NET 4.7 and install .NET 4.6.2 using this download link. Note that the uninstall of the offending version must be done first! AutoCAD 2013 to 2016 and Inventor are affected, and possibly other products. BricsCAD users are unaffected. It is also …

AutoCAD 2018.0.2 arrives

AutoCAD 2018.0.1 is dead, long live 2018.0.2! Here’s the readme. Here’s the 64-bit direct link. Here’s the 32-bit direct link. This supposedly fixes stuff that 2018.0.1 broke, such as the signed VLX thing. Will this one break other stuff? I guess we’ll find out.

AutoCAD 2018.0.1 mystery deepens with silent withdrawal

As I mentioned earlier, the release of AutoCAD 2018 was followed almost instantaneously by the first update, 2018.0.1. At the time of writing, there was no official information about this update. Some information was later made available, but questions remained. Now the update has been silently withdrawn. Go to Autodesk Account > Management > AutoCAD > Downloads > Updates & Add-ons and you will no longer see this: The infamous Autodesk desktop app also shows no sign of this update. So why has it been withdrawn? Autodesk isn’t saying, but thanks to Jimmy Bergmark, we know that installing the 2018.0.1 …

Autodesk updates Design Review

Despite the previously announced end-of-active-life for Design Review (Autodesk’s DWF viewer), there is now a new release available. This wasn’t supposed to happen, because we should all now be using cloud-based solutions. A new version of DWG TrueView was needed to deal with the new DWG 2018 format, and one knock-on effect is that a new Design Review was needed to be compatible with DWG TrueView 2018.  It’s still only 32-bit, so it appears to be a matter of Autodesk just touching it up enough to keep it compatible. Interestingly, the new Design Review is not called 2018. Here’s where …

AutoCAD 2018.0.1 mystery partially resolved but questions remain

As I mentioned earlier, the release of AutoCAD 2018 was followed almost instantaneously by the first update, 2018.0.1. At the time of writing, there was no official information about this update. Some information is now available, but more questions have arisen. If, like me, you don’t/won’t/can’t have Autodesk desktop app running on your systems, the only current official way to get at the download is using Autodesk Account (but read the whole of this post before you go there). That’s also how you get at information about the update. Go to Management > AutoCAD > Downloads > Updates & Add-ons. From there, …

AutoCAD 2018 – there’s already an update

If you downloaded and installed AutoCAD 2018 yesterday and don’t/won’t/can’t have Autodesk desktop app running on your systems, you may already have another download to do, because AutoCAD 2018.0.1 is out. At the time of writing there is no sign of this update on Autodesk’s main site, but you can get at it using Autodesk Account. Go to Management > AutoCAD > Downloads > Updates & Add-ons. All that’s downloaded is an executable. No readme, nothing. There is currently no official information about the reasons behind this update, what it includes, what it might affect, how to include it in …

AutoCAD 2017.1.1 Update

Thanks to Jimmy Bergmark, I now know that the controversial subscription-only* AutoCAD 2017.1 Update has itself been updated. Jimmy was brave enough to install and run the execrable Autodesk desktop app and discovered the update update. Rather you than me, Jimmy! Here’s the readme. You’ll need to get at it using Autodesk Account. I note that a bunch of crashes are fixed by this update update. Perhaps that is related to the magical missing AutoCAD 2017.1 crash information? Who knows? The update was apparently released over a month ago on 17 November 2016. Autodesk needs to work out an alternative …

BricsCAD startup LISP bug fixed

In my previous post I have a real problem with BricsCAD, I related my then-latest interaction with the Bricsys support system: Steve Johnson 05-12-2016 05:30 UTC I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions. If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in …

I have a real problem with BricsCAD

To be precise, I have a real problem with writing  about BricsCAD. I’ve written some pretty complimentary things about BricsCAD lately. In the interests of balance, I’ve been intending to write about some of the issues people can expect to deal with when moving from AutoCAD to BricsCAD. Such issues certainly exist. The problem I have with that is that the issues keep going away! Here’s how it usually goes. I find a problem in BricsCAD. I submit a support request. Within hours, I get a meaningful response from a person who understands the issue. Within days, I’m informed it’s …

So what’s actually new in BricsCAD V17?

A big problem I have in communicating the improvements to BricsCAD in V17 is that there are such a huge number of them. This isn’t an AutoCAD 201x-style touch-up masquerading as serious progress, this is a real  upgrade. You know, an AutoCAD V12-style upgrade that veteran AutoCAD users will remember from the good old days before Autodesk got bored and distracted. Dozens upon dozens of new features, improvements to existing features, performance improvements and bug fixes. Lots of stuff that’s genuinely useful. I could write three posts a week on the changes and not be finished by this time next …