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
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.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.
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 …
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.
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 …
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. …
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 …
In my previous post I have a real problem with BricsCAD, I related my then-latest interaction with the Bricsys support system:
05-12-2016 05:30 UTC
I don’t know if this is a BricsCAD problem or a DOSLib one, so I am reporting it to both Bricsys and Dale at McNeel. I’m also not sure if this was happening in earlier versions.
If I load DOSLib during an S::STARTUP call and then use the (dos_msgbox) function later in that call, this fails the first time round because BricsCAD things the function is not defined. Opening a second drawing results in the call working as expected. I’ve chopped down our startup routine so you have an example.
; error : no function definition ; expected FUNCTION at [eval]
Awesome Bricsys Person
05-12-2016 12:32 UTC
There was a regression introduced in V17.1.10 that caused …
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:
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.
Invoke the DrapeImage command, which will show you this dialog: Full post
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.
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 …
In AutoCAD 2012 and products based on it, saving the drawing while in the block editor can result in your whole drawing being replaced by the block you’re editing. As this can be somewhat inconvenient, it’s probably a good idea to download and install Autodesk’s hotfix for this problem. As always, read the readme first.
Any drawing created in AutoCAD 2008 and later which uses Multileaders will present problems to users of AutoCAD 2007 and earlier. The users of the earlier release will find that rather than having leaders to deal with, they have proxy objects. As a result, it is impossible to edit these leaders in any way other than erasing them. Also, depending on the setting of the PROXYSHOW system variable in the earlier release, the objects may not display at all, or could display only as rectangles.
If the user of 2008 or later used the background mask feature when creating Multileaders, they might appear to be fine on the screen. But when plotting, the text part of each leader will come out as a filled black rectangle. That sort of thing has a long history of happening with wipeouts in some cases, depending on the output device and driver. This problem …
A problem I’ve seen affecting keyboard users (particularly fast ones) in recent AutoCADs (since 2006) is that the characters entered into the command line are not always the ones you typed. Or rather, they are the ones you typed, just not in the right order. In particular, I’ve seen the first couple of characters get messed up, so you might get ILNE instead of LINE. In addition to the annoyance factor, this is something of a productivity killer.
Has this happened to you? If so, please comment. Any comment is welcome, but it would be great if you could provide the following information:
AutoCAD (or vertical) release(s) where you have seen this happen. Also mention any recent releases where you have seen it not happen.
Command line status when you have seen this happen (docked, floating, off, all of the above).
Dynamic input status when you have seen this happen (on, …
In a recent blog post, Deelip Menezes appears to be shocked by the very idea that a particular CAD company (no, not Autodesk) would ship software that contains known bugs. I thought he was joking, because he’s surely aware that practically all software companies with highly complex products release software with known bugs. As Deelip points out, those companies with 12-month cycles are particularly prone to doing this. There is no possible way any company can release something as complex as a CAD application within a fixed 12-month cycle without it containing dozens* of known bugs (because there isn’t time to fix them after discovery) and dozens* of unknown ones (because of insufficient Beta testing time).
Reading Deelip’s post and subsequent comments more carefully, it becomes clear that he doesn’t mean what a casual glance might lead you to believe he means. Deelip makes a specific distinction between …
It appears that the mystery bug was in fact a mole cricket. It appears that these things are poorly understood and I should have passed it on to our local museum. I should definitely not have put it on our lawn, as it appears that these things are quite likely to be the culprit behind the damaged patches on our lawn.
No, not the Bug Watch, just a bug you can watch. Does anybody know what this insect is? It is the second one of these we’ve found in our home in Western Australia. It’s very active and it smells horrible.
For those of you who can’t access YouTube, here are some photos of the bug:
A higher resolution version of the above picture is available here. This is the bug about to be given its freedom:
On release, it buried itself in our lawn:
In 25 years in Australia, I had never seen one of these until recently. Any ideas?
I know there are plenty of people still using AutoCAD 2007 and earlier, so this bug warning may save some of you some grief. I have no idea how widespread or isolated this problem is, but under some circumstances I haven’t worked out yet, AutoCAD 2007 fails to plot all of certain dynamic blocks. Some attributes have a habit of being plot-shy. Even if you don’t use dynamic blocks yourself, you could receive a set of drawings, check them on-screen, approve them, plot them and send out paper drawings without all of their parts. Unless you’re carefully manually checking the paper plots, this situation is obviously a little dangerous. Fortunately, Plot Preview also shows up the problem, so it is at least possible to check things without wasting trees.
Here’s an example. This is part of such a drawing displayed in AutoCAD 2007, with all of its parts in place. …
Just when I thought it wasn’t possible for my Autodesk discussion group experience to get any worse, it has. Much worse.
I stated before that in the 15 November update, some Einstein decided it would be fun to copy my private work email address over the top of my public user ID, automatically making it visible to all and sundry in many places. I should note at this point that publishing somebody’s email address without consent is illegal in some locations, including here in Australia. So to the best of my knowledge (not that I’m a lawyer), Autodesk is not only perpetrating a grossly irresponsible breach of privacy, it’s also breaking the law.
Attempting to fix this myself failed, because of some new introduced bug in the login system. When changing my user ID from my email address to “Steve Johnson”, the screen falsely claimed that the data entered was …
I must admit that I wasn’t really expecting the November 15 Autodesk discussion group maintenance effort to come up with the goods and make everything all better again. However, it appears that even my lowly expectations were nothing but naive optimism.
Here are the changes I see:
- The old messages and Plain Text new messages that had their paragraphs stripped out have had them returned. This is the end of the good news, as far as I can tell. If you only ever like reading positive things, particularly about Autodesk, I suggest you stop reading now.
- Rich Text messages have had superfluous paragraphs introduced, and other formatting issues. The more you edit a message, the worse it gets. Try switching back and forth between Rich Text and Plain Text a few times, it’s a crock.
- My email address has been newly exposed to the spambots as my user ID, and …