Tag Archives: Bug

Fix released for Autodesk subscription licensing error (yes, another one)

1 Reply

Providing yet another entry in the it’ll never happen again file, Autodesk has issued a fix for an AutoCAD 2018 subscription licensing crash.

Thankfully, it’s not compulsory to use the execrable Autodesk desktop app or malware-like Akamai download manager to obtain this fix. There are direct links for the 32-bit and 64-bit fixes.

Lessons we learned from this:

  • AutoCAD doesn’t just phone home once every 30 days to maintain even a long-term a subscription license, it phones home 24 hours later too. And probably every 24 hours after that.
  • Desktop software that relies on the internet to continue working is a terrible idea.
  • Yes, it will happen again.

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.

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.

Autodesk has released an update to fix the following AutoCAD 2018 problem:

Product users of version 2018 Autodesk single-user subscriptions may experience an intermittent crash. The crash occurs when it has been more than 24 hours since the last successful authorization check and there is intermittent or no internet connection, or the licensing authorization server is unavailable. The licensing authorization check occurs in the background and is completely unrelated to activities the user is performing at the time of the crash.
A fatal error message may be shown by the product. For example:

FATAL ERROR: Unhandled e06d7363h Exception at ee563c58h

 
Links:

Note that this crash only afflicts subscription (rental) single-user (standalone) customers. People with perpetual licenses don’t have to put up with the multiple additional points of failure caused by the subscription licensing system insisting on phoning home every 30 days. Yes, even if you pay for three years’ subscription up front, you’ll still need a working Internet connection every 30 days if you want to keep using the product.

At least, Autodesk has been saying it’s only once every 30 days (as if that wasn’t bad enough). The information provided with this hotfix tells a different story. What is the license server doing phoning home 24 hours after the last successful authorization check? Enquiring minds want to know.

No criticism of Autodesk is implied for providing this hotfix. As always, I commend Autodesk for fixing up problems as they arise. The basis of my criticism is the hotfix being necessary in the first place. It’s caused by Autodesk inflicting unnecessary complication on its customers for its own internal reasons. This one fails the “how does this benefit the customer?” test big-time.

The single-user subscription licensing mechanism has been a crock from day one, especially for CAD Managers of multiple users who have to deal with its onerous requirements. It’s an astonishingly poor design, very badly implemented. Even with this particular crash fixed, it’s still a crock.

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.

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.

AutoCAD 2018.0.1 mystery partially resolved but questions remain

6 Replies

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 is now available, but more questions have arisen.

If, like me, you don’t/won’t/can’t have Autodesk desktop app running on your systems, the only current official way to get at the download is using Autodesk Account (but read the whole of this post before you go there). That’s also how you get at information about the update. Go to Management > AutoCAD > Downloads > Updates & Add-ons. From there, it’s not obvious how to get the information, but it’s under More options.

From there, pick View Details. This will show you the following information (after you pick More):

As you can see, the severity is considered high. If you pick View release notes, you can see the readme, or you can go straight to it if you have this direct link. Here are the fixes described in the readme:

  • Occasional crashes when ending an AutoCAD session using specific API code no longer occur.
  • Publishing annotative multiline attributes no longer results in incorrect annotative scaling.
  • PFB fonts can now be compiled successfully as SHX files.
  • The border of a mask is no longer plotted in PDFs when “Lines Merge” is turned on.

Although it would be easy to have a go at Autodesk for shipping a product that needs fixing within hours of release, that wouldn’t be entirely fair. No software is flawless. Stuff happens, and the sooner fixes are provided to resolve that stuff, the better. So I commend Autodesk for getting this fix out quickly.

That doesn’t mean Autodesk is blameless, though. Read on.

First, the way the information about this update was (or wasn’t) disseminated was sub-optimal. It has required too much prodding and guesswork to get to the point we are now, and we’re still not where we should be.

Next, there’s scant information in the readme. I don’t see any documented way of including this fix in a deployment, for example. That means it’s not possible to create a one-step automated install without resorting to trickery.

Further, this update isn’t available on the main Autodesk site. It needs to be. Even if you know the version number to look for, a search at autodesk.com will come up blank:

Using the Autodesk Knowledge Network Download Finder won’t help, either:

Fortunately, these direct links appear to work:

This brings me to my fourth point of criticism. See that the 64-bit executable has “r2” on it? The one I downloaded on 23 March doesn’t. The 64-bit executables are similar in size to each other but the binary content is different. The 32-bit 2018.0.1 has a date of 22 March and the 64-bit 2018.0.1 r2 has a date of 24 March. So it looks like the patch has been patched, at least for 64-bit users.

Information on this patch-patch is non-existent. Should somebody who downloaded and applied the 64-bit 2018.0.1, download and apply 2018.0.1 r2? Will that work? Do they need to uninstall 2018.0.1 first? How should they do that? Will the 32-bit 2018.0.1 also be updated to r2? Should those users hang off a few days to avoid wasting time or go ahead with what’s there now?

Over to you, Autodesk.

AutoCAD 2018 – there’s already an update

3 Replies

If you downloaded and installed AutoCAD 2018 yesterday and don’t/won’t/can’t have Autodesk desktop app running on your systems, you may already have another download to do, because AutoCAD 2018.0.1 is out.

At the time of writing there is no sign of this update on Autodesk’s main site, but you can get at it using Autodesk Account. Go to Management > AutoCAD > Downloads > Updates & Add-ons.

All that’s downloaded is an executable. No readme, nothing. There is currently no official information about the reasons behind this update, what it includes, what it might affect, how to include it in a deployment, etc. You’ll need to make up your own mind whether to install this update now or wait for information about it. I suggest the latter.

Of course, if you’re using desktop app and allowing automatic updates, you don’t need to worry about any of that that. Just trust Autodesk to not break anything and hope for the best.

What’s the worst that could happen?

Edit: see this post for further information.

Huge PDFs? AutoCAD 2017.1.1 could be to blame

3 Replies

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. In apparently unrelated news, you seem to be getting more fatal errors and several of your add-ins have stopped working. You decide to do without them.
  • Autodesk desktop app installed AutoCAD 2017.1.1. Your add-ins have magically started working again and there seem to be fewer fatal errors.
  • You get some huge PDFs from AutoCAD but read this post and uninstall AutoCAD 2017.1.1. The PDFs you create are no longer huge, but your add-ins have stopped working again and there seem to be more fatal errors.
  • You read this other post and manually install the AutoCAD 2017.1 Hotfix. Your add-ins start working again. The fatal errors remain.
  • Autodesk desktop app continually and perpetually nags you to install AutoCAD 2017.1.1.**
  • You uninstall Autodesk desktop app. Your system speeds up and the nags go away.

Moral of the story? Autodesk isn’t competent enough to trust with automatic updates. Uninstall Autodesk desktop app. Relax.

* YMMV
** I don’t know if this actually happens (Autodesk desktop app is not going to be installed on any of my systems to find out) but it wouldn’t surprise me.

AutoCAD 2017.1.1 Update

9 Replies

Thanks to Jimmy Bergmark, I now know that the controversial subscription-only* AutoCAD 2017.1 Update has itself been updated. Jimmy was brave enough to install and run the execrable Autodesk desktop app and discovered the update update. Rather you than me, Jimmy!

Here’s the readme. You’ll need to get at it using Autodesk Account.

I note that a bunch of crashes are fixed by this update update. Perhaps that is related to the magical missing AutoCAD 2017.1 crash information? Who knows?

The update was apparently released over a month ago on 17 November 2016. Autodesk needs to work out an alternative mechanism to Autodesk desktop app so that those of us who won’t/can’t use it will still be informed when updates become available. If only there were some other method Autodesk could use to communicate with customers! Too hard, apparently.

* not really

BricsCAD startup LISP bug fixed

Leave a reply

In my previous post I have a real problem with BricsCAD, I related my then-latest interaction with the Bricsys support system:

Steve Johnson
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
Hi Steve,

There was a regression introduced in V17.1.10 that caused startup code to execute too early under certain conditions, before the lisp engine document context was properly initialized. This has been fixed now for the next update.

Steve Johnson
06-12-2016 02:43 UTC
I must say, the responses I’ve been getting to my support requests have been absolutely bloody brilliant. Cheers!

Let’s just finish the sequence, shall we?

Second Excellent Bricsys Person
13-12-2016 19:18 UTC
Hi Steve,

I have very good news. The fix is included in BricsCAD V17.1.11, available for download.
Thank you for your help.

Following a fast and straightforward download and install, I can confirm that the bug is fixed. The elapsed time from my bug report to the fix being publicly available and me being informed personally of the fact was 8.5 days. Note that this isn’t a workaround, patch or service pack, it’s a permanent fix that is now automatically in place for everybody who downloads the software.

Edit: the new version was actually released at 4 PM on 9 December, so it was less than 4.5 days from report to fix. Outstanding!

I should mention that I also received a prompt and relevant response from Dale at McNeel, despite the fact that the problem was nothing to do with him!

For somebody used to dealing with Autodesk, this is a breath of fresh air. Bricsys team, take a bow!

Draping images over surfaces in Civil 3D

3 Replies

Having recently overcome various difficulties to successfully drape an image over a surface in Civil 3D, it may be useful to pass on a few points I have learned. There are various posts and videos out there that helpfully go through this process, but some of them (including Autodesk sources) contain information that is irrelevant or just plain wrong, and none of them contained all  of the information I needed to complete the task.

I used Civil 3D 2015 for this, but the principles apply to all recent releases. Here is the basic sequence required:

  1. In the drawing containing the surface, attach the image to your drawing using your preferred method (ImageAttach, Xref, ClassicImage). I’ll assume you’re familiar with what you need to do to get the image correctly scaled and aligned with the surface.
  2. Invoke the DrapeImage command, which will show you this dialog:DrapeImage01
    Make sure this is set for the image you want to drape and the surface you want it draped over. You can change the Render Material Name to whatever you like, or leave it as the default. Pick OK.
  3. You no longer need the image attached to the drawing and it will probably only confuse matters, so you can use use the Xref or ClassicImage command to detach it.

If you’re really lucky, that’s it. You will have a lovely-looking surface with a draped image over it. However, at this stage that’s pretty unlikely. Don’t panic! You also need to ensure the following conditions are in place:

  1. The surface will need to use a surface style that includes triangulated surfaces so the image has something to drape over. In the Toolspace, under Surfaces, right-click on the surface and pick Surface Properties…, then change Surface Style to anything with triangles, triangulation or TIN in the name (this varies depending on the template used). If you don’t have such a style available, you’ll need to make your own or edit an existing one using the button with a pencil in it.DrapeImage02
  2. While you’re in the Surface Properties dialog, have a look at Render Material. That should be showing the Render Material Name you specified in step 2 above. If it isn’t, make sure it is. Pick OK.
    Bonus tip: if you later need to remove the draped image from the surface, you can do so by changing the Render Material to something else (e.g. ByLayer).
  3. Still seeing nothing useful? Make sure you are using the Realistic visual style. You can get at the Visual Styles Manager using the VisualStyles command, but in recent releases it has been made easier to switch visual styles using the in-canvas control:DrapeImage03
  4. Still nothing? Try turning off Hardware Acceleration. Right-click on that glowing blue blob thing in the lower right corner and pick Graphics Performance…DrapeImage04That will give you a dialog with a Hardware Acceleration switch. Turn it off, pick OK and (hopefully) voila!

Note that the above conditions need to be in place when plotting, too. You might not expect hardware acceleration to make a difference to plotting, but in this case, it does.

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

Leave a reply

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.

How to break Civil 3D 2013

6 Replies

In Civil 3D 2013 (with or without hotfix 2.1), use the PLOT command and use the Window option. While being prompted for the window corners, use the middle button mouse wheel to zoom to locate the exact point you want. Civil 3D then enters a loop in which it displays:

Document “drawing name” has a command in progress.
Hit enter to cancel or [Retry]:

At this point, the user can do nothing with the program. Hitting Enter, Esc, R, etc. or doing more all do nothing except cause the message to be redisplayed. Picking a point or further wheel zooming does nothing useful. Using the application’s red X, or attempting to use the Taskbar to close it are equally ineffectual. The user has no alternative but to terminate Civil 3D using Task Manager, losing all unsaved work in all drawings.

This happens for me in Windows 7 64-bit. It does not occur using AutoCAD 2013 on the same system. Does it happen for you?