AutoCAD 2018 licensing crash – another reason to avoid subscription

Autodesk has released an update to fix the following AutoCAD 2018 problem:

Product users of version 2018 Autodesk single-user subscriptions may experience an intermittent crash. The crash occurs when it has been more than 24 hours since the last successful authorization check and there is intermittent or no internet connection, or the licensing authorization server is unavailable. The licensing authorization check occurs in the background and is completely unrelated to activities the user is performing at the time of the crash.
A fatal error message may be shown by the product. For example:

FATAL ERROR: Unhandled e06d7363h Exception at ee563c58h

 
Links:

Note that this crash only afflicts subscription (rental) single-user (standalone) customers. People with perpetual licenses don’t have to put up with the multiple additional points of failure caused by the subscription licensing system insisting on phoning home every 30 days. Yes, even if you pay for three years’ subscription up front, you’ll still need a working Internet connection every 30 days if you want to keep using the product.

At least, Autodesk has been saying it’s only once every 30 days (as if that wasn’t bad enough). The information provided with this hotfix tells a different story. What is the license server doing phoning home 24 hours after the last successful authorization check? Enquiring minds want to know.

No criticism of Autodesk is implied for providing this hotfix. As always, I commend Autodesk for fixing up problems as they arise. The basis of my criticism is the hotfix being necessary in the first place. It’s caused by Autodesk inflicting unnecessary complication on its customers for its own internal reasons. This one fails the “how does this benefit the customer?” test big-time.

The single-user subscription licensing mechanism has been a crock from day one, especially for CAD Managers of multiple users who have to deal with its onerous requirements. It’s an astonishingly poor design, very badly implemented. Even with this particular crash fixed, it’s still a crock.

The big Bricsys interview 10 – platforms

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh.

In this post, R.K. McSwain asks about BricsCAD running on three different platforms. Erik explains why BricsCAD for Mac (and Linux) is so much more complete than AutoCAD for Mac, which has more holes than a block of Swiss cheese.

R.K.: Do all three platforms (Windows, Linux, Mac) contain the same functionality?

Erik: Yes. Sometimes it’s a bit hard with the Mac to bring it along but so far, so good. The only problem sometimes is in the APIs.

We are using wxWidgets and not the Microsoft classes. This gives us the ability, with the same source code more or less, to serve Mac, Linux and Windows. By far Windows is the most important one. By history, all the applications …

Full post

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 …

Full post

AutoCAD 2017 for Mac released, still half-baked

AutoCAD 2017 for Mac and AutoCAD LT 2017 for Mac have been released. Here’s a video highlighting exciting and innovative new features such as drawing and layout tabs. Despite such stellar advances, it’s safe to say that AutoCAD for Mac remains half-baked, even after all these years. Don’t say I didn’t warn you.

According to Autodesk, these are the features missing from AutoCAD 2017 for Mac:

LAYDEL, LAYMRG, LAYWALK and LAYVPI
Tool palettes
New layer notification
Navigation bar
ShowMotion
Ribbon*
DesignCenter**
Sheet Set Manager***
Steering wheel
Feature finder for help
Model documentation tools
Dynamic block lookup parameter creation/editing
Table style editing
Multiline style creation
Digitizer integration
Geographic location
Simplified, powerful rendering
Material creation, editing, and mapping
Advanced rendering settings
Camera creation
Point cloud

Full post

AutoCAD 2013 for Mac – the holes live on

A couple of years ago, I reported on the missing features in AutoCAD 2011 for Mac. While some generous souls were prepared to accept something half-baked as a first attempt, even that excuse doesn’t wash when it comes to a third iteration. So how well is Autodesk doing at filling those holes? Decide for yourself. Here’s an updated list of missing features in AutoCAD 2013 for Mac:

  • Quick Properties Palette
  • Layer State Manager
  • New Layer Notification
  • Various layer commands including LAYCUR, LAYDEL, LAYMRG, LAYWALK, and LAYVPI
  • Autocomplete doesn’t work entirely properly, including offering commands that don’t exist
  • Filter
  • Quick Select
  • DesignCenter
  • Tool Palettes
  • Navigation Bar
  • ShowMotion
  • Sheet Set Manager (but there is Project Manager)
  • Model Documentation Tools (but at least now there are object enablers)
  • Geographic Location
  • Table Style Editing
  • Hatch Creation Preview
  • Multiline Style Creation
  • Digitizer Integration
  • Change Space
  • Express Tools
  • Material Creation, Editing, and Mapping
  • Full post

Autodesk Cloud – don’t panic, business as usual

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

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

(As an aside, I must say this was a much more worthwhile announcement than the ridiculously over-hyped DE8.16N thing. So I was supposed to get excited about a routine upgrade of …

Full post

AutoCAD for Mac Update 2

As reported on Without a Net, there is a second update for AutoCAD 2011 for Mac. This will be welcome news to those of you who have discovered that AutoCAD crashes when using Copy/Paste after installing the 10.6.7 OS X update.

If you haven’t applied Update 1 yet, you will need to do that first. As always, read the readme before applying the update itself.

Full post

Autodesk for Mac – the hole story

You may remember my pre-release speculation about what was likely to be missing from the Mac version of AutoCAD 2011. It turns out that my list was pretty accurate as far as it went, but very incomplete.

In a move that I can only applaud, Autodesk has now published its own list of missing Mac features. It includes this statement:

Although AutoCAD 2011 for Mac is based on AutoCAD 2011, it was written to be a native Mac application. As such, it is a new and separate product and not simply a port from the Windows version. In the first release of this new product, there are some features and functionality that exist in AutoCAD 2011 that are not yet available in AutoCAD 2011 for Mac, including (but not limited to):

This is followed by a list of over 80 holes in the product. Many of them are …

Full post

Executive summary of Deelip’s AutoCAD for Mac interview

Deelip has just published an extensive interview with several Autodesk people about AutoCAD for the Mac. Deelip had a good set of questions and I suggest you read the whole thing, but if it’s all too tl;dr for you, then here is the lazy reader’s version of what Autodesk had to say:

  • The AutoCAD code was split up into 3 sections: the core CAD engine (platform-independent), the Windows-specific (MFC) parts and the Mac-specific (Cocoa) ones.
  • AutoCAD for Mac is incomplete. Choosing which features to leave out was done with the aid of CIP (oh, dear) and Beta feedback. (Hang on a minute, I thought CIP said most people were using the Ribbon…)
  • No comment on when or if AutoCAD for Mac functionality will catch up with its Windows counterpart.
  • No comment on the stability or performance of the Mac version.
  • Buying Visual Tau wasn’t a …

    Full post

Apple – Autodesk history revisited

In a post on WorldCAD Access, Jay Vleeschhouwer makes some reasonable observations. However, the timing of the 1990s Autodesk / Mac history looks all wrong to me. Jay quotes himself from a 2008 note:

…until about the mid-1990s Autodesk did have a reasonable presence on the Mac … commitment waned when Apple’s fortunes faded a dozen or so years ago

The last of the original Mac AutoCADs was Release 12, a 1992 product. Apple market share continued to increase after that; indeed, 1994 was a bumper year. However, Autodesk’s commitment had already vanished by then, and its 1994 product, Release 13, had no Mac version.

Apple’s fortunes did indeed fall away “a dozen or so years” before Jay’s note, largely as a result of the success of Windows 95. But this decline could not have been the cause of Autodesk’s lack of commitment to Apple; by that time the …

Full post

AutoCAD for Mac – what’s missing?

According to Autodesk, the forthcoming OS X version of AutoCAD has “many of the powerful AutoCAD features and functionality.” So what doesn’t it have? What are the holes? Autodesk hasn’t bothered to let me know a single thing about this software, so I guess I’ll just indulge in some irresponsible and uninformed speculation, based on what I can glean from marketing materials and various better-informed sources. I could have just asked, but who knows if I would have ever got any real answers? Besides, this way is more fun.

First, here’s a quick list of some things that don’t appear to be missing, but which might have been lost in translation:

  • Command line (in fact, the Mac one appears to be better than the Windows one).
  • Xrefs.
  • 3D, including visual styles and rendering.
  • Some kind of Quick View Layouts and/or Drawings feature.
  • Navcube.
  • Constraints.
  • Dynamic Input.
  • Selection highlighting.
  • LISP (at least …

    Full post

AutoCAD 2011 for Mac announced

According to Macworld, Autodesk has now made its worst-kept secret, AutoCAD for Mac OS X, official. There are also goodies for those with cute little rectangles:

Autodesk also announced that the new Mac version of AutoCAD would be accompanied by the AutoCAD WS mobile application, a new app for iPad, iPhone, and the iPod touch…

When?

AutoCAD for Mac and the AutoCAD WS mobile application will be available in North America and Europe sometime between August and October. Users can pre-order the app starting Wednesday, September 1.

Huh? August is pretty much over. September or October, then.

Full post

Does Autodesk discuss future plans?

According to Shaan, Autodesk does not discuss its future plans. Or does it? In a comment, Ralph reckoned it does. Putting aside technology previews and various NDA-bound circumstances (e.g. Beta testing), can you think of cases where Autodesk has revealed what it intends to do in future? Here are a few off the top of my head:

  • I’ve been to AU sessions dating back to 1995 that pretty much give away the contents of the next release of AutoCAD, using a vague cover-my-butt session title and a disclaimer at the start of the session. I understand that these days, attendees need to sign an NDA before entering such sessions.
  • Last year in San Francisco, an international blogger audience was given all sorts of information about Autodesk’s future directions (preceded by a similar disclaimer), with no NDA and nothing off the record. I assume something similar happened at this …

    Full post

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 …

Full post

AutoCAD for Mac under construction

Despite it being A Bad Idea, it look like Autodesk is going ahead with making some kind of OS X variant of AutoCAD, as has been hinted at for a while now. Owen Wengerd has pointed out a few dead giveaways in the AutoCAD API.

Another giveaway is the move to the browser-based Help system. OK, it may perform hopelessly and have terrible functionality, but hey, it’s platform-independent! If you still doubt my assertion that the development of AutoCAD for Mac would be a bad thing for AutoCAD, just go and search for a few things in the new AutoCAD 2011 Help system. Then go back to an earlier release (one that uses Windows-specific Help) for a comparison. Once you’ve seen how platform-independence has “improved” Help, just imagine that level of “improvement” applied to the rest of AutoCAD.

Full post

AutoCAD for Linux – another bad idea

I often see calls for Autodesk to support AutoCAD on Linux. Just like AutoCAD for the Mac, while I can sympathise with the users of that OS, I think a native port of AutoCAD for Linux would be a bad idea. Again, I think it would be bad for everybody: Autodesk, AutoCAD for Windows users, and most of all, AutoCAD for Linux users.

Why? First of all, for most of the same reasons I gave for the Mac port. Autodesk hasn’t just failed in the past with AutoCAD for the Mac, it has failed with AutoCAD for Unix, too. I remember Autodesk being very enthusiastic about the Sparc port in particular (AIX, too). I know personally of customers who were caught up in that enthusiasm and invested heavily in a Unix environment, only to bitterly regret it a few years later when Autodesk abandoned them. Would this happen again? …

Full post

AutoCAD for Mac review in Cadalyst (circa 1989)

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

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

Is there anybody out there with a complete …

Full 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 …

Full post