BricsCAD V17.2 is out. Although there’s nowhere near as much new and useful in this mid-term update as in the full upgrade from V16 to V17, there’s more here than in Autodesk’s last mid-term update, AutoCAD 17.1. There’s even arguably more than in the uninspired AutoCAD 2018 upgrade, including those 17.1 features.
But that’s not the main reason I say Bricsys is schooling Autodesk in how to do mid-term updates. While Autodesk is restricting such updates (including the bug fixes and security updates included in those updates) to subscription and maintenance customers, Bricsys is doing no such thing.
BricsCAD V17 customers who have a perpetual license, even without maintenance (called All-In by Bricsys), will be receiving V17.2 free of charge. Bricsys still considers such users as customers who have paid good money and still need to be looked after, rather than a non-paying irritant, … Full post
Note: due to new information from Autodesk, an updated summary has been posted.
In this series of posts, I’ll examine various payment options for CAD software and compare them with the cost of staying on your Autodesk maintenance contract long-term.
In this third post, I examine what happens if you do something out of the box. Something Autodesk didn’t plan on you doing, and something it won’t like. What if you don’t renew your maintenance and then maybe hop on the subscription gravy train later? What if you don’t renew your maintenance and switch to a non-Autodesk product?
As stated in my first post, staying on maintenance is the baseline with which I’m comparing these options:
Option 1 – stay on maintenance
Assumptions: maintenance cost 20% compound rise annually from 2020
Pros: keep your perpetual license, keep it up to date, retain previous version … Full post
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
It’s been a while since I posted any beginners’ tips, so here goes.
There are several commands in AutoCAD to do with reversing things you’ve done. They are in some cases subtly different and this can confuse newcomers. Here’s what they do:
- U – reverses the last command you used.
- Redo – reverses the last U or Undo operation you performed, if that’s the last thing you did.
- Undo – displays a set of command options that allow greater control over undoing things. (This is rarely used directly by a user, and is more of a programmer’s tool, so I won’t be going into any detail).
- Erase – removes from the drawing an object or set of objects as selected by the user.
- Oops – reverses the last Erase command, even if you have done other things in the meantime. (It also reverses erasures performed by the Wblock command, … Full post
In my previous post I have a real problem with BricsCAD, I related my then-latest interaction with the Bricsys support system:
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 the call working as expected. I’ve chopped down our startup routine so you have an example.
; error : no function definition ; expected FUNCTION at [eval]
Awesome Bricsys Person
05-12-2016 12:32 UTC
There was a regression introduced in V17.1.10 that caused … Full post
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 been fixed internally and the fix will be in the next update. Within a week or two, that update is released. I download and install the updated version. It’s basically a full reinstall, but all settings are seamlessly retained and it’s faster and less painful than an AutoCAD Service Pack … 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
Back in 2010 I asked the question Any BricsCAD users out there? and there were a few of you who had tried to replace AutoCAD with BricsCAD. Most who responded had made the change successfully, others not so much.
Six years on, the situation is different. The fact that you can’t buy a permanent AutoCAD license any more has prompted some Autodesk customers to look more seriously at alternative vendors who do provide that option. Bricsys is one of those vendors, and their DWG-based AutoCAD alternative BricsCAD has improved way more rapidly than AutoCAD over the same time period. No, that isn’t a guess, I’ve been keeping an active eye on things. BricsCAD today is by no means perfect, but it’s impressive in many ways. LISP compatibility and performance are excellent, for example. BricsCAD v16 superior to the also imperfect AutoCAD 2017 in several … Full post
Let’s start the rebirth of this blog on a positive note. I’d like to express my gratitude to Robert McNeel & Associates for what must surely be the most outstanding example of long-term customer service in the CAD industry.
These days, McNeel is best known for the 3D modelling software Rhino. I have heard good things about this product, but have never used it. However, I am a long-term user of another McNeel product, DOSLib. This is an extensive set of functions that adds greatly to the functionality of AutoLISP. It all works very well and has saved me many hours of work that I would have spent reproducing that functionality. Of course, many LISP programmers could write functions to calculate a cube root, or read a text file, or display a date in whatever format you like, or copy files, or generate a GUID, … Full post
As I mentioned earlier, any company that wants to move its customers to the Cloud is going to need the trust of those customers. Three months ago, I started a poll to try to get some measure of how trustworthy you consider Autodesk to be, in terms of doing the right thing by its customers. The results of that poll look pretty awful for Autodesk. Right from the start, the distrusters have outnumbered the trusters by three to one, with the current results showing an overwhelming majority of respondents (77%) not trusting Autodesk.
Why? What has Autodesk done in the past, or is doing now, that leads people to this level of distrust? If you have voted in this poll, I’d like to know your reasons, so please add your comments whichever way you voted. If you think there’s an issue with the question wording and/or its simple … Full post
I would be very interested to hear from any of you who have adopted Bricscad (either partially or fully replacing AutoCAD or AutoCAD LT in your organisation), or at least seriously investigated using the product. This post is aimed at users and CAD managers rather than third party developers, who I expect to cover in future posts.
Why did you investigate changing over? How far have you gone? What are your experiences? What are the pros and cons? How is performance? Reliability? Bugs? Ease of use? Familiarity? Support and other aspects of customer service? Total cost of ownership? Are you experiencing interoperability problems when exchanging drawings with Autodesk software users? How did you go with incorporating in-house customisation and third party tools?
Please add a comment, or if you prefer, email me using my contact form.