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

Huge PDFs? AutoCAD 2017.1.1 could be to blame

Autodesk has yet again demonstrated why continuous automatic updating is no panacea for avoiding CAD update disruption. On the contrary…

If you have noticed some of your PDFs exported from AutoCAD getting huge and unwieldy lately, AutoCAD 2017.1.1 could be to blame. Try uninstalling it using Programs and Features > View Installed Updates and see if the problem goes away. It may also be possible to work around this by going into PDF options and turning on Include Hyperlinks. Source: The Swamp.

Here’s one possible* install history:

  • You install AutoCAD 2017. This defaults to also installing Autodesk desktop app. If this works on your system and you leave it on there doing its thing and consuming your resources, it will attempt to automatically keep your Autodesk software up to date.
  • Autodesk desktop app installed AutoCAD 2017.1. You like this because it has added a couple of nice features. … Full post

I have a real problem with BricsCAD

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

Hotfix for AutoCAD 2017 SP1 Autoloader bug

As reported earlier, AutoCAD 2017 SP1 breaks third-party add-ins that use the officially approved Autoloader mechanism. Autodesk is to be commended for acting quickly to produce a hotfix for this. In order to make this hotfix available quickly, Autodesk has taken the very unusual step of allowing a third party to distribute it. See this post from Jimmy Bergmark, who pointed out the bug in the first place. Kudos to whoever at Autodesk made the call to think outside the box to do this. It’s a very un-Autodesk Corporate thing to do, and particularly commendable for that very reason.

It’s important to note that because of the way Service Packs are now handled in AutoCAD and the vertical products based on it, this SP1 bug affects all of those products, not just base AutoCAD. Here is the list of affected products*:

AutoCAD 2017 Service Pack 1 is out but you probably don’t want to install it

As reported by Jimmy Bergmark, AutoCAD 2017 SP1 will break add-ins that use Autodesk’s built-in autoloader mechanism. It looks like it’s a problem caused by third party applications, but it’s not. It’s entirely Autodesk’s fault. The only fix at this stage is to uninstall SP1.

It’s astonishing that Autodesk would release a service pack like this, introducing a nasty bug that will break customers’ existing functionality. This reminds me of the comedy of errors that was AutoCAD Release 13 with its multitude of updates, many of which introduced new bugs as well as fixing others. AutoCAD 2017c4a, anyone?

If you needed any more evidence that automated continuous updates from Autodesk are A Bad Idea, here it is. What a crock.