Tag Archives: BricsCAD for Mac

Why Bricsys makes the best AutoCAD for Mac

Bricsys has just released BricsCAD V18 for Mac. Here’s the download link and here are the release notes.

BricsCAD V18 is an excellent DWG 2018-based CAD application, and the Mac version lacks little in comparison to the Windows version. It’s so much more capable than the perpetually half-baked AutoCAD for Mac that I struggle to comprehend why anybody with the choice would even contemplate the notably inferior and seriously overpriced Autodesk offering.

That’s not just opinion, it can be supported objectively.

Price first. US prices are shown here for a single standalone license over five years, inclusive of the cost of upgrades. The BricsCAD prices therefore include maintenance (it’s optional); the Autodesk prices are for subscription (not optional). No temporary discounts have been included. I have excluded bargain-basement BricsCAD Classic because it lacks the full set of programming and 3D modeling tools. I have assumed that there will be no price increases over the next five years. Given recent history, that’s probably close to the truth for Bricsys prices. Autodesk, not so much.

Year BricsCAD Pro BricsCAD Platinum AutoCAD
1 970 1330 1470
2 240 240 1470
3 240 240 1470
4 240 240 1470
5 240 240 1470
Total 1930 2290 7350

It’s worth noting that if you want to stop paying Bricsys, you’re left with the latest version to use indefinitely. You can change your mind and get back on the upgrade train later, if you like. That sort of flexibility is long gone at Autodesk, where subscription means no pay, no play. If you stop paying, despite having paid 3.2 times as much for your software over the five year period, you’re left with nothing.

Now, features. You may have noticed that Autodesk is now too embarrassed to list the differences between the Windows and Mac versions of AutoCAD on its web site. The Compare AutoCAD vs. AutoCAD for Mac page is now a shadow of its former useful self, devoid of all detail. If you want to get a reasonable idea of what’s going on with AutoCAD for Mac’s deficiencies, you can check out my post about the 2017 release that lists the missing features.

Alternatively, you can have a look at the equivalent Bricsys comparison page, which you should probably do anyway before spending any money. It’s strange that you now need to visit a competitor’s page to get detailed information about an Autodesk product, but in the CAD world these are strange days indeed.

It’s important to note that the Bricsys comparison page has issues; while the BricsCAD columns are up to date, the AutoCAD columns are a year behind. That page definitely needs an update in order to provide a fair comparison. Don’t rely on it completely (e.g. all of the listed products except BricsCAD V17 for Linux use DWG 2018 as the native format, not DWG 2013), but it will give you an approximate idea. Look at the little red X marks in the rightmost column and you’ll see that a whole bunch of the missing AutoCAD for Mac features, even after all these years, are very significant and their absence could rule out the product for you. Don’t expect much in the way of future improvement. either. AutoCAD for Mac is in maintenance mode, just like the full product.

BricsCAD for Mac is not just more fully-featured, it’s ironically also more AutoCAD-compatible than Autodesk’s effort. For example, try to run a selection of LISP routines in both products. Almost all of it will run just fine in BricsCAD. Anything that uses ActiveX or DCL (dialog box) calls simply won’t work in AutoCAD. You might be all right with some simple routines (if it was written for AutoCAD for DOS then it will probably be fine) but any LISP even moderately sophisticated is going to fail.

BricsCAD for Mac doesn’t just provide capabilities that AutoCAD for Mac doesn’t have and never will, it offers something more than that. It offers a path beyond basic drafting. You can abandon all hope of Revit for Mac – that won’t be happening. AutoCAD-based vertical products? Nope. Inventor OS X? Forget it. But the availability of a product like Bricsys BIM for Mac (not priced above – it’s US$770 extra if purchased seperately) is an obvious drawcard for Mac-happy architects. You can create 3D parametric models on your Mac if you use BricsCAD Platinum, and you can create them without straying far from a familiar AutoCAD-like environment. Sheet metal? Sure (at extra cost).

If you’re a Mac-only person and you’re wedded to Autodesk, you’re not only being ripped off, you’re following a dead-end path. Time to check out the alternatives.

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 are on Windows, because AutoCAD was only Windows. What we have as APIs, and the most important ones are BRX and .NET. If you want to port an application to Mac, it means our API must support that as well. BRX is doing that for 90 to 95%; there are a couple of functions that only work on Windows. For most of the applications, they can port their application to Linux or the Mac without any problems.

Steve: And you support the Visual LISP COM functions as well, right?

Mark: Yes, we cover them and they are also available on Mac and Linux.

Steve: You have a solution there that Autodesk doesn’t, which gives us the strange situation that BricsCAD for Mac is more AutoCAD-compatible than AutoCAD for Mac.

R.K.: AutoCAD for Mac leaves a lot of holes.

Erik: That’s because they rewrote the whole interface for Cocoa, and we didn’t. We are using one code base. You can be more Catholic than the Pope, yeah? If you rewrite AutoCAD completely for the Mac, the result is many holes, no applications possible, it doesn’t help anybody. We’re better off being pragmatic and doing it the way we did it.

Still, we must say that applications availability for Mac and Linux is not much. That has to do with 95% of our sales being on Windows. We expect that might change for BIM, because more architects are Mac users, partly because the first version of ArchiCAD was on Mac, Vectorworks is, so it’s really an Architect’s machine. We expect that maybe for BIM, it might change and we might sell more versions on the Mac.

Steve: Autodesk doesn’t have a competitor there, does it?

Erik: No, absolutely not.

Mark: I should mention that all of our keys are cross-platform. So when you buy a key, you can run them all. So every time you on decide to run on Mac and later on you decide to switch it to Windows, we don’t have any problem. You can switch whenever you want, from one to the other, on to Linux if you want.

Erik: Again, choice. It’s up to the users.


This is the complete set of links to this interview series: