Category Archives: Bug

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!

I have a real problem with BricsCAD

3 Replies

To be precise, I have a real problem with writing  about BricsCAD. I’ve written some pretty complimentary things about BricsCAD lately. In the interests of balance, I’ve been intending to write about some of the issues people can expect to deal with when moving from AutoCAD to BricsCAD. Such issues certainly exist. The problem I have with that is that the issues keep going away!

Here’s how it usually goes. I find a problem in BricsCAD. I submit a support request. Within hours, I get a meaningful response from a person who understands the issue. Within days, I’m informed it’s been fixed internally and the fix will be in the next update. Within a week or two, that update is released. I download and install the updated version. It’s basically a full reinstall, but all settings are seamlessly retained and it’s faster and less painful than an AutoCAD Service Pack installation. The whole thing from start of download to completion typically takes 5 or 6 minutes. The problem is gone, and I have nothing to write about!

Here’s the latest interaction. This is typical, and has been repeated many times:

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!

 
Now, can you imagine the same scenario with Autodesk? I’m sure many of you have lived through it. First thing would be an automated response. A day or two later would be a confused support person coming up with totally unrelated links to Knowledgebase articles. A series of increasingly frustrating back-and-forth emails might go on for days or weeks until the Autodesk person finally plays their trump card, blaming the third-party routine (incorrectly) and/or stating that they don’t support users’ customization.

Such a problem would stay in AutoCAD indefinitely. Repeated reports, year after year, using subscription support and the forums and formal reporting mechanism in the Autodesk Beta program, would make no difference. Eventually I would give up and the problem would never get fixed. Again, this is typical, and has been repeated many times. This applies to bugs, incompatibilities, feature design, performance issues, user interface difficulties, documentation system idiocy, you name it. It’s massively frustrating and I know many very smart people who have given up even trying. The only exception is documentation content; that gets fixed as soon as possible, within the limitations imposed by Autodesk’s arcane systems.

The difference in attitude between Autodesk and Bricsys is glaring, stark, obvious. Autodesk pays lip service to providing customer service and software quality. Bricsys just gets on and does it.

So what’s actually new in BricsCAD V17?

4 Replies

A big problem I have in communicating the improvements to BricsCAD in V17 is that there are such a huge number of them. This isn’t an AutoCAD 201x-style touch-up masquerading as serious progress, this is a real  upgrade. You know, an AutoCAD V12-style upgrade that veteran AutoCAD users will remember from the good old days before Autodesk got bored and distracted. Dozens upon dozens of new features, improvements to existing features, performance improvements and bug fixes. Lots of stuff that’s genuinely useful.

I could write three posts a week on the changes and not be finished by this time next year. So I’m going to be lazy. I’ll pick out a few features for future posts but for the big picture I’ll point you to the official list. This isn’t a marketing document, it’s a technical list of terse descriptions of changes (to the Windows version only – remember BricsCAD supports Mac and Linux too), and it’s large. To give you some idea of the scale of changes, there are 3,200 words describing new V17 features, for example:

DMDISTANCE3D Specific measuring modes for cylinders, circles, and spheres have been introduced. Distance can be specified between boundaries (nearest points), central points or axes of the corresponding geometries.

 
There are 1,600 words describing improvements, such as:

IMAGEATTACH Multiple selection of images from a single folder is supported now so multiple images can be attached in one go. This is especially useful for images with geo-information attached.

 
There are 1,450 words describing fixes, like:

MATCHPROP When the source entity was non-annotative and the target annotative, the target undesiredly remained annotative.

 
There are 1,100 words describing API changes and fixes, e.g.:

BRX/LISP/SDS wcmatch() now supports the (undocumented) space character as a pattern key to match any contiguous sequence of whitespace characters (space, tab)

 
That last one is a fix for a bug that I reported in V16. Within ten days of submitting my report, I was informed directly by the developer that the fix had been done and would be available in V17. Here’s another one of mine:

BRX/LISP Improved sds_getFiled() / (getfiled) behavior during a Save operation when default filename argument is empty.

 
Elapsed time between my report and acknowledgement by the developer that a fix would be forthcoming? Just under 12 hours. Less than 3.5 hours after that, I was informed that the fix had been implemented. Hands up all those people who have had similar experiences with Autodesk?

Magical disappearing AutoCAD 2017.1 crash information

1 Reply

In preparing to write something about the AutoCAD 2017.1 non-subscription-only update, I came across something slightly strange. Google AutoCAD 2017.1 crashes and you will probably see something like this:

autocad2017-1crashgoogle

What happens if you click that link? Nothing useful. You’re just taken to the landing page for the Autodesk Knowledge Network. The Google cached version of the link takes me to 404 land. Searching within the Autodesk Knowledge Network doesn’t produce relating to the crash in the original link, which seems to be language-pack related. The search wasn’t entirely fruitless, because I did discover that 2017.1 breaks linetype preview images for those of us who prefer a light user interface. But of information about the crashes, I see no sign.

On Twitter, I see a similar story. Some weeks ago, the @AutodeskHelp account reported:

autocad2017-1crashtwitter

Click that link (which points at a page called AutoCAD-crashes-when-you-install-AutoCAD-2017-1-English-Update-on-computers-with-installed-language-packs.html) and you will pay an unenlightening visit to Page Not Found World.

I’m baffled. It’s almost as if somebody at Autodesk has tried to hide something about this all-important first new-regime update and not done a very good job. Nah, can’t be that, there must be an innocent explanation.

If anyone has any information on this or any other 2017.1 crash or instability issues, please let me know.

Dear Autodesk Recap 360 team…

2 Replies

…your software (3.0.0.52, came with AutoCAD 2017) fails to allow sign-in (a prerequisite to connection to the cloud) in a secure proxy server environment. This happens (see picture):

autodeskrecap360cantsignin

I am online. I did try to inform you about this problem using the feedback mechanism in the product. This allowed me to type my problem report, but on hitting the send feedback button, I got this (see picture):

autodeskrecap360cantsignin2

I am connected. In fact, I’m so connected I’m typing this post online while reproducing the problem. While this is going on, I’m able to sign in to Autodesk Account, A360 Drive, AutoCAD Beta forums, the Autodesk public forums and so on. What’s happening is your software is trying to do something our firewall doesn’t like. Autodesk has an unfortunate history of doing this sort of thing. Often, things that worked in one release will stop working in the next, and vice-versa, because somebody tinkered under the hood. For example, Application Manager works, desktop app doesn’t. There have been many other examples going back over a decade.

No, please don’t direct me to the knowledgebase article that expects me to drill a bunch of holes in the firewall. That’s not happening. Instead, make your software work nicely, please. Find the bits of code that work, make them standard, and insist your developers use the standards.

Just thought I’d let you know. Other people in the same situation would probably just give up, and you would never know it was happening.

Hotfix for AutoCAD 2017 SP1 Autoloader bug

2 Replies

As reported earlier, AutoCAD 2017 SP1 breaks third-party add-ins that use the officially approved Autoloader mechanism. Autodesk is to be commended for acting quickly to produce a hotfix for this. In order to make this hotfix available quickly, Autodesk has taken the very unusual step of allowing a third party to distribute it. See this post from Jimmy Bergmark, who pointed out the bug in the first place. Kudos to whoever at Autodesk made the call to think outside the box to do this. It’s a very un-Autodesk Corporate thing to do, and particularly commendable for that very reason.

It’s important to note that because of the way Service Packs are now handled in AutoCAD and the vertical products based on it, this SP1 bug affects all of those products, not just base AutoCAD. Here is the list of affected products*:

  • AutoCAD 2017
  • AutoCAD Map 3D 2017
  • AutoCAD Civil 3D 2017
  • AutoCAD Mechanical 2017
  • AutoCAD Electrical 2017
  • AutoCAD Architecture 2017
  • AutoCAD MEP 2017
  • AutoCAD P&ID 2017
  • AutoCAD Plant 3D 2017
  • AutoCAD Utility Design 2017

*See links in comments below for further information about this.

Having heaped praise upon Autodesk for acting so quickly, it still needs to be said that Autodesk has done the wrong thing very quickly. Customers who go along with Autodesk’s continuous update push will see third party applications failing. The third party developers will be getting support requests from those customers and will have to persuade them a) that it’s Autodesk’s fault, and b) to go and deal with a manual hotfix that requires admin rights and requires copying/renaming things in Program Files. For customers without sufficient confidence to do that, or for whom just getting permission from IT to perform admin-rights operations is onerous, that’s pretty inconvenient.

It is wrong for Autodesk to offload the consequences of its incompetence onto its victims. Those customers and developers who have simply followed Autodesk’s direction and done nothing wrong deserve better than this.

What should have happened? SP1’s immediate withdrawal. It should be pulled now and reintroduced later (perhaps as SP1a) with this bug fixed. Given we’re only talking about one file, a week or two should do it. The hotfix should remain available for those customers who have already installed SP1, wish to keep it in place, and are happy to do the manual hotfix steps.

The lesson for customers and developers is not to blindly follow Autodesk’s direction. Make your own informed decisions about how you use, manage and develop for Autodesk products.

There are lessons here for Autodesk, too.

  1. Test stuff properly before releasing it. If serious bugs like this are discovered, delay the release until they’re fixed and retested.
  2. When you do screw up, fix it not only quickly but correctly. Don’t offload your problems onto your customers and developers; clean up your own mess.
  3. You’re not competent enough to do the automated continuous update thing. Your customers won’t trust you to do it, and they will be right. Give it up.

If item 2 above involves extra inconvenience and expense, so be it. It’s part of the cost of doing business; people pay a lot of money for Autodesk software, particularly if they’re forced to rent it. But doing item 1 right is actually cheaper and it means item 2 is much less likely to be relevant.

Will Autodesk learn from this? Unfortunately, I can’t be confident about that. I’ve seen too many such lessons unlearned or simply ignored over the years.

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?

AutoCAD Help suckage to continue – confirmed

5 Replies

In a recent post on Between the Lines, Shaan passed on the following response from the AutoCAD Team:

There has been some recent discussions about the built-in help system in AutoCAD 2013, both positive and some criticism.  As our longtime users know, AutoCAD help has been through many evolutions.

We are particularly proud of the new AutoCAD 2013 online learning environment we recently released (AutoCAD Online Help Mid-Year Updates.) This update addressed several user requested fixes and changes, and we will continue to take our direction from our user’s feedback.

We do recognize that the online learning environment may not be the solution for every user, so while we are focused on creating a rich and personalized online experience, we will continue to maintain our current basic offline experience.

(The emphasis is mine). This statement, although couched in marketingspeak, confirms what I’ve had to say on the subject. Here’s my translation into plain English:

AutoCAD 2013 Help sucked, the customers said so, the recent update improved matters somewhat for online users, but the awful old system stays in place for offline users. The offline system is in maintenance mode, and the experience will continue to remain basic (i.e. it will suck long-term).

There’s no mention of correcting this situation; it’s clearly a matter of policy rather than some unfortunate accident.

Today, I was using Autodesk Navisworks Manage 2013. As you might expect from an Autodesk product, it’s powerful but unstable. In addition to the lockups and crashes, it has various bugs and annoyances. In looking for a way of working around one of the annoyances, I delved into the Help system. Strangely enough, this product (much younger than AutoCAD) uses something that looks remarkably like an old-fashioned CHM-based Help system. It worked offline. It was quick. It had contents, search and index tabs, and they worked on a Windows 7 64-bit system. It had a hierarchical structure and a breadcrumb bar that helped me understand the context of what I was reading. Using it was, in short, a breath of fresh air.

Memo to Autodesk: if you’re going to try to make online Help look good by mangling offline help, you’re going to have to do this to all your products at once to make it remotely convincing.

AutoCAD 2013 – Using Help in anger

3 Replies

Trying to be fair, I decided to put aside my initial hostility to the AutoCAD 2013 Help system and use it for real. I used it in a realistic situation, to find out how to work with something new or changed (model documentation) as I was working through it with my own example drawing. Try as I might to give it a fair go, I could only get so far before I got irritated. Using it in anger might not be an entirely appropriate phrase for it, but it’s not that far off. Using it in annoyance, perhaps? Here’s how it went.

I hit F1, wait for it to finish loading itself, click in the search box (because that’s not where the focus is to start with), type ‘model documentation’ and pick Search (because Enter doesn’t work). I then wait again, for about 10 seconds, even though I’ve configured it for offline use. Eventually, there is a huge mass of results displayed, almost all of which are totally (totally!) irrelevant to model documentation. Most of them are relevant only to ARX programmers dealing with completely unrelated matters.

If I use the “phrase” option rather than “and”, the list is much shorter and has a much higher proportion of results that have some relevance, but there are still completely pointless results. For example, the 4th result is About Performance Considerations (AutoLISP), which does not contain the phrase at all. It does contain the words ModelSpace and Document, but not together. It does not contain any information remotely related to model documentation. Didn’t Autodesk buy a search technology company a while back? If that company’s technology is in use here, then Autodesk bought a dud.

At least the top two results directly relate to what I need, so I’ll move on with those. They are Commands for Working With Model Documentation Drawing Views and About Model Documentation. The content of the former page is OK; it’s just a list of commands. There is some pointlessly wasted space at the top of the page that means I have to scroll down to see the bottom of the list, but other than that it serves as a useful reference. The latter page is also fine. It’s an executive summary of the feature with a few relevant pictures, followed by a decent set of links pointing to relevant pages that expand on the subject and explain how to do various tasks associated with it. Now I have overcome the inadequacies of Search and determined that useful Help content is all there, that’s all good then, isn’t it? Not really, I’m afraid.

If Help was being run from a real browser, I’d be able to keep both of those starting pages open with their useful links, then middle-click on each of them as needed to open each useful page in a new tab. However, Help isn’t being run like that. It’s being run from inside Autodesk’s pseudo-browser thing, which only allows one page at a time to be displayed. To be fair, this restriction also applies to the old CHM-based Help to some extent. However, the old CHM Help is split into multiple sections, and it is possible to have multiple CHMs each open in their own windows. For example, I can have the AutoCAD 2010 main Help and Developer Documentation open at the same time, something that’s very important for my productivity and which I would find extremely difficult to give up.

To work around the tabless nature of 2013 Help, I need to choose one particular page and stick to it. When I need another page, I need to navigate back up to one of the original links pages and then back down again. That would be bad enough if navigation within the pseudo-browser was good, but unfortunately it isn’t. Despite what looks like a breadcrumb feature at the top of the page, this is non-functional because of the lack of a hierarchical structure to the content. It just keeps taunting me by saying ‘Home’ and nothing else, pointlessly wasting a swathe of vertical space. There are back and forward buttons in that space, but the back and forward mouse buttons I can use everywhere else do nothing in this browser. You can use Alt+Left and Alt+Right to back and forward. Don’t go too far back, though! If you do, the Search panel goes blank and can’t be restored by going forward again, or by switching between Favorites and Search. To fix this, you can close and restart Help , or pick the Home button and wait about 6 seconds for it to get its act together and restore the Search panel. Then you’ll be at the home page, which may not be where you wanted to go back to.

All right, so I have chosen the single page I’m allowed to have open and I want to use the features it describes. This test PC only has a single 1280 x 1024 screen so there really isn’t room for both AutoCAD and Help at the same time, a situation that will be familiar to users of notebooks. I click on the AutoCAD drawing area behind the Help window, expecting AutoCAD to come to the top and to go behind it. Nothing happens, other than Help losing focus. Help stays on top, obscuring the drawing area. If I click the main AutoCAD taskbar button (this is in XP), that minimizes both Help and AutoCAD. Restoring AutoCAD also restores Help, so it still obscures the drawing area. The two windows are linked, and not in a good way for somebody with one screen. I guess some users will want Help to stay on top, but there are plenty of others who won’t, so what could Autodesk have done to keep everybody happy? Made it configurable, obviously.

Eventually I worked out that I could work on AutoCAD if I explicitly minimised the Help window, so away I went. I used the Commands for Working… page, then the VIEWBASE page to start my model documentation experiment. I then picked another link from the VIEWBASE page, the Drawing View Creation Ribbon Contextual Tab page. Having finished with that, I wanted to get back to the Commands for Working… page, so instead of picking multiple Back buttons (which as noted above is fraught with danger if you do it too often), I clicked on that result in the Search panel on the left. Did this take me back to the Commands for Working… page? No, it did not. It did nothing at all. To make it work I had to click another search result first, and only then the one I really wanted.

One saving grace is that I discovered that if I right-clicked on a link in Help, I could copy the URL and then paste it into a proper browser. This works both on and offline, and allowed me to work around many of the problems noted above. This kludge doesn’t work for search results, though, only for links in pages.

I’ve given AutoCAD 2013 Help a decent go, as much as the average reasonable person would before giving up. Maybe more so. I feel pretty comfortable about giving it what I consider a fair assessment. The content of the Help pages itself looks pretty good to me, at least for those pages I visited and the context in which I was using them. If you already know what command you’re supposed to be using, you just hit F1 from within that command to get at the page you want and you don’t need to go any further, you could well be satisfied. But if you’re using the system in any other way, there’s no getting away from it, it’s a crock. The content is not the problem, it’s the loss of structure to that content, and the browser thing being used to present that content. That loss of structure was A Bad Idea and the browser is a very poor effort. The system as a whole should not have been inflicted on customers.

As a courtesy, Autodesk should do what it did following the 2011 Help debacle and provide a CHM solution for customers to download. It should then go on providing a CHM solution indefinitely, until it can come up with something that is of comparable quality. People are already talking about making their own 2013 CHMs. Autodesk, please do the right thing and save them the bother; let us all know that you’re going to provide CHM as a workaround and get it to us as soon as you can. Don’t worry about losing face by admitting that the 2013 Help isn’t up to scratch. It’s too late for that; we’ve already noticed.

AutoCAD 2013 – Help improved in one area

2 Replies

There’s one important area in which AutoCAD 2013’s Help shines when compared with its immediate predecessors. If you’re a Visual LISP user, you’ll be pleased to know that if you select a function name in the editor (e.g. (vla-get-ActiveDocument)) and hit Ctrl+F1, this now takes you to the appropriate page in the ActiveX and VBA Reference, as it should. In AutoCAD 2011 you just got a cryptic message or a 404 error, depending on the context. In AutoCAD 2012, you were just taken to the front page of Help and expected to find it yourself. Props to Autodesk for fixing this problem.

As a bonus, the reference you’re taken to is still a CHM so it works nicely. The Search tab doesn’t work in Windows 7, but that applies to all CHM Help and it’s Microsoft’s fault, not Autodesk’s. The structured contents and index are fully functional, which makes the whole thing usable even without the search facility.

AutoCAD 2012 drawing mangler hotfix

2 Replies

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.

AutoCAD for Mac Update 2

1 Reply

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.

ClassicArray Beta 2 (0.5.0)

I have just posted the second public Beta of ClassicArray™ (version number 0.5.0). There are some documentation updates (still no Help, though), and the main changes are:

  • Bugs fixed with rectangular arrays where single-row and/or column arrays confused AutoCAD.
  • The command now remembers its settings from one invocation to the next, within a single drawing session.
  • Timebomb has been moved on 7 days to 21 April.

The ReadMe.txt file in the zip explains how to uninstall the old version. Simply delete the old ClassicArray.bundle folder from the place you put it. Replace it with the new ClassicArray.bundle folder from the later zip file. Then try to break it!

Please see the main ClassicArray Beta post for the download, and add any comments there.

AutoCAD 2012 – ClassicArray Beta

27 Replies

People have already started to notice that AutoCAD 2012 has killed the dialog box interface for the Array command, and not everybody is happy about it. So I guess it’s time to launch ClassicArray™ Beta.

ClassicArray is an add-on for AutoCAD 2012 for Windows that allows the creation of arrays using a dialog box interface similar to that provided in AutoCAD from 2000 to 2011, but enhanced to include new AutoCAD 2012 functionality. I will create another post later have created a Help page that describes ClassicArray more fully, but for now here are the commands ClassicArray adds to AutoCAD:

ClassicArray (short form CA)
ClassicArrayRect (short form CAR)
ClassicArrayPolar (short form CAP)
ClassicArraypAth (short form CAA)

In addition, there are the same names with N appended, which default to creating non-associative arrays. For example, ClassicArraypAthN (short form CAAN) will create a non-associative path array. However, it is easy to create associative or non-associative arrays of any type, whatever command you use to start it. Toolbar and Ribbon buttons are provided. Help is currently non-functional now complete. This pre-release software is time-bombed, meaning it will no longer work after the date shown below.

Here it is to download:

ClassicArray.1.0.0.zip (Shipping product – 850 KB – will not create arrays after 15 day evaluation period
ClassicArray.0.7.0.zip (Release Candidate 2 – 850 KB – will not create arrays after 15 day evaluation period)
ClassicArray.0.6.0.zip (Release Candidate – 787 KB – will not work after 28 April 2011)
ClassicArray.0.5.0.zip (49 KB – will not work after 21 April 2011)
ClassicArray.0.4.2.zip (48 KB – will not work after 14 April 2011)

It’s a small zip file; unzip it and read the readme to see what to do with it run the setup routine of your choice, depending on whether you want to install it for just the current user or for all users. Installation is a matter of simply copying a folder to a specific location; uninstallation is simply a matter of removing that folder. The mechanism I used for this is AutoCAD 2012’s new Plug-In feature. This feature is A Good Thing that deserves to be described more fully, which I intend to do when I get the time.

This is pre-release software. It generally works fine, but it will contain bugs. Please let me know about them, either in a comment here or using my email form. Over time, I expect to update this post with later versions, so I would appreciate it if you let me know the version number along with any other relevant information, such as the AutoCAD variant and OS you have installed it on. If you have any suggestions, of even if it works without problems, please feel free to let me know that, too!

AutoCAD 2012 – Array has good and bad points

19 Replies

For many users, the most useful new feature in AutoCAD 2012 is going to be the updated Array command. It adds a great deal of very welcome new functionality that will provide a potential productivity boost for 2D and 3D users. But it’s from an Autodesk wedded to its infernal 12-month product cycle, so of course it’s half-baked.

The Good

So what’s good about the Array command in AutoCAD 2012?

  • Associativity. By default, arrays are now associative objects. This means that if you want to, say, modify the distance between columns a couple of days after you drew them, you can now do so. If you’re a Ribbon user, it’s easy to change array parameters because when you select an array, you get a Ribbon tab dedicated to just that task. If you’re not, then the Properties palette allows you to do the same thing.
  • Dynamic preview. Once you have set your various options appropriately, you can just move your cursor around and click to choose things like the number of rows and columns.
  • Path option. In addition to rectangular and polar arrays, you can now array along a path such as a polyline, similar to the Measure and Divide commands. But because it’s associative, if you edit the path, the array changes too.
  • 3D functionality. It is now easy to create 2D or 3D arrays with the Array command. You can add levels (Z) to the rows (Y) and columns (X) of arrays, and this applies to all three types of array. You can also provide a elevation increment, which means the items get progressively higher the further they are from the base row. Think of the seating in a stadium as an example, although real seating arrangements are usually more complex than you will see in the Autodesk examples, so in the real world I don’t expect this feature to be used much.

The Bad

So far so good, then. But what’s not so good?

  • 1990s user interface. Can you remember when the Array command had only a command-line interface? Because that’s what it has now. While some of us old-timers may yearn for some aspects of the “good old days” of 1997’s Release 14, I don’t think many of us want to lose truly useful functionality. But that’s what has happened here. The Array command uses the new command line. The -Array command uses the old command line. Nothing uses a dialog box; there’s no ClassicArray command. *
  • Bugs and limitations. The new command line interface ain’t cooked. There are a bunch of bugs and limitations that mean some valid inputs get rejected, some arrays get drawn incorrectly, and some can’t be created at all. There are other aspects of the feature that strike me as not well thought out, such as the extra step involved in creating a non-associative array (not everybody will need or want associativity), or the clumsy way in which users who want to keep existing objects are expected to mess about with a system variable that affects unrelated things. **
  • Missing API. Autodesk’s long-standing grotesque neglect of LISP continues with the new Array object. There is no meaningful ActiveX API for such objects. If you wanted to use ActiveX to create a simple array, you would have to pretty much reproduce Autodesk’s array creation code (it’s an anonymous block, really) and hope you got it right. There is, of course, no documentation whatsoever to help you do this.

On balance, the AutoCAD 2012 Array command should be viewed as a positive, but it could (and should) have been done a lot better.

* Disclaimer: I have written my own ClassicArray™ command, and I intend to provide it as an add-on soon. Watch this space over the next few days for a public Beta. Edit: here it is.

** ClassicArray acts as a workaround for many of these bugs, limitations and design failings.

Is AutoCAD stability getting better or worse?

42 Replies

The term “stability” is sometimes used as a euphemism to refer to how many bugs a program has. I don’t use the word in that way. To me, stability is a measure of a program’s basic ability to keep functioning without crashing or corrupting data. A program can have a thousand tiny irritating bugs and still be very stable. Another program might have only one bug, but if that causes it to crash a dozen times a day, taking down your data with it, then that is very unstable.

So, given that definition, how stable is your AutoCAD, or vertical AutoCAD variant? How often does it crash, or mess up your drawings? How does that stability compare with your experience of earlier releases? How does the stability of plain AutoCAD compare with that of its vertical siblings?

Please add your comments. If this proves a popular topic, I may run some polls.

Dealing with blacked-out leader plots in older AutoCAD

Leave a reply

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 is different because it happens every time, and with all output devices.

What can be done if you are the recipient of such drawings? The -ExportToAutoCAD command, which can be used to create a version of the drawing with most proxy objects converted to standard AutoCAD objects, does not work with Multileaders. So I can see three options, in descending order of desirability:

  1. Upgrade to a more recent release of AutoCAD. Depending on your circumstances, this may not be a practicable solution.
  2. Forbid the use of Multileaders among your users and all parties producing drawings for you. This also may not be a practicable solution.
  3. Explode the leaders. This results in them becoming dumb text and lines, with no background masking. However, the masking can be easily re-established using the Textmask command that is part of the Express Tools.

It fills me with horror to suggest something as awful as exploding anything even remotely dimension-like, but if you have one of these drawings and you’re forced by circumstances to use AutoCAD 2007 or earlier, what alternative do you have?

This, along with various other Multileader design issues (such as non-integration with dimension styles), appears to be a natural by-product of Autodesk’s decision to add these objects part-way through the lifetime of a DWG version. The 2007 DWG format is shared by AutoCAD 2007, 2008 and 2009, but this interoperability issue affects even users of those releases that supposedly share the same format. Users of vertical AutoCAD variants are, unfortunately, accustomed to this sort of thing happening every year.

AutoCAD 2011 Update 1.1

Leave a reply

As I described earlier, Autodesk recalled AutoCAD 2011 Update 1 because it killed AutoCAD under certain circumstances (e.g. plotting with the layer palette open). Now there’s a fixed version available for AutoCAD and LT. There is no news yet about Updates for vertical AutoCAD variants.

If you have installed Update 1 and the hotfix, you don’t need to do anything. If you have not installed Update 1, you should install Update 1.1. If you have installed Update 1 but not the hotfix, you can either install the hotfix or uninstall Update 1 and then install Update 1.1.

For the full story, I suggest you read Tom Stoeckel’s Without a Net post. At the risk of sounding like a broken record (remember those?), make sure you read the readme before installing or uninstalling anything.