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 year. So I’m going to be lazy. I’ll pick out a few features for future posts but for the big picture I’ll point you to the official list. This isn’t a marketing document, it’s a technical list of terse descriptions of changes (to the Windows version only – … Full post
The most heavily commented post on this blog is AutoCAD 2013 – An Autodesk Help writer responds, featuring Dieter Schlaepfer‘s response to posts and comments here about AutoCAD 2013’s Help. I don’t always agree with Dieter but I respect him enormously, and not just because he was brave enough to stick his head above the parapet in a hostile environment. Dieter is a principal technical writer at Autodesk with many years’ experience and is therefore responsible for large amounts of documentation content. You’ve almost certainly read his work.
I’ve been critical of AutoCAD’s Help system since it was broken in 2011, and I make no apologies for that. The Help system sucked then, it sucked even worse in 2013, and it continues to suck badly in 2017. None of that’s Dieter’s fault. It’s the Help engine that’s at fault, or to be more accurate the Help … Full post
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
I’d like to thank Steve for the opportunity to write this guest post. My post doesn’t necessarily represent Steve, nor does it represent any company. It’s strictly a personal point of view. The purpose of this post is to prompt discussion and debate, and get your opinion.
Recent discussion on this blog has focused on Autodesk and its many changes over the past few years (upgrade pricing, policy changes, term-only aka rental licenses, move to the cloud, etc.), and there’s been a lot of skepticism. If we stand back and look at the landscape, though, Autodesk is not alone. True, they’re moving faster and more aggressively than their competitors, but many software companies are making similar changes.
Change can be disruptive, it can have positive and negative impact, and there can be winners and losers. But … it’s inevitable, and it’s better to understand change than to fight it. To … Full post
…the fact that one of the Express Tools finally got an update. Not just a minor maintenance tickle or mere absorption into the core code, either. A real update, resulting in not only bug fixes but genuinely useful improvements in functionality.
A little background on Express Tools might help put this into context. The history goes back to 1992 and AutoCAD Release 12. In addition to an impressively full set of paper manuals, people with Release 12 (great value at US$500 to upgrade from any earlier release) obtained a Bonus CD containing 2605 files of free add-on goodness. Fonts, LISP, DOS and Unix utilities, sample drawings, demos, all sorts of stuff. Remember that just popping on the web to grab that sort of thing wasn’t really an option at the time, so this CD was quite a big deal.
In preparing to write something about the AutoCAD 2017.1 non-subscription-only update, I came across something slightly strange. Google AutoCAD 2017.1 crashes and you will probably see something like this:
What happens if you click that link? Nothing useful. You’re just taken to the landing page for the Autodesk Knowledge Network. The Google cached version of the link takes me to 404 land. Searching within the Autodesk Knowledge Network doesn’t produce relating to the crash in the original link, which seems to be language-pack related. The search wasn’t entirely fruitless, because I did discover that 2017.1 breaks linetype preview images for those of us who prefer a light user interface. But of … Full post