I’ve been evaluating BricsCAD for a few years now, and have been looking at it pretty seriously as a DWG-based LISP-compatible AutoCAD alternative for a year or so. A couple of weeks ago, I flew to Munich for the Bricsys International Conference (at Bricsys’ expense – see the Legal page for disclosure) where I learned quite a few things I had failed to notice during my own evaluation of V17. As you may have noticed, I can be pretty hard-bitten and cynical about what CAD companies have to say about their products, but I came back impressed.
The conference and the product itself are not free of flaws, but I have to say the progress Bricsys has shown in developing the BricsCAD product is really quite astonishing. The rate at which serious, worthwhile-to-customers improvements have been made to BricsCAD over the last few releases is huge. Some of … Full post →
My CADLock, Inc. colleague, Owen Wengerd has posted about a fix utility he has written to help clean up drawings infested with the language pack problem discussedhere. I have not yet tested Owen’s utility*, but as this should run in any AutoCAD-based product from 2007 on, it could well be a better partial solution than Autodesk’s Civil 3D-only (so far) patches. Autodesk still needs to sort out its dodgy templates, of course, and should probably provide its own non-Civil 3D fixes, if only to maintain a little corporate self-respect.
As Owen has a long and distinguished history of being consistently and demonstrably better at AutoCAD programming than Autodesk’s own programmers, I’d be tempted to try this one first. However, Civil 3D users should probably apply the patches and updates anyway to help resolve other issues.
In my recent interview of Autodesk Subscription VP Callan Carpenter, he made these statements:
…there is a very small fraction of our revenue that comes from upgrades at this point in time.
We’re down to very low single digits of customers who upgrade, and of those only half of those upgrade 1 or 2 years back. So we’re talking about approximately 1.5% of our revenue that comes from customers upgrading 1 and 2 versions back.
…[customers who upgrade] 1 or 2 [releases] back, a very small percentage of our customer base, less than 2% of our customer base that was buying those upgrades.
Others are calling those numbers into doubt. Deelip Menezes (SYCODE, Print 3D) estimated the numbers of AutoCAD users not on Subscription at 66% (or 43%, depending on which bit of the post you read), by counting the AutoCAD releases used by his customers … Full post →
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.