It must be March, because another AutoCAD has just been launched. Despite this one being codenamed Omega, I’ve been assured it’s not the final AutoCAD release. The good news is that AutoCAD 2018 is twice the upgrade that 2017 was. But hold your excitement, because the bad news is that 2017 was only a 1/10 upgrade.
Autodesk has continued the well-established tradition of acting like a low-quality sausage machine, reliably popping out consistently unexciting products at regular intervals.
Here’s what’s in this year’s underwhelming sausage:
- Xrefs now default to relative path attachment and there are a few associated tweaks including find/replace path
- You can select objects off-screen (handier than it sounds)
- File dialogs remember settings
- A couple more dialogs can be resized
- There are a couple more tiny user interface tweaks
- The stuff from 2017.1 is included, of course, some seeing minor improvements since then
- iDrop …
If you’re a power user or CAD Manager transitioning from AutoCAD to BricsCAD, one of the things you’ll like is that almost all of your LISP routines will just work. That’s not an statement that can be made about various Autodesk products that bear the AutoCAD name, such as AutoCAD 360, AutoCAD LT and AutoCAD for Mac.
It’s not just simple old AutoLISP code that runs in BricsCAD, but complex dialog routines that use DCL, and Visual LISP stuff that uses ActiveX. Yes, even on the Mac and Linux platforms. Some DOSLib functions are built in and the rest can be loaded, as with AutoCAD. Even OpenDCL is supported. It’s a quite astonishingly high level of compatibility.
But it’s not 100%. There are minor incompatibilities, system variable and command-line differences that cause problems in a handful of cases. It’s often possible to work around these and still retain …
AutoCAD 2017 for Mac and AutoCAD LT 2017 for Mac have been released. Here’s a video highlighting exciting and innovative new features such as drawing and layout tabs. Despite such stellar advances, it’s safe to say that AutoCAD for Mac remains half-baked, even after all these years. Don’t say I didn’t warn you.
According to Autodesk, these are the features missing from AutoCAD 2017 for Mac:
LAYDEL, LAYMRG, LAYWALK and LAYVPI
New layer notification
Sheet Set Manager***
Feature finder for help
Model documentation tools
Dynamic block lookup parameter creation/editing
Table style editing
Multiline style creation
Simplified, powerful rendering
Material creation, editing, and mapping
Advanced rendering settings
Back in 2010 I asked the question Any BricsCAD users out there? and there were a few of you who had tried to replace AutoCAD with BricsCAD. Most who responded had made the change successfully, others not so much.
Six years on, the situation is different. The fact that you can’t buy a permanent AutoCAD license any more has prompted some Autodesk customers to look more seriously at alternative vendors who do provide that option. Bricsys is one of those vendors, and their DWG-based AutoCAD alternative BricsCAD has improved way more rapidly than AutoCAD over the same time period. No, that isn’t a guess, I’ve been keeping an active eye on things. BricsCAD today is by no means perfect, but it’s impressive in many ways. LISP compatibility and performance are excellent, for example. BricsCAD v16 superior to the also imperfect AutoCAD 2017 in several …
A couple of years ago, I reported on the missing features in AutoCAD 2011 for Mac. While some generous souls were prepared to accept something half-baked as a first attempt, even that excuse doesn’t wash when it comes to a third iteration. So how well is Autodesk doing at filling those holes? Decide for yourself. Here’s an updated list of missing features in AutoCAD 2013 for Mac:
- Quick Properties Palette
- Layer State Manager
- New Layer Notification
- Various layer commands including LAYCUR, LAYDEL, LAYMRG, LAYWALK, and LAYVPI
- Autocomplete doesn’t work entirely properly, including offering commands that don’t exist
- Quick Select
- Tool Palettes
- Navigation Bar
- Sheet Set Manager (but there is Project Manager)
- Model Documentation Tools (but at least now there are object enablers)
- Geographic Location
- Table Style Editing
- Hatch Creation Preview
- Multiline Style Creation
- Digitizer Integration
- Change Space
- Express Tools
- Material Creation, Editing, and Mapping
One of the major attractions of the Cloud for vendors is that it ties in customers, providing a reasonably consistent revenue stream. It is an effective anti-competitive strategy. There are various technical and other methods that can be used to ensure that it’s difficult or even impossible for customers to jump ship. While that’s all very nice for vendors, it’s not such a wonderful thing for customers.
Let’s say you’re a CAD Manager who persuades your company to use a great new SaaS service and Cloud storage. Let’s assume it performs well, is secure, has 100% uptime and offers functionality that is not available with standalone software. Your company is pleased with all this and uses it increasingly over several years, eventually moving completely into the Cloud. A good news story, right?
Well, maybe. There are a few things that could go wrong. Very wrong. Wrong enough to get you fired. …
One of the more painful aspects of dealing with installations of recent releases of AutoCAD and related products is that although you might run a single setup routine to install what you think is a single application, the end result is a mass of different components being installed. Each of these components is considered a separate program by Windows, and needs uninstalling separately. Frankly, this is manifestly antisocial behaviour.
I have complained to Autodesk about this ever since it started happening, but the number of sub-installations has been getting greater rather than smaller. Now Autodesk has provided an uninstallation tool, which you can find here. If you download and run psebuninstalltool.exe, you will be provided with a list of applications to uninstall.
This is a move in the right direction, but it’s still far from ideal. You still have to choose which applications to install and which …
One of the less obvious features introduced by AutoCAD 2012 is the Autoloader mechanism that has been provided to make installation of plug-ins (current standard Autodeskspeak for add-ons, apps, utilities, routines, etc.) easier for both developers and users. It may not be immediately obvious, but it’s a useful and important addition.
This mechanism has nothing to do with the AppLoad command, the Startup Suite, acad*.lsp, the (autoload) function or anything else that existed in earlier releases. This is completely new, it has not replaced or broken any of the existing loading mechanisms, and is, in short, A Good Thing. Developers don’t have to use it, but those who do, and their customers, will have certain advantages. I have used it for the ClassicArray loading mechanism, and I expect to see it used by more and more plug-ins over time. It works fine with all of the usual AutoCAD add-on …
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 …
Good news! Autodesk has announced an app that will link iPads and iPhones to Project Butterfly. This provides viewing, markup and limited editing facilities.
Bad news! Autodesk has decide to call it AutoCAD WS, which is bordering on the fraudulent. It’s not AutoCAD, is nothing like it, and is unlikely to ever be anything like it. I can call my dog Prince, but that doesn’t make him royalty. Unfortunately, much of the mainstream media appears to be blissfully unaware of this. This is gaining Autodesk some short-term column inches, but at the longer-term expense of furthering the myth that “AutoCAD” is going to run on iPhone and iPads. People will start using Butterfly, think it’s AutoCAD, and then, if they need CAD for their Macs, wonder why they should spend thousands on something so basic and limited.
Good news! It will be available Real Soon Now, and you can sign up for it …
If you install Civil 3D 2011 using the ANZ (Australia/New Zealand) profile, when you start it up for the first time, you will see a large warning indicating that the drawing requires an Asian language pack to be installed. It also warns that this is a symptom of the acad.vlx virus:
Now I know that in this case it’s not an actual virus causing the problem, but rather the ANZ template drawing being “infected” with this Language Pack requirement. I have had to deal with quite a few incoming drawings in this state, and that’s painful enough without Autodesk also infecting every Australasian Civil 3D drawing with the problem. Other profiles may be similarly infected, but at the moment I don’t know. Edit: Matt Anderson reports that the problem occurs on US systems too.
Autodesk, I suggest that as a matter of great …
Disclaimer: I have absolutely no access to inside information about this Beta. Even if I had, I would not reveal anything that I had learned as a result of such access. This post discusses only information that is already public knowledge.
The native Mac OS X AutoCAD port that Autodesk has been foreshadowing for some time is now in Beta, it seems. The Italian Mac community is getting particularly excited about the leak, but it’s also a popular subject of discussion on at least one English-speaking forum. The Autodesk codename is Sledgehammer, and it’s currently 64-bit only. If this is a subject that interests you, with a bit of sniffing around you can easily find screenshots, a video and you can apparently even download it via torrent if you’re feeling particularly brave/stupid.
If you’re interested in trying it out, it would be much better to apply …
This morning I spoke with CAD International‘s Nigel Varley. Here is a paraphrased summary of the interview.
SJ: When did CAD International buy the drcauto intellectual property rights?
NV: About two weeks ago.
SJ: You are currently helping drcauto customers with authorisation codes, is that correct?
NV: Yes, masses of them. It’s taking up a lot of our peoples’ time.
SJ: Are you charging for this service?
NV: Not at present.
SJ: Do you intend to charge for this service in the future?
NV: Maybe. We may need to, both to pay for our time and to recoup our investment. I don’t particularly like the idea of annual renewals for software, so we may do something different in future.
SJ: If somebody wanted to buy drcauto products such as LT Toolkit now, could they do so?
NV: No, we’re still processing the materials we …
Last week, in my capacity as a de facto CAD manager for a large public utility company, I was having a chat with an Autodesk Australia person (he’s a nice guy and very honest, by the way). The topic of conversation moved to the new AutoCAD-based vertical, Plant 3D 2010. At that stage, I had not even installed the 30-day trial, but I still raised some of the issues that potentially stood in the way of the company adopting this apparently highly suitable product.
In a word, it comes down to trust. Each drawing used or issued by this utility is a legal document with a potentially very long life ahead of it. I showed the Autodesk person a drawing issued in 1901. The assets documented by that drawing are still in use today; indeed, many thousands of people daily depend heavily on them. Before we invest our money, time …
Thanks to Brian and Rick for pointing out the availability of a hotfix for Raster Design 2010’s standalone/network license incompatibility. As a bonus, it also fixes some Raster Design / Civil 3D stability issues.
The hotfix is available here, and as always with patches, fixes, service packs and updates, read the readme first.
Note that although this fixes the most common scenario where a network Raster Design needs to work on a standalone AutoCAD, it does not fix the opposite scenario. So if you have a bunch of network licensed AutoCAD variants available to you and you have a standalone license of Raster Design because you’re the only person in the office who needs it, you’re still out of luck. If you’re in such a position, I think you have a very strong case for a no-cost change from standalone to network licensing for Raster …
Autodesk has been in touch to confirm that the failure to allow a mixed network/standalone environment is confined to Raster Design. I haven’t yet tested this myself, but I’ve been told unequivocally that you can mix standalone and network license models for the major products.
Here is the official Autodesk response to the issue:
We are very aware of the issue currently relating to the co-existence of an AutoCAD SLM (stand-alone license) and AutoCAD Raster Design NLM (network license) configuration. This was not an intentional “change of licensing policy” as expressed in some blog posts this week, but an unfortunate side effect of updating our licensing technology for SLM (stand-alone) seats to be in sync with our NLM seats for all AutoCAD-based products. We can only apologize for this new behavior experienced by customers upgrade to 2010 version products.
We are currently pursuing a couple of options to rectify this …
There are now quite a few file types that you can attach to an AutoCAD drawing as a reference, in the same way that you can attach other drawings as xrefs. We’ve been able to attach other drawings since Release 11 (1990) and images since Release 14 (1997), but every release since 2007 has introduced a new kind of attachment. In AutoCAD 2010, you can now also attach PDFs, MicroStation DGNs (v7 and v8), DWF and DWFx files.
But should you? Maybe not. It depends who is going to use those drawings after you. If you know for certain that every user of that drawing is going to be using 2010 and later, that’s no problem. But if there is the possibility of earlier releases being used, your fine-looking attachments could vanish silently in the night. Attach a PDF to your drawing in 2010, give it to a user of …
I have been in touch with various people at Autodesk about Raster Design 2010’s failure to work in a mixed standalone/network environment. These people have all been suitably apologetic, they assure me it wasn’t a deliberate move on Autodesk’s part, and that moves are afoot to provide a solution fairly soon. For example:
Our intention was never to cause such inconvenience for our Raster customers with the licensing change. We are currently working on a solution and hope to have more information in the coming weeks.
…we are very aware of the issue currently relating to the co-existence of an AutoCAD SLM and Raster Design NLM. This was not an intentional “change of licensing policy”, but an unfortunate side effect of updating our licensing technology for SLM (stand-alone) seats to be in sync with our NLM seats for all AutoCAD-based products. I can only apologize for this new …
I was horrified to learn (in this Autodesk Discussion Group thread) that Autodesk has changed the rules as far as the way Raster Design licenses are handled. It’s quite possible that Autodesk has also done this with other products that I’m not yet aware of. If so, please comment and let me know.
If you’re not familiar with Raster Design, it’s an Autodesk add-on that adds raster handling capabilities to AutoCAD and AutoCAD-based products. The change that has been introduced is that the licensing method of AutoCAD and Raster Design now has to match. That is, if your AutoCAD is standalone, the network version of Raster Design won’t run on it, and vice versa.
Why does this matter? Let’s say you’re a CAD Manager in this scenario:
You have a hundred AutoCAD users, half of which are full-time users with standalone licenses and the other half who are mainly part-time …
Evan Yares has provided more information on the incident I mentioned in my last post. Here it is:
It was years ago. My guess was that the person who did it was just trying to spider the website pages, for marketing research, and didn’t realize he got all the libraries too.
In any event, I said hey you did this, they said no we didn’t, I produced download logs, they said there was no agreement and even if there was we hereby cancel it, I said if you want to see our libraries I’ll send ’em to you no strings, they said no thanks, then I just let it drop. Of course, I’m paraphrasing.
I wasn’t going to get in a fight with Autodesk. Trying to trick them into joining the ODA would have been both futile and dumb. I’d been trying for years to get them …