Tag Archives: AutoCAD

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 3, parts on demand

This is the third post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about using BricsCAD as a mechanical and structural parts library for your AutoCAD users. As I mentioned in my last post in this series, I was writing a client-specific AutoCAD 3D training course recently. To demonstrate the concept of revolving profiles, and also to compare and contrast different styles of solid creation, I wanted to use a ball bearing as an example. The easiest way for me to get hold of an accurate example ball bearing model was to fire up BricsCAD (a few seconds) and select the part from the Standard Parts panel (a few more seconds).

It gets inserted as a block. After explosion to reduce it to 3D solids, I could then slice it in either BricsCAD or AutoCAD to form the basis for my example. I could save it at any stage in BricsCAD and open it in AutoCAD to continue to work on it seamlessly. What I can’t do is simply copy and paste from one application to another; you do need to save the DWG. You can then open it in AutoCAD or access the blocks using AutoCAD’s DesignCenter palette; if you’re doing this a lot you might want to point DesignCenter to a scratch DWG you keep handy for this sort of parts exchange.

There are currently 13 sets of standards:

Although you may already have your own parts library, having access to a wider range of international standards may prove useful. Aussie steel sections? Go for your life, mate.

Just how much stuff is available? A lot. Each of the sets of standards has multiple sections, each section has many parts, and many of the parts have many sizes. Depending on the part, other parameters (such as bolt length) may also be available for a given size.

Here’s the full Standard Parts panel in action, in this case selecting a nut.

BricsCAD Pro and Platinum have 3D parametrics built in (and given the minor extra cost I’d suggest going for Platinum), so it’s quite feasible to use it as the basis for your own 3D parts library. If you’ve built up a few 2D dynamic blocks in AutoCAD, you’ll be quite capable of doing the same thing in 3D in BricsCAD. The methods are different but straightforward enough to teach yourself.

As pointed out in a comment by James Maeding, you can set up a network license or two and install BricsCAD on everybody’s PC, giving everybody access to the goodies without excessive cost. Bear in mind that like Autodesk, Bricsys charges a premium for a network license over a standalone one. Unlike rent-or-go-forth Autodesk, Bricsys allows you to have a perpetual license and the total cost of ownership is substantially lower.

By the way, this series isn’t theoretical, it’s all based on stuff I’ve tried out in the real world. For example, the network license software will happily coexist with Autodesk’s network license software on the same license server. The services ignore each other; no clash, no problem. My experience is that it works just fine on a virtual server.

It will cost you a few minutes to download and install of an evaluation BricsCAD and check out the included parts content for yourself.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 2, 3D operations

2 Replies

This is the second post in this series where I explain why this statement holds true:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

This post is about using BricsCAD to do things to help out your AutoCAD users who are having problems with 3D operations. Why would you bother using BricsCAD to mess with AutoCAD 3D models? Because sometimes AutoCAD can’t do stuff with them, and BricsCAD can.

If you have a user who finally asks for help after fighting AutoCAD for ages trying to get an operation to work such as an awkward fillet, a self-intersecting extrusion or a direct edit that doesn’t want to move, you have a couple of options:

fight the same fight yourself in AutoCAD, eventually discover that the user was right, and then construct an excruciatingly awkward workaround; or
fire up BricsCAD and see if you can do it there. There’s a good chance it will. If it does, hand the DWG back to the user with a smug look on your face. If it doesn’t, construct an awkward workaround in BricsCAD, because it will almost certainly be faster than doing the same thing in AutoCAD. Direct editing of 3D solids is more flexible and easier in BricsCAD; the Quad Cursor helps a lot.

I’ve been writing a client-specific AutoCAD 3D training course recently, and going through the exercises I’ve developed has been instructive. I’ve lost count of the number of times I’ve thought, “Man, this would have been so much easier in BricsCAD.” That’s before we get to the 3D parametrics that BricsCAD has had for a while and which AutoCAD never will.

Why is BricsCAD so much better than AutoCAD at making 3D work well? Because it has to be. When you base your entire product line (including BIM, parametric 3D, sheet metal and a host of other uses covered by 3rd party developers) on a single DWG-based 3D engine, that engine has to be robust, powerful, efficient and fast.

It’s not as if Bricsys can say to somebody struggling with performing 3D operations in BricsCAD that they should be using Inventor or Revit instead. That cop-out is unavailable. It has to just work.

Fortunately, Bricsys has acquired a small group of genius-level experts in this area, and holds on to them rather than dumping them when they get too experienced. It shows. Overwhelmingly, it just works.

It will cost you a few minutes to download and install of an evaluation BricsCAD and confirm this for yourself. It’s well worth it.

There are exceptions, of course. Nothing is perfect, and you will come across the occasional glitch. But those exceptions are definitely rarer than in AutoCAD. My experience also tells me that if you report those exceptions, there’s an extremely good chance that they will be fixed, and quickly. Bricsys ain’t Autodesk.

Why every AutoCAD CAD Manager should have a copy of BricsCAD – part 1, fixing drawings

2 Replies

Here’s a mega-tip with a lot of experience behind it:

As a CAD Manager looking after AutoCAD users, or a power user looking after yourself, it’s worth your while to have a copy of BricsCAD handy.

Why? There are too many reasons to fit in one blog post, so I’m going to do a mini-series. The first post is about using BricsCAD to fix up drawings that are giving your AutoCAD users problems.

One of the things that surprised me most when evaluating BricsCAD as a potential replacement for AutoCAD was that my expectations were wrong when it came to the reliability of opening DWGs. Over the years, I collected a variety of DWGs that gave various releases of AutoCAD some problems. Some of those problems occurred while performing some kind of editing or processing, while others prevented AutoCAD from opening the drawing at all. I was expecting BricsCAD to have all those problems, plus perhaps some additional incompatibilities of its own.

What happened was the opposite. I don’t think I came across a single drawing that AutoCAD could open but BricsCAD couldn’t. On the contrary, BricsCAD was much more forgiving than AutoCAD, breezing through the process of opening drawings that had problems that originated in AutoCAD. Maybe 80-90% of my “problem” drawings were problems for AutoCAD alone. In many cases an AUDIT in BricsCAD and a re-save was enough to make the problem go away in AutoCAD. In other cases I could use BricsCAD to recover the unrecoverable using the traditional methods of WBLOCK, saving as an earlier release, saving as DXF, binary search (I may do a later post on exactly what that means), and so on.

Note that you may be able to obtain similar results using other DWG-based products such as DraftSight, ZWCAD or even the free BricsCAD Shape. However, I don’t have the experience with those products to be able to confirm that. Autodesk’s DWG TrueView, being a cut-down AutoCAD, tends to have the same problems as AutoCAD.

One thing that was particularly pleasant about using BricsCAD to fix problem drawings was the speed at which it could be done, because of BricsCAD’s generally superior performance. Closing and opening AutoCAD is painfully slow these days as the bloat gets worse, so having a product that fires up quickly is very handy.

Also handy is the availability of tools within the product that make it easier to locate and fix problems. Of particular importance is the Drawing Explorer, which provides a consistent and efficient interface that provides access to over 20 different types of aspects of a drawing (e.g. layers, linetypes, text styles, etc.):

One example arose showing how useful this is, when my users were having an intermittent problem with some drawings locking up AutoCAD 2015 on open. Some trial and error made it possible to discover that the trigger for this was the existence of a text style (any text style) with a bigfont attached, where the bigfont SHX file did not exist. It was possible to fix this in an earlier or later AutoCAD release, which the users may or may not have available to them, by opening the drawing, using the STYLE command, then using that dialog box to go through each text style one at a time, looking for bigfonts.

It was much easier to quickly fire up BricsCAD, use the STYLE command which opens the Drawing Explorer in the Text Style section, and see all of the text styles laid out at once (see above). It was very efficient to quickly look for recalcitrant bigfonts and make them go away, or to see instantly that bigfonts weren’t the problem.

Similarly, the consistent, searchable and efficient interface of the BricsCAD Settings dialog makes it easy to check the values of any settings that you suspect may be triggering the problem in AutoCAD:

As a CAD Manager, it’s definitely worth your while to do the quick download and install of an evaluation BricsCAD. My experience in dealing with Bricsys is that requests for extensions for evaluation purposes are usually accepted, so you probably won’t have to give up your valuable tool as soon as your 30 days are up.

Once you’ve determined that it really is an invaluable tool to have around, the cost of entry is low enough to make it relatively easy to justify the investment. You won’t need to recover many drawings to get your money back.

The game has changed – Robert Green migrates to BricsCAD

10 Replies

Is anybody left who still thinks BricsCAD isn’t a serious replacement for AutoCAD? If that’s you, perhaps the latest news might make you take it seriously. No, not the Heidi Hewett news. Even more recent news than that!

Robert Green, CAD Management guru, Cadalyst writer and consultant (not to mention a rather good guitarist) has been announced as the first Bricsys Certified Migration Consultant.

Image courtesy of Bricsys

Read all about what Robert has to say on this Bricsys blog post.

Anybody who has been reading this blog for the last few years will be surprised by none of what Robert has to say in that blog post. It’s not merely a repeat of what I’ve been saying for some time now, it’s all factually correct and easily verifiable by any competent CAD Manager.

I’ve been there and done that. I’ve gone through the process of taking a very complex custom AutoCAD environment, applying it to BricsCAD and giving it to my users. They loved it. No training was required to work as usual. Most things happened quicker, more conveniently, or both, starting right from the speedy installation. Once the product is in place and established, training can then be applied to take advantage of the places where BricsCAD is ahead of AutoCAD.

If you’re a CAD Manager where AutoCAD is used and you haven’t checked out BricsCAD yet, it’s about time you did.

This might come as a shock to those who see Autodesk domination of DWG CAD as a permanent fact of life, but the game has changed. AutoCAD’s stagnation and comments by senior figures show that the former flagship is clearly unloved by the powers within Autodesk. AutoCAD LT, even more so. An unimpressive AutoCAD 2019 shows that major improvements can no longer be expected in exchange for your ever-increasing annual payments, and with large numbers of people having been offloaded from the research and development teams, who would do it anyway? Meanwhile, BricsCAD development shoots ahead.

Thanks to decades of hostility towards customers that has only accelerated in recent years, Autodesk can’t even rely on customer loyalty for survival. When there’s a serious competitor that offers an easy migration path, the inertia that has kept Autodesk alive so far in the DWG space is no longer enough. The feeling among industry observers I meet is that Autodesk is in a decline of its own making. The only debate is whether that decline is temporary or terminal.

Back to Robert et al. Autodesk has lost many good people, and Bricsys is gaining them. The momentum is clearly with the Belgian company. Anybody want to run bets on who the next big name defector will be?

Why One AutoCAD is smart strategy

4 Replies

OK, so Autodesk may have blown the AutoCAD 2019 rollout, triggering an apology from CEO Andrew Anagnost.

OK, AutoCAD 2019 may have the smallest set of significant advances in the history of AutoCAD releases. If you’re wondering, I give it 1/10. The “there can be only one” hype could easily refer to meaningful improvements to the product per year. This year’s improvement is… drawing compare!

Still, AutoCAD 2019 is a significant release for reasons beyond the content of the core product. An examination of the One AutoCAD strategy reveals a collective corporate mind that’s smarter than it’s being given credit for.

In case you’ve missed it, the idea behind One AutoCAD is that if you subscribe to AutoCAD, you can now also get a bunch of vertical variants of AutoCAD thrown in, renamed as “Toolsets”. You need to ask for it, and it’s for renters only, no perpetual license owners need apply. Oh, and Civil 3D isn’t part of the deal.

This concept has been received less than enthusiastically among respected independent observers such as Ralph Grabowski and Robert Green. I’m going to go against the trend a little and point out several ways in which this is a smart move for Autodesk.

It represents the first time Autodesk has had anything of substance to positively differentiate between maintenance and subscription. Until now, it’s all been negative: give away your perpetual licenses to avoid forthcoming maintenance price increases.
It provides some substance to Dr Anagnost’s “give us a year to show the value of subscription” request to customers. OK, it may have taken a lot more than a year, but at least it’s now possible to point to something that customers can gain by subscribing, rather than having the embarrassment of an empty promise hanging around.
It acts as an effective distraction from yet another price rise (7% on top of Autodesk’s already sky-high subscription costs). Yes, this new price still applies even if you don’t use the toolsets. Yes, it still applies even if you’re a Mac user who doesn’t have these toolsets available.
It will almost certainly be used as justification for future subscription price rises. How can you complain about a few more dollars when you get all those products included in the price?
This stuff has already been developed to a point that Autodesk considers mature (web apps excluded), and it isn’t costing Autodesk anything to “give it away”.
It means that the glacial or non-existent rate of improvement of AutoCAD and its variants suddenly appears less important. How can you complain that nothing worthwhile has been added to your AutoCAD variant this year when you now have access to hundreds more commands than you used to have? This line has already been tried with me on Twitter.
It provides a marketing counter-argument against competitors who sell DWG-based AutoCAD-compatible products that provide above-AutoCAD standards of functionality (e.g. BricsCAD).
If an increased number of users start using the vertical variants, there will be increased pressure on those competitors to handle the custom objects created using those variants. This will act as a distraction and reduce the ability of those competitors to out-develop Autodesk at the rate that has been occurring for the past few years.

There are a couple of flies in Autodesk’s One AutoCAD ointment:

Critical mass – it has yet to be seen how many customers are so won over by this concept that they sign up for it. Remember that it’s only available to a minority of customers anyway, and if the bulk of customers remain reluctant to give up their perpetual licenses then all this is moot. If the move-to-rental numbers are small, then the anti-competitive nature of this move is negated. The marketing gains still apply, though.
Interoperability – traditionally, the AutoCAD-based verticals add custom objects to the core AutoCAD objects, which when opened in vanilla AutoCAD or another vertical, appear as proxy objects that either don’t appear or will provide very limited access. Improved but still limited access can be provided if Object Enablers are installed. Object Enablers are not always available for the AutoCAD variant you want to use. LT? Mac? Old releases? Forget it.This has always been a highly unsatisfactory arrangement. I have worked for a company that explicitly prohibits drawings containing proxy objects and rejects any it receives, and that has proven to be a smart policy. Also, the vertical variants of AutoCAD have always had hidden DWG incompatibilities built in. AutoCAD 2015 user? Try to use a DWG file that has been created in a 2017 vertical variant. Good luck with that, even though all those releases supposedly use 2013 format DWG. Paradoxically, you can expect to experience much better DWG interoperability with non-Autodesk products and their add-ons than you will with AutoCAD and its verticals, because the non-Autodesk products are forced to work with AutoCAD native objects. It remains to be seen how, when, or even if Autodesk addresses these issues.

In summary, this strategy has potential to significantly benefit Autodesk. Will it work? That will largely depend on how many customers are prepared to put aside their mistrust enough to hand over their perpetual licenses to Autodesk. That mistrust is mighty large (Autodesk’s been working hard for years on building it up) and recent sorry-we-broke-your-rental-software events have reiterated just how valuable those perpetual licenses are.

Autodesk has produced what it considers to be a very attractive carrot. Is it big and juicy enough to attract you?

CAD Nostalgia Video

6 Replies

For the first video in the new cad nauseam YouTube channel, I’ve had a bit of fun. I unearthed a bunch of my old stuff to show you. Does any of this take you back? Enjoy!

How to sign your LISP files

Leave a reply

This post follows on from Why digitally sign your LISP files? and How to obtain a digital signature to sign your LISP files.

In the first post, I explained why you might want to digitally sign your LISP files. In the second, I explained how to obtain and install a digital signature. This third and final post in the series assumes you have done all that and now want to sign your files. There are two methods available to you, using a dialog box or command-line interface.

Signing LISP using the AcSignApply.exe dialog box

Autodesk has provided a utility called Attach Digital Signatures for years. This was provided to sign drawings, zip files, etc., but the ability to sign LISP files was added in AutoCAD 2016. Don’t go using the 2015 version or you’ll have a very frustrating time! You can invoke this utility using the Windows Start Menu:

You can also make your own desktop shortcut if you like. The executable is stored at (XXXX is your AutoCAD release number):

C:\Program Files\Autodesk\AutoCAD XXXX\AcSignApply.exe

AutoCAD doesn’t need to be running when you start the application. Here’s the interface:

Half way down, there is a list of code signing certificates that you can use. You should see the one you obtained and installed earlier in this list. If you don’t see it listed it may not have been installed correctly. It’s possible to install a public key version of a certificate and see it listed in the Windows Certificate Manager, but that won’t help you sign code. You need to install the private key version in order to be able to sign things. If you do the wrong kind of export from your browser, or if you use the wrong browser to obtain and export the certificate, you may have installed the public key version. In such a case, you will need to contact the certificate provider for help. I have found that the online chat help provided by Comodo is excellent in such cases. Yes, I know this because I got it wrong the first time!

Assuming your certificate is visible, click on that line to select it. You can add files to the pane at the top left using the buttons on the right side or by simply dragging and dropping files onto the pane from Explorer. But wait! Before you do that, make sure you have a safe unsigned copy of all your files. Applying the signatures is a modification process; you are left with only the signed version of the files.

LISP files with the LSP, MNL, FAS, or VLX file extensions can be selected and dragged into the pane. As mentioned in the first post, there’s a bug in the original iterations of AutoCAD 2016 and AutoCAD 2018 that prevents signed VLX files from working, so I would advise against creating them. If you need to distribute signed DCL-based code and don’t want the LISP source visible, you will need to provide a signed FAS instead, along with a DCL file that’s either provided alongside the FAS or created on the fly by your code. Yes, this is a pain.

Note that at the time of writing, you can’t sign CUI, CUIx, DVB, JS, PGP and SCR files.

Once you have selected the certificate to use and the files to sign, select a source for the time stamp and enter a description in the Comment box (optional). Pick the Sign Files button and you’re done.

Signing LISP using the AcSignTool.exe command-line utility

This utility isn’t provided with AutoCAD, but you can download it here. It doesn’t require AutoCAD, which means you can sign LISP files even if you don’t have a copy of AutoCAD 2016 or later.

Once you have downloaded and unzipped the file, place the files somewhere handy. If you make a shortcut to cmd.exe that starts in that location, you can run this command to see all the options:

acsigntool.exe /?

Usage is usually as follows:

AcSignTool -sign /file:[inputfile] /cert:[certificate] /time:[timestamp] /comment:[description]

Here’s an example:

AcSignTool -sign /file:"X:\ToSign\MyCode.lsp" /cert:abcdef1234567890 /time:1 /comment:Hello

The resultant file should be the same as with the dialog box interface. If it’s a raw LISP file, a large comment like this will be placed at the bottom of the file:

;;;-----BEGIN-SIGNATURE----- ;;; /gcAADCCB/oGCSqGSIb3DQEHAqCCB+swggfnAgEBMQ8wDQYJKoZIhvcNAQELBQAw ;;; IE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD ;;; CwYJKoZIhvcNAQcBoIIFQzCCBT8wggQnoAMCAQICEQCyNMZT2aa05avqeC3j+F3p ;;; YQBuAGQAYQByAGQAcwAgAGEAbgBkACAAVABlAGMAaABuAG8AbABvAGcAeQAgACgA ;;; MA0GCSqGSIb3DQEBCwUAMH0xCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVy ;;; QSBMaW1pdGVkMSMwIQYDVQQDExpDT01PRE8gUlNBIENvZGUgU2lnbmluZyBDQTAe ;;; bnB31gkc9o/M8YjPdGVjQG0VS96RVf/WtkmGugV2n1Fv4wWXBLA7n410yglqSZh9 ;;; NOK2Ya1KFx4trccIHV1oAFN+BCKzSf6J/HdVkmCcy4TEPcrxSzZsi//slm2o9EHl ;;; mwdm6Quhw1wMT8+iRmJNO4ofwuKfBwyE28ZIK4q+zorJPNwiK2o43CmNJViU5SQD ;;; M9ImVtHTTtdAR1Iln+wEtg/4xgwj5KWuxoUJ22OJ/K0A8IcnxqGBujCBtwYDVR0O ;;; Fw0xNzEwMDQwMDAwMDBaFw0yMTEwMDQyMzU5NTlaMIGAMQswCQYDVQQGEwJBVTEN ;;; MAsGA1UEEQwENjE1NTELMAkGA1UECAwCV0ExEjAQBgNVBAcMCVdpbGxldHRvbjEV ;;; A1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1JT ;;; QUNvZGVTaWduaW5nQ0EuY3JsMHQGCCsGAQUFBwEBBGgwZjA+BggrBgEFBQcwAoYy ;;; aHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPUlNBQ29kZVNpZ25pbmdDQS5j ;;; MYGvBIGsOAAyADsAMgAvADEAMAAvADIAMAAxADgALwA4AC8AMgA2AC8AMQA3AC8A ;;; TgBhAHQAaQBvAG4AYQBsACAASQBuAHMAdABpAHQAdQB0AGUAIABvAGYAIABTAHQA ;;; dABpAG0AZQAtAGEALgBuAGkAcwB0AC4AZwBvAHYAKQAAAA== ;;; -----END-SIGNATURE-----

Because it’s a comment, it will be ignored by AutoCAD releases prior to 2016, and by other AutoLISP-compatible CAD applications such as BricsCAD and ZWCAD.

References:
Signing your application modules for AutoCAD 2016 – Part 1 – Kean Walmsley
Signing your application modules for AutoCAD 2016 – Part 2 – including various other references
To Digitally Sign an AutoLISP File – Autodesk Knowledgebase article

How to obtain a digital signature to sign your LISP files

2 Replies

In an earlier post, I explained why you might want to digitally sign your LISP files. If you decide to go ahead with that, then this post explains how you can obtain and install the digital signature you will need to sign your files. This is the most difficult part of the process and it involves spending money.

Getting a digital signature

Although you can make your own digital signature (there’s an Autodesk Knowledgebase article describing the process), there’s little point in doing this. You can sign your files, sure, but that signature won’t be seen as trusted by software that checks for it. Anybody can create a signature like that, including one that impersonates you, and it doesn’t prove anything. The only purpose for such a home-made signature would be to test the methods you’ll be using to apply a proper trusted signature later.

Edit: if you do want to make your own signature, BlackBox informs me that the MakeCert tool in the Windows SDK mentioned in the Knowledgebase article is deprecated. He suggests using this PowerShell Cmdlet instead.

You’re going to need a signature that is trusted. That means you’re going to have to pay somebody trustworthy to trust you. There are a set of certifying authorities, trusted by Microsoft, Autodesk, etc. who can issue code signing certificates to companies and people. You need to prove who you are to one of those authorities and pay them to certify that you are who you say you are. So before you start, make sure you or your business are visible in terms of directory listings, publicly visible phone numbers, etc. If you are representing a company asking for a certificate, you can expect to be asked to produce evidence that you really represent that company. You can expect to confirm that your email and phone number are really under your control.

You only need to do this once a year, or even once every several years if you pay in advance. You might find that the evidence you need to provide changes at renewal time; for example a Yellow Pages listing that was OK in 2015 was no longer accepted when I renewed in 2017, so I had to register my business with another listing.

In my search for a certifying authority, I found that K Software, a reseller for Comodo, was the cheapest source for a code signing certificate, see here. An OV certificate will be fine for signing LISP.

K Software takes your money (USD $67 to $84 a year depending on the length of time you need), gets Comodo to provide the certificate, and provides a handy tool (KSign) that allows you to simply apply the certificate to various files without some of the messing about that’s otherwise required. It’s not useful for LISP files, though. Comodo also provides the support, and I’m happy to report that in my experience their customer service is excellent.

Note: it’s important that you pay close attention to the instructions when applying for your certificate. For example, the browser you use to apply for the certificate is vital. Choose one that’s suggested (e.g. Firefox) and which you expect to use later to obtain the certificate.

Installing a digital signature

Once your evidence is accepted and your payment has gone through, you will be sent an email with a special code, allowing you to obtain the certificate. It’s important that you’re using the same browser on the same computer that you used when applying for the certificate.

Once you click the link and obtain the certificate, you’ll want to export it. In Firefox 58.0, use Options > Privacy & Security and scroll to the bottom to see View Certificates. Select the certificate and pick Export. This will create a .P12 file that you can back up and install on this or another computer. To install the certificate, double-click the .P12 file and follow the prompts to assign it to the current user in the default location (Personal).

That’s it. You should now have a certificate installed that you will be able to use to sign LISP and other files. To check this, start the Windows Certificate Manager (C:\Windows\System32\certmgr.msc). Have a look in Current User > Personal > Certificates and you should find your newly installed certificate.

The next post in this series will explain how to apply this digital signature to your LISP files. That’s the easy bit.

Why digitally sign your LISP files?

4 Replies

After I mentioned in an earlier post that I had digitally signed the sample LISP file I had provided, this generated some interest. In this post, I’ll explain why you might want to sign your LISP files. In a later post, I’ll explain how to do it.

These days it is standard practice for developers to digitally sign their code. Operating systems and applications are displaying increasingly scary warnings when coming across unsigned code. Here is an example of the sort of message you get when you load an unsigned LISP file into AutoCAD from a location that has not been explicitly configured as a trusted location:

If you’re a CAD Manager dealing with your own internal code, it’s not too onerous to configure AutoCAD in Options > Files such that a folder is trusted by AutoCAD and place your code in there. The folder should be read-only; if it isn’t, AutoCAD warns you when you try to configure it. If you do this, the scary warnings don’t appear to bother and confuse your users, even if your code is unsigned.

Another way a CAD Manager can avoid the warnings is to set the SECURELOAD system variable to 0. That’s generally not recommended because it turns off AutoCAD’s security features. While you’ll probably get away with this, there’s always a chance that a user will load some malware and then you’ll have to explain yourself to management.

If you’re not just using your code internally and it’s going to be used by other parties, then you’re not going to have that level of control over the user environment. In recent AutoCADs it’s possible to set up the installation deployment such that users can’t turn off the security settings. If the CAD Manager at the location using your code has done this, your potential users are going to be presented with unprofessional-looking scary warnings.

If you sign your code, users might still get a warning, but it’s less scary. It identifies you as the verified source of the code so they will have more confidence in picking the Always Load button. Once they’ve done this, other signed code of yours will be automatically trusted.

There’s another important reason you might want to sign your code, and that’s protection against other people’s modification of your code. If somebody edits your LSP file and then gives it to someone who tries to load it, the user is presented with an even scarier warning:

Note that this warning no longer has your name on it. This means it’s possible to protect yourself from people (internal or external) who well-meaningly hack about with your code and then try to blame you when it goes wrong. It also gives a level of protection against your code being infected by malware.

Note that all of the above only applies to AutoCAD 2016 and later. AutoCAD 2014 introduced some LISP loading security measures, but the signature stuff came a couple of releases later. Earlier AutoCAD releases, along with compatibles such as BricsCAD and ZWCAD, will just ignore the digital signature. It’s just a comment in the code as far as they’re concerned.

LISP files with the LSP, MNL, FAS, or VLX file extensions can be digitally signed. There’s a bug in the original iterations of AutoCAD 2016 and AutoCAD 2018 that prevents signed VLX files from working. This was patched later in both releases (2016 SP1 and 2018.0.2), but if you’re distributing your code externally there’s always a chance that your VLX might end up in the hands of somebody using a broken release. Also, VLX files that are digitally signed cannot be loaded into AutoCAD 2015 and earlier, broken or not. You should bear that in mind before distributing signed VLX files. I don’t do it and would advise against it. Thanks, Autodesk.

Given this information, if you decide that signing your LISP is a good idea, watch this space for information on how to do it.

Setting your application or document window size using LISP

1 Reply

I intend to produce a few videos containing tips, tutorials, product comparisons and the like. I’ve set up a cad nauseam YouTube channel, but don’t bother visiting it yet because it’s empty.

One of the things I need to do for these videos make sure I’m capturing the screen at an appropriate resolution. I knocked up a bit of Visual LISP to take care of this task quickly and accurately, and you might as well have it. It’s a simple routine that allows you to accurately size either the main AutoCAD application window or the current document window (drawing area) within the main window.

The file is WindowSize.lsp. It should work in all full AutoCAD releases (not counting LT and AutoCAD for Mac) and AutoCAD-based verticals from 2000 on.

It works in recent BricsCAD releases (except the free and LISPless BricsCAD Shape). I’ve only tested it in Windows, but it should also work in the Mac and Linux versions due to the high degree of LISP compatibility provided even across platforms. It also works in ZWCAD 2018 for the main application window, but don’t use it on the document window because that doesn’t work.

Download it, put it in a location of your choice and load it into your CAD application (for example by dragging and dropping it from Explorer onto the drawing window).

Note: In AutoCAD 2014 and later, loading any LISP or other executable file may result in a warning depending on the release, the security settings, whether the file is located in one of AutoCAD’s trusted locations, and whether the file is digitally signed. I’ve digitally signed the file to reduce the incidence of warnings, but you could still see something like this:

The verified publisher should be cad nauseam as shown above. If you pick Always Load then you shouldn’t see the warning again for this file or any others signed by cad nauseam. Feel free to edit the file for your own needs, but if you do the signature will become invalid and you’ll be warned again when loading the file.

Once it’s loaded, enter the command WindowSize. The prompt sequence goes like this:

Command: WINDOWSIZE Window to size [Application/Document] : Width in pixels <1280>: Height in pixels <720>:

Now, back to work on the first of those videos.

Why Bricsys makes the best AutoCAD for Mac

3 Replies

Bricsys has just released BricsCAD V18 for Mac. Here’s the download link and here are the release notes.

BricsCAD V18 is an excellent DWG 2018-based CAD application, and the Mac version lacks little in comparison to the Windows version. It’s so much more capable than the perpetually half-baked AutoCAD for Mac that I struggle to comprehend why anybody with the choice would even contemplate the notably inferior and seriously overpriced Autodesk offering.

That’s not just opinion, it can be supported objectively.

Price first. US prices are shown here for a single standalone license over five years, inclusive of the cost of upgrades. The BricsCAD prices therefore include maintenance (it’s optional); the Autodesk prices are for subscription (not optional). No temporary discounts have been included. I have excluded bargain-basement BricsCAD Classic because it lacks the full set of programming and 3D modeling tools. I have assumed that there will be no price increases over the next five years. Given recent history, that’s probably close to the truth for Bricsys prices. Autodesk, not so much.

Year	BricsCAD Pro	BricsCAD Platinum	AutoCAD
1	970	1330	1470
2	240	240	1470
3	240	240	1470
4	240	240	1470
5	240	240	1470
Total	1930	2290	7350

It’s worth noting that if you want to stop paying Bricsys, you’re left with the latest version to use indefinitely. You can change your mind and get back on the upgrade train later, if you like. That sort of flexibility is long gone at Autodesk, where subscription means no pay, no play. If you stop paying, despite having paid 3.2 times as much for your software over the five year period, you’re left with nothing.

Now, features. You may have noticed that Autodesk is now too embarrassed to list the differences between the Windows and Mac versions of AutoCAD on its web site. The Compare AutoCAD vs. AutoCAD for Mac page is now a shadow of its former useful self, devoid of all detail. If you want to get a reasonable idea of what’s going on with AutoCAD for Mac’s deficiencies, you can check out my post about the 2017 release that lists the missing features.

Alternatively, you can have a look at the equivalent Bricsys comparison page, which you should probably do anyway before spending any money. It’s strange that you now need to visit a competitor’s page to get detailed information about an Autodesk product, but in the CAD world these are strange days indeed.

It’s important to note that the Bricsys comparison page has issues; while the BricsCAD columns are up to date, the AutoCAD columns are a year behind. That page definitely needs an update in order to provide a fair comparison. Don’t rely on it completely (e.g. all of the listed products except BricsCAD V17 for Linux use DWG 2018 as the native format, not DWG 2013), but it will give you an approximate idea. Look at the little red X marks in the rightmost column and you’ll see that a whole bunch of the missing AutoCAD for Mac features, even after all these years, are very significant and their absence could rule out the product for you. Don’t expect much in the way of future improvement. either. AutoCAD for Mac is in maintenance mode, just like the full product.

BricsCAD for Mac is not just more fully-featured, it’s ironically also more AutoCAD-compatible than Autodesk’s effort. For example, try to run a selection of LISP routines in both products. Almost all of it will run just fine in BricsCAD. Anything that uses ActiveX or DCL (dialog box) calls simply won’t work in AutoCAD. You might be all right with some simple routines (if it was written for AutoCAD for DOS then it will probably be fine) but any LISP even moderately sophisticated is going to fail.

BricsCAD for Mac doesn’t just provide capabilities that AutoCAD for Mac doesn’t have and never will, it offers something more than that. It offers a path beyond basic drafting. You can abandon all hope of Revit for Mac – that won’t be happening. AutoCAD-based vertical products? Nope. Inventor OS X? Forget it. But the availability of a product like Bricsys BIM for Mac (not priced above – it’s US$770 extra if purchased seperately) is an obvious drawcard for Mac-happy architects. You can create 3D parametric models on your Mac if you use BricsCAD Platinum, and you can create them without straying far from a familiar AutoCAD-like environment. Sheet metal? Sure (at extra cost).

If you’re a Mac-only person and you’re wedded to Autodesk, you’re not only being ripped off, you’re following a dead-end path. Time to check out the alternatives.

AutoCAD 2018 for Mac – welcome to twenty years ago

3 Replies

In the past, I’ve described how AutoCAD for Mac was released half-baked (as I predicted) and has remained half-baked ever since.

But wait! Autodesk has proudly announced AutoCAD 2018 for Mac. Skimming through that blog post, I must admit my jaw dropped when I saw some of the new features. This one, for example:

This “new feature” was first provided to AutoCAD users in the 20th century. It was an Express Tool in AutoCAD 2000 (released 1999) and was absorbed into mainstream AutoCAD a few years later. The alias editor goes back even further, to the Release 14 Bonus Tools (1997). That one was absorbed into AutoCAD in 1999. Some of the other new features are also old. Migrating your settings was new back in the century that started without powered flight. Now, not so much.

These features are new to AutoCAD for Mac, of course, and that’s kind of the point. Autodesk is advertising, as new, features that were born before some of the adults who are now using their products.

There are other very important features (e.g. DCL support, essential for LISP compatibility) that date back even longer (Release 12, 1992) and which are still missing from AutoCAD for Mac. That’s right, in some areas AutoCAD for Mac is a quarter of a century behind. And counting.

On the bright side, you do now get access to the pointlessly-changed 2018 DWG format. A couple of features are reasonably new additions, but they represent a small subset of the small number of minor improvements in AutoCAD 2017 and 2018 for Windows. If anything, the rate of improvement of AutoCAD for Mac is lagging behind even the glacial progress of AutoCAD for Windows, despite starting from a much lower base point.

I note with interest that Autodesk’s comparison page is now hiding the detail of the differences between the full product and AutoCAD for Mac. I guess if you have two identically-priced products and one’s missing a bunch of stuff, you might be tempted to hide the fact from your potential customers. This post of mine from last year will give you some idea of what Autodesk’s not telling you about what’s missing from AutoCAD for Mac. Clue: it’s a lot.

Mac users pay full price for their product and deserve much better than this. If you want information on a full-featured “AutoCAD for Mac”, don’t bother looking for it from Autodesk. Try Bricsys instead.

Tip: what to do when your text becomes empty rectangles

1 Reply

Dear person who used the search terms “writing has become empty rectangle in cad” and “autocad text has become an empty rectangle” on this blog, I suspect you probably have a drawing where QTEXT has been turned on. To fix this, enter QTEXT at the command prompt, set it to OFF, and if the problem doesn’t go away by itself then issue the REGENALL command.

Pedantic note: the command name is QTEXT, but this controls a system variable called QTEXTMODE. QTEXT OFF is equivalent to both SETVAR QTEXTMODE 0 and just QTEXTMODE 0. In LISP it would be (setvar “QTEXTMODE” 0).

This tip applies to all AutoCAD releases and variants you’re likely to run. Because BricsCAD has a high degree of command-line compatibility with AutoCAD, it applies to BricsCAD too. The same may apply to other AutoCAD-compatible applications.

CAD-related Twitter exchange of the year

Leave a reply

In a Twitter post (now deleted), the AutoCAD twitter account asks us to submit our feature ideas for AutoCAD, and links to the Autodesk Ideas Page:

Just one problem. As R.K. McSwain points out in his reply, the Ideas Page has no section for AutoCAD. There should be one, and should have been one for years, but there isn’t. That tells you all you need to know about how the level of concern Autodesk has about AutoCAD’s future development.

Here’s the exchange in all its glory:

Oops.

First 2018.1-broke-my-AutoCAD reports coming in

1 Reply

Thanks to R.K. McSwain for pointing out that at least one user has reported unexpected shutdowns from AutoCAD (Architecture, probably) following installation of the 2018.1 Update. The problem went away following uninstallation of the update.

Caveat updator.

Anybody else have any issues or are you all waiting for the early adopters to find out for you?

Edit: it turns out the crash occurs when opening 2013 DXF files.

Edit 2: a hotfix has been posted here.

AutoCAD 2018.1 released, but only for some

10 Replies

Autodesk has released the AutoCAD (and LT) 2018.1 Update, not to be confused with the earlier ill-fated 2018.0.1 Update. It’s only available for currently-paying subscription and maintenance customers. The “non critical” bug fixes in this Update (by Autodesk’s definition) are being withheld from Autodesk’s other customers.

Those of you who have allowed your maintenance to expire due to Autodesk’s development inaction and unjustified price increases can consider yourselves duly punished for failing to fall into line.

If you have the execrable Autodesk desktop app installed (not recommended) and it works as expected, this update will present itself to you. Otherwise, get it from your Autodesk Account page. Go to Management > AutoCAD > 2018 Downloads > Updates & Add-ons and then pick the appropriate AutoCAD 2018.1 Update download.

It has yet to be seen whether this update will break things, so if you’re feeling nervous you might want to hold off for a while and let others find out for you. (Edit: it broke one person’s AutoCAD, see comment from R.K. below).

Weighing in at well over 400 MB, the AutoCAD 2018.1 Update download is about twice the size of a complete BricsCAD download, even before expansion. So it must contain a pretty impressive amount of stuff, right? Or is it all bloat? Well, it includes 2018.0.1 and 2018.0.2 and adds this:

Xref Layers Override – Improvements to Xref Layers make it easier to identify overrides and restore them to their default values.
Views and Viewports – A new Named Views panel is added to the View tab to make it easy to create and restore named views from the ribbon, and to create scaled views and viewports for your layouts. The new layout viewports are automatically assigned a standard scale that can easily be changed from a new scale grip on the viewport. Viewport grips have been enhanced.
High Resolution Monitor Support – Supports additional dialog boxes. Palettes and icons are correctly adjusted to the Windows setting for the display scale.
3D Graphics Performance – Work on performance continues to optimize the speed of 3D display for the Wireframe, Realistic, and Shaded visual styles.

The user interface has been touched up to support the above changes. The Preview Guide has been prepared to the usual excellent standard.

That’s all useful stuff, and most welcome. Work has gone into providing some genuinely useful adjustments. But there’s not a lot of it. Autodesk is still just tinkering at the edges.

Overall, AutoCAD 2018.1 is a pretty minor mid-term update, falling a long way short of, say, Release 13c4. That update was shipped on CD to all customers. Free. No maintenance or subscription required.

Bricsys does much more significant and worthwhile mid-term updates than this, and doesn’t charge for them. Perpetual license owners, even those not on maintenance, get them for nothing. Along with the bug fixes. Which are properly documented.

Autodesk used to do all that too, but its customer service has since regressed to the point that the standards of the Release 13 days are something to yearn for. Long-term Autodesk customers will know just how damning that state of affairs is. Autodesk lags a long way behind not only the competition, but also its former self.

Autodesk CEO and all-rental architect Andrew Anagnost has asked Autodesk customers to give him a year to prove that his business model will provide them with better value. It’s not clear when that year was supposed to start, but the all-subscription start date of 1 August 2016 seems reasonable. However you reckon it, a big slab of that year is gone and there’s very little to show for it.

Time to get your finger out, Andrew.

Automated .NET 4.7 update kills AutoCAD pre 2017

7 Replies

Thanks to Robert Green for pointing this out:

Microsoft is installing .NET 4.7 as part of their auto updates and it is causing many legacy Autodesk applications to crash on any ribbon interaction. Touch the ribbon, away goes your software.

If you can keep from installing the 4.7 framework do so. If the damage is already done then uninstall .NET 4.7 and install .NET 4.6.2 using this download link. Note that the uninstall of the offending version must be done first!

AutoCAD 2013 to 2016 and Inventor are affected, and possibly other products. BricsCAD users are unaffected.

It is also reported that you can work around the problem by hacking the registry to identify an earlier .NET version as being installed (the usual caveats apply). That’s described in this Autodesk Knowledgebase article that works around a related but slightly different issue.

Don’t you just love the way continuous automated updates enhance and enrich the user experience?

AutoCAD 2018.0.2 arrives

3 Replies

AutoCAD 2018.0.1 is dead, long live 2018.0.2!

Here’s the readme.
Here’s the 64-bit direct link.
Here’s the 32-bit direct link.

This supposedly fixes stuff that 2018.0.1 broke, such as the signed VLX thing. Will this one break other stuff? I guess we’ll find out.

Bloatware – a tale of two installations

Leave a reply

In a previous post, I showed that AutoCAD is bloatware by comparing the size of its downloads to that of BricsCAD. Obviously, an application that’s ten times the size it should be is going to cost you a lot of unnecessary bandwidth, download time and drive space. But maybe you don’t care about that. What practical difference does it make?

Well, for one thing, the blimping-out of Autodesk’s former flagship product has a big effect on installation time. Vast and ever-increasing amounts of time are wasted by users of Autodesk products, just waiting for the things to finish installing. But isn’t this just the inevitable price to pay for the functionality provided?

No. Again, BricsCAD proves it.

The installation comparison is shown below. These installations were performed on a mid-range Windows 10 i7 PC with 8 GB RAM. The downloaded files were executed from a local hard drive and the applications were installed to a local SSD. If I needed to enter information manually, I stopped the clock while that was going on. Times are the total elapsed time from commencement in minutes and seconds. More user input was required for the AutoCAD install, but that has not been counted in this comparison. That is, by eliminating the human input stages I’m being kind to Autodesk.

I performed a complete default installation of BricsCAD. In the case of AutoCAD, I turned off the installation of Recap and A360 Desktop to make for a fair comparison, as equivalents are not part of the BricsCAD install and those components are not required by the average CAD user. Everything else was as per default settings.

BricsCAD V17.2 64-bit Windows Installation

Installation Operation	Timestamp
Execute BricsCAD-V17.2.03-1-en_US(x64).msi	0:00
Prompt for questions	0:03
Click Yes for UAC Allow	0:14
Installation complete, start application	0:35
First run startup	0:40
Total time from install to ready to draw	0:40 (100%)

That’s astonishingly fast. Remember, this is an application that is more capable than AutoCAD overall. How does installing AutoCAD itself compare?

Equivalent AutoCAD 2018 64-bit Windows Installation

Installation Operation	Timestamp
Execute AutoCAD_2018_English_Win_64bit_dlm_001_002.sfx.exe	0:00
Self-extractor finishes initializing	2:46
Self-extractor finishes extracting, click Yes for UAC Allow	4:56
Install screen appears, answer questions, start install proper	5:04
Desktop icon appears	8:10
Install complete, restart required	10:21
Restart complete, start application	11:41
Activation begins	12:05
Activation complete	12:21
Close AutoCAD, execute AutoCAD_2018_Product_Help_English_Win_32_64bit_dlm.sfx.exe	12:25
Self-extractor finishes initializing	14:44
Self-extractor finishes extracting, click Yes for UAC Allow	14:54
Install screen appears, answer questions, start install proper	14:57
Offline Help installation complete, execute AutoCAD_2018.0.1_64bit_r2.exe	15:44
2018.0.1 install complete, start AutoCAD	16:50
Second startup complete	17:18
Total time from install to ready to draw	17:18 (2595%)

Installed sizes are roughly 0.5 GB for BricsCAD and 2.4 GB for AutoCAD. It’s hard to be exact because Autodesk likes to perform multiple installs when one is requested and tends to squirrel away various components in a variety of places. Here are the ten(!) new entries in Add or Remove Programs after just the first stage of the AutoCAD install:

OK, so maybe AutoCAD takes 26 times as long as BricsCAD to install. But the AutoCAD installation images are so much prettier than the plain old BricsCAD dialogs! Shall we call it a draw?

No.

Autodesk, you took a real pounding here. Bricsys chewed you up, spat you out, ground the chewings into the dust, set fire to the remains and then put out the fire with bodily fluids. Sorry, but you deserve it. Your installations have been ridiculously slow for years and are getting worse. Installing a vertical product or suite is beyond a joke; it makes even the AutoCAD install look speedy. It’s not good enough.

AutoCAD 2018.0.1 mystery deepens with silent withdrawal

Leave a reply

As I mentioned earlier, the release of AutoCAD 2018 was followed almost instantaneously by the first update, 2018.0.1. At the time of writing, there was no official information about this update. Some information was later made available, but questions remained.

Now the update has been silently withdrawn. Go to Autodesk Account > Management > AutoCAD > Downloads > Updates & Add-ons and you will no longer see this:

The infamous Autodesk desktop app also shows no sign of this update. So why has it been withdrawn? Autodesk isn’t saying, but thanks to Jimmy Bergmark, we know that installing the 2018.0.1 update re-introduces a bug from AutoCAD 2016 (pre SP1) where signed VLX files don’t load. This means various 3rd party applications won’t load if the developers have done the Autodesk-recommended right thing by digitally signing their code.

If you’re a developer and want to test your code under the different versions, these direct links still work at the time of writing:

If you’re not sure whether or not you have 2018.0.1 installed, the About command will show you.

You can also check for this under program control by inspecting the system variable _VERNUM. In AutoCAD, it’s “O.49.0.0” before the patch and “O.61.0.0” after. I don’t know about LT, and I don’t know about the situation with verticals. Do they incorporate the 2018.0.1 fixes? How about the VLX bug? Should users who have applied this update uninstall it? Is this going to be done automatically or by Autodesk desktop app? How should users manually revert to the pre-2018.0.1 state if they need to load applications that use signed VLX files?

I think it’s fair to say that Autodesk’s management of this update has been a disaster. This is just one in a long line of AutoCAD update screw-ups going back decades. It proves comprehensively that continuous updates from Autodesk are a non-starter.

Autodesk can’t be trusted avoid breaking things with its updates. It can’t be trusted to effectively communicate about the updates. It can’t be trusted to provide fixes for its broken fixes. It can’t be trusted to provide an automated update mechanism that doesn’t hog your resources or one that works properly.

The AutoCAD 2018 install inflicts the execrable Autodesk desktop app on your systems without asking, which in itself is a betrayal of trust. I recommend you uninstall it immediately after all Autodesk installs. You will need to right-click the app tray icon and use the Exit option before you can uninstall it using Add or Remove Programs.

Autodesk needs your trust to make its continuous update idea work. Autodesk doesn’t have that trust. Autodesk doesn’t come close to deserving it.