Autodesk wants your input again in its annual API survey. This used to be a closed survey for Autodesk Developer Network (ADN) members, but has been open to all for the last few years. If you do any AutoCAD-based development at all, I encourage you to take part. That includes those of us who do most of our development in LISP.
Here’s the direct link to the survey. As you can see if you click the link, there’s a lot of stuff in there that assumes you’re keen to get developing for AutoCAD WS. If you’re not quite so filled with Cloudy enthusiasm and would prefer Autodesk to expend its resources elsewhere (on fixing and improving Visual LISP, for example), please fill in the short survey and say so. It closes on 22 June, so you only have a week.
Why bother, when it’s obvious that …
In a comment in response to my AutoCAD 2011 Help system is not popular post, Autodesk’s Diane Serda acknowledged the problems, offered apologies and posted a link to a CHM version of the Help. From Diane’s comment:
We have posted the zip file for download here: http://usa.autodesk.com/adsk/servlet/ps/dl/item?id=15068206&siteID=123112&linkID=9240618
1. Download the AutoCAD2011CHMHelp.zip to your local drive (such as My Documents\AutoCAD2011Help).
2. Extract the zip file to this same folder.
3. To access the CHM Help, you’ll need to click on acad181.chm or create a desktop shortcut.
You can also point to the locally installed HTML help by turning on the local help checkbox under Options, System. You can also access the PDF’s from the Online Help Home page under Online Resources. http://docs.autodesk.com/ACD/2011/ENU
Thanks, Diane! That saves people from having to do inconvenient and dodgy things like downloading a demo version of an AutoCAD …
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’s time to examine how Autodesk has reacted to the widespread criticism of Revit 2010. Is Autodesk listening? To be more specific, is Autodesk’s Revit team listening?
It has been good to see extensive public participation by Autodesk people in various discussions in different places. The Revit team isn’t hiding. It is asking for feedback on the Autodesk discussion groups, the AUGI forums and its own blogs, and getting lots of it. Much of it is negative, but it is to Autodesk’s credit that I’m not seeing much in the way of denial, or demands that the criticism must be constructive. I’ve been trying in vain for years to convince some people at Autodesk that denial is counterproductive and that criticism doesn’t have to be constructive to be useful.
The sort of messenger-shooting that I’ve seen some Autodesk people do from time to over the years (*cough* …
Update (nee Service Pack) 3 for AutoCAD 2009 is now available. See Between the Lines for full details. As always, read the readme first. Here are the links:
AutoCAD LT 2009
AutoCAD 2009 for Revit Architecture
AutoCAD 2009 for Revit Structure
No word yet about related updates for the vertical products.
While I’m not convinced by some aspects of the recently introduced multiple-update-per-release regime, I do approve of Autodesk continuing to maintain 2009 after 2010 has been released. People have complained about this not being done in the past, and on this score at least, I have to say that Autodesk has listened.
What do you think about these updates? Do you use them? What about CAD Managers using deployments; do you deploy the updates? Is it too disruptive? Does it cause problems with the deployment no …
I hesitate to cover this subject because my understanding of Revit is very close to nil. I’m going to cover it anyway, because it relates to the Does Autodesk Listen? theme that I’ve discussed here in the past.
Revit 2010 has appeared with a Ribbon interface, and many users don’t like it. Some well-known Revit users, including bloggers, former Autodesk employees and Revit founders, have railed against the new release. Autodesk has been accused of ignoring long-standing wishlists and pre-release feedback. Autodesk has (it is said) wasted precious development resources by introducing a badly-designed and poorly-performing pretty new face at the expense of solving long-standing and much-requested improvements to the core product. The main complaint appears to be that Autodesk didn’t do much with this release, other than introducing an interface that doesn’t work as well as the one it replaced.
All this will sound very familiar to …
I frequently see people remark that Autodesk doesn’t listen to its customers. I’ve made that remark myself in relation to certain specific items, most recently the botched discussion group update. Of the six Rate Autodesk polls, the Listening to its customers poll shows easily the biggest bias towards the wrong end of the graph.
Now I happen to know that Autodesk goes to some lengths to find out what its customers are thinking (more on that later), but still this feeling of being ignored persists among its customers. Why is this so? Why do so many of you hold this view? I have my own thoughts about this, but right now I’m more interested in yours.
I’d like to see some examples that make you think that Autodesk doesn’t care about your viewpoints, wishes and desires. If you can suggest ways in which Autodesk could do things better, let’s …