3DConnexion device support in AutoCAD

Do you have a 3DConnexion device (3D ‘mouse’) and use it in AutoCAD or AutoCAD-based products? What do you think of the way it works in the most recent releases of AutoCAD? From AutoCAD 2011 on, Autodesk provided built-in support for these devices. Has that made things better or worse than in earlier releases? If you’re having problems, exactly what are they and how does it affect your ability to work with AutoCAD in 3D? Is the 2012 support any better than 2011? How does AutoCAD’s support for these devices compare with that of other products?

Full post and comments

AutoCAD 2012 – Autoloader mechanism for plug-ins

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 APIs, including LISP. User perspective As a user, what this means is that for AutoCAD and related applications from 2012 on, there is a standard loading mechanism for plug-ins. The installation should be straightforward, with no multi-step processes to go through for different AutoCAD variants and releases. The result of the installation should automatically present itself in a standard way, with a short-lived welcome bubble, an extra panel in the new Plug-ins Ribbon tab, plus any other interface additions the developer wants to provide. If you subsequently install another AutoCAD variant or release, the plug-in will automatically appear in that variant with no further user action required, as long as that AutoCAD variant is supported by the plug-in. Developer perspective What this means for me as a developer is that I have much less to worry about in terms of installation. All that needs to be done to make the loading…

Full post and comments

AutoCAD 2012 – Putting things back to “normal”

The most popular post on this blog, in terms of both hits and comments, is AutoCAD 2009 – Putting things back to “normal”. This is followed by AutoCAD 2010 – Putting things back to “normal”, with AutoCAD 2011 – Putting things back to “normal” not too far behind. As it seems many people find these posts useful, here’s an updated version for the latest release. Much of this post is based on older versions, but there are many additions and differences in this year’s “keep off my lawn” post. One thing that’s regularly asked whenever a new AutoCAD release hits the streets is how to make it work like earlier releases. As I stated in my original post, I think you should give any new features a fighting chance before turning them off or ignoring them. But it’s entirely your choice. We should be grateful that in AutoCAD 2012 at least (unlike some Autodesk products), you do still have that choice. At least, you have a choice in most cases. Let’s assume you’ve made the decision to put your environment back to AutoCAD 2008 or earlier; how do you do it? I’ve arranged these items in alphabetical order: Aerial View. The DSVIEWER command appears to be gone, but it’s just hiding. It has been undefined. You can use REDEFINE DSVIEWER to turn it back on, or just enter .DSVIEWER (with a leading period). It may not work perfectly on all systems under all circumstances. Array dialog box. The excellent new associative array features of AutoCAD 2012 have come at the cost of the Array dialog box. While you can use the Ribbon or the Properties palette to modify arrays, if you want to create one you have to go back to the future with a Release 14-style user interface. Using…

Full post and comments

ClassicArray Release Candidate 2

I have now posted the second Release Candidate of ClassicArray™ (version number 0.7.0). The main changes from the first Release Candidate (0.6.0) are: Help documentation, which you can also view here, now describes how to resolve an AutoCAD CUIx loading problem. (The problem is not specific to ClassicArray and can affect any CUIx file that is removed or relocated. More on that in a future blog post). Timebomb mechanism now works 15 days after first use rather than a specific date. Also now allows the interface to still be used (but no arrays to be created) once the evaluation period has expired. About dialog enhanced to show registration information and to provide access to a new registration dialog. Barring disasters, I intend to release ClassicArray in this exact form (except for updating the version number to 1.0.0) in about a week. Please see either www.classicarray.com or the main ClassicArray Beta post for the download, and provide feedback either as a comment on that post or in an email.

Full post and comments

ClassicArray Release Candidate – massive download bloat

I have just posted the Release Candidate of ClassicArray™ (version number 0.6.0). The main changes from Beta 2 (0.5.0) are: Setup executables have been provided to provide easier installation and uninstallation. Pretty comprehensive Help documentation is now in place, which you can also view here if you want to learn about the product without installing it. Bug fixed with Path preview not displaying accurately when no path is selected. Minor cosmetic dialog box fixes. Timebomb has been moved on 7 days to 28 April. Regrettably, the download file size has blown out to 787 KB because of the inclusion of the Help files and setup executables. There are two setup choices; one for all users (requires admin rights) and one for the current user only (admin rights not required). When installing the Release Candidate, it is not necessary to uninstall the Beta first. I would appreciate any feedback you might have, particularly on installation and uninstallation. If there are no significant problems reported with this version, I intend to release it in this form, except for version information and the timebomb mechanism. Please see the main ClassicArray Beta post for the download, and add any comments there.

Full post and comments

Why do you comment here?

One of the things that most pleases me about this blog is the amount of comments it gets. I’m sure there are several AutoCAD-related blogs that are much more frequently visited than this one, especially the Autodesk ones. However, I’m not aware of another AutoCAD blog with the volume of comments I see here. On average, each post here receives just under 5 comments, and the most popular subject for discusssion is now not far short of the 100 mark. I recently went four complete calendar months without making a single post, but comments kept trickling in anyway. When I returned to normal posting, the commenters returned as if I had never been “away”. What’s up with that? I’m curious. Why do you comment here and not so much elsewhere? Or am I mistaken and there’s an AutoCAD blog I’ve forgotten that’s a hotbed of commentary?

Full post and comments

AutoCAD 2012 – Massive download bloat

Note: this post is not an April fool’s joke. It may be ridiculous and hard to believe, but unfortunately it’s all true. After I managed to overcome Autodesk’s obstructive download manger and download AutoCAD 2012, it became available on the Subscription site (when that site wasn’t running unusably slowly). Or it became kind-of available. Here’s what is actually available: AutoCAD 2012 Multilingual 32 bit Download File Size: 2,080,558,319 bytes (1,984.2 MB) AutoCAD 2012 English Korean Traditional-Chinese Simplified-Chinese Win 64bit Download File Size: 2,240,915,999 bytes (2,137.1 MB) These file sizes are roughly double those of the AutoCAD 2012 English files I’ve already downloaded from the trial page and installed. The 32-bit English file is 1,144,011,680 bytes, or 55% of the size of what the Subscription site is trying to offer me. Why? Because the Subscription downloads contain three bonus Asian language packs. It has apparently escaped Autodesk’s notice that Australia is an English-speaking country, and that the ability to install a Korean version of AutoCAD 2012 isn’t going to be spectacularly useful here. Duh! There was a a distribution fiasco last year when Autodesk couldn’t make up its mind which AutoCAD 2011 language variant Australian users were supposed to use. This resulted in weeks of delays, uncertainty and disrupted shipments. This year, there’s less uncertainty. Somebody has made a firm decision about what we’re getting, right from the start. What a shame it’s the wrong one, and it makes Autodesk look utterly clueless. Just in case you’re wondering, the AutoCAD 2012 English from the trial page installs and works fine, correctly detecting that I’m in Australia and presenting the correct legal information. The installation also registers and authorises correctly using the serial number provided on the Subscription site. No problems there, then. What, then, is the reason for the massive download bloat? Is it…

Full post and comments

AutoCAD for Mac Update 2

As reported on Without a Net, there is a second update for AutoCAD 2011 for Mac. This will be welcome news to those of you who have discovered that AutoCAD crashes when using Copy/Paste after installing the 10.6.7 OS X update. If you haven’t applied Update 1 yet, you will need to do that first. As always, read the readme before applying the update itself.

Full post and comments