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
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
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*:
The most frequently accessed posts on this blog are the AutoCAD 201x – Putting things back to “normal” series. They also attract a lot of comments:
Most Commented Posts
AutoCAD 2013 – An Autodesk Help writer responds – 164 comments
AutoCAD 2012 – Putting things back to “normal” – 158 comments
AutoCAD 2011 – Putting things back to “normal” – 135 comments
AutoCAD 2009 – Putting things back to “normal” – 121 comments
AutoCAD 2010 – Putting things back to “normal” – 106 comments
The … Full post
An interesting new feature of AutoCAD 2017 is Share Design View, which is invoked using the leftmost button on the A360 Ribbon tab or the ONLINEDESIGNSHARE command. The idea behind this command is to create a web-published snapshot of your drawing that can be accessed by anyone with a browser (they’ll need a fairly recent one).
This command works as advertised and provides another option to allow limited access to your design information without providing access to your DWG files. It creates a web page containing a view of your drawing and lets you have the URL (link) so you can access it. You can then share this URL with anyone you want to share the design with. They just follow the URL and can view the design using the Autodesk A360 Viewer (no download required).
Heidi Hewett wrote a fuller description of how it works on the … Full post