According to David Cohn, at yesterday’s blogger event in San Fransisco prior to the 2011 launch, Autodesk provided the following figures:
- 76,000 man hours spent on Q/A of the new release
- 6,000 total code reviews of new release
- 2,000 commands tested
- 4,600 Beta customers involved in AutoCAD 2011
- 1.4M lines of old code were removed
Well, that’s all very nice, but those numbers are completely meaningless without context. Autodesk may as well have just published the equivalent numbers for Release 13; I’m sure they would have looked impressive in isolation.
Did anybody in the blogger audience ask the obvious question?
How do these numbers compare with previous releases?
If so, I’d be interested to see the answer.
If not, why not? I’d like to think that I would have asked such a question rather than sitting there unquestionably accepting whatever was being presented.
I’d like to think …
No, I haven’t written a post containing a summary of AutoCAD 2011 features. I won’t be doing so, either. Instead, I’ll just point you at R.K. McSwain’s excellent AutoCAD 2011 in 3 minutes post on his CAD Panacea blog.
I won’t be ignoring the new release; I will be covering selected AutoCAD 2011 features in more detail in future posts. I just don’t see much point in doing a “me too” post when somebody else has already done such a fine job of it.
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 …
Things have moved on since my first post on this subject in which I passed on the information that Leonard Liang (a former drcauto employee) could help with codes for LT Toolkit orphans. In recent developments
- In a comment in a WorldCAD Access post, Nigel Varley from Australian company CAD International stated that they had bought the intellectual property rights to the drcauto software, and that drcauto codes and software obtained from former employees are illegal.
- Another comment on the same post from former drcauto employee Kevin J Secomb lamented the demise of Gary D’Arcy’s dream and criticised CAD International for indicating in an email to users that they would charge for authorisation codes.
- CAD International created a web page describing the situation with regard to drcauto products, including a statement that it would “offer immediate assistance to those needing new authorisation codes”.
- Deelip …
LT Toolkit from the now-defunct drcauto was an add-on for AutoCAD LT that provided LISP and other capabilities that Autodesk disabled. Autodesk hated this, of course, but the late Gary D’Arcy made sure everything was done legally so it couldn’t be stopped even by Autodesk’s hyperactive legal team.
If you are a user of LT Toolkit and you want to keep using the software now the company has closed down, you may find this information from Evan Yares useful:
I’ve gotten in contact with Leonard Liang, the former key developer at DRCauto. He’s asked me to send any Toolkit Max users to him, and he will help them. His website is www.cadsta.com. His email, at that domain, is “leonardl”.
Source: a comment in this this WorldCAD Access post. If you don’t read comments, you may well have missed this, so I thought it was worth repeating.
One of the blogs I read regularly is Photoshop Disasters, which recently posted a picture of a Ralph Lauren ad. In common with many fashion photos, this showed a skinny model that appeared to have been further skinnified on somebody’s computer to the point that the poor waif was ridiculously deformed. Like this:
Nothing out of the ordinary there, then. Under normal circumstances it would have received a few dozen comments and scrolled off the front page in a week or so, because there is no shortage of bad image manipulation out there for the blog to snigger at. The image was reposted at Boing Boing, but it would still have been forgotten in a week.
Except this time, Ralph Lauren prodded its lawyers into action and demanded the image be removed from both sites, issuing a Full post
As I mentioned in my last post, I had some reservations about the code provided by Autodesk to deal with suspect acad.vlx and logo.gif files. Based on a suggestion from Jimmy Bergmark, I have written my own, safer version which you can download here: clean_virus_safe.lsp.
The comments at the top of the clean_virus_safe.lsp file explain what to do with it, but I will reproduce some of the relevant points here.
- Purpose: Checks for existence of acad.vlx and logo.gif files, which are associated with virus AL/Logo-A, also known as ACAD/Unexplode, ACAD/Agent.A or ACM_UNEXPLODE.B. Written as a safer alternative to Autodesk’s code which deletes suspect files without prior warning. This code renames the files instead.
- Legal: Provided as-is with no warranty whatsoever, use at own risk. May be distributed freely.
- Usage: Append the contents of this file into a startup LISP file (e.g. acaddoc.lsp in your search path – …
Shaan Hurley has posted some useful information about another AutoCAD-based virus that is doing the rounds, and I strongly suggest you read it. However, I have some reservations about the solution that is posted there and in the Autodesk knowledgebase.
The LISP code suggested will delete any files called acad.vlx or logo.gif that are located in the current user’s current AutoCAD search path. There are a couple of problems with that.
- The search path will change depending on the user, the profile, the startup folder and the drawing folder. That means you can’t just use the code once and expect the problem to go away; the code will need to remain in place permanently to ensure it does not recur. That may not be a huge problem, although it will have a performance penalty (particularly where the search path is long and/or includes network paths) …
There is a piece of malware out there written as an ObjectARX application, i.e. it will only affect AutoCAD users. It’s a China-based adware client, which Andrew Brandt at the Webroot threat blog has named Trojan-Pigrig. For full details, see here. Also, see here for AutoCAD-specific advice from the AutoCAD support team at the Without a Net blog.
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* …
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 …
This post is not about the new SpacePilot PRO 3D controller from 3Dconnexion (a division of Logitech). This post is about the Internet coverage of the launch of that new device, journalism, blogging, freebies and ethics.
It has long been common practice for companies to give out free stuff to journalists. Free gadgets, free transport and other expenses for attending events, free beer, free lunch… oh, wait, there’s no such thing. As blogging has risen in prominence, that practice has been extended to providing free stuff for bloggers. It was traditional in the past for such freebies to go unmentioned in reports about the products of such companies. I think the first time I saw this kind of thing disclosed was by Ralph Grabowski, and I was impressed. Maybe it’s just the sites I read, but I see more of that kind of disclosure in blogs than …
I’ve added a link to Without A Net, a new blog on support issues, technical solutions, fixes, and tips for AutoCAD. It’s run by Tom Stoeckel, global technical lead for AutoCAD product support. In my limited experience, I’ve found Tom to be a fine fellow with his customers’ needs at heart. This blog promises to be a worthwhile addition to the existing AutoCAD support mechanisms, and I commend Autodesk and Tom for introducing it.
Autodesk’s Executive Chairman of the Board (who has one or two other little jobs, too) has made a Yahoo! blog post in which she promises to kick a donkey, or something.
Yahoo! if of only tangential interest to me; I don’t particularly care if it thrives or if it dies. However, it’s good to see Carol communicating directly in this way, and it’s good to see her emphasise the importance of looking after the customer, placing emphasis on efficiency over innovation for innovation’s sake, and promising to do better at listening. Welcome to the blogsphere, Carol.
Time to lighten things up a bit, I think. While attending the AutoCAD 2010 product launch in San Francisco on 5 February 2009, I conducted a series of micro-interviews with a collection of AutoCAD bloggers and Autodesk employees. One geek asks 14 other geeks if they are geeks; nothing too serious here. I hope Shaan enjoys my tabloid journalist editing job right at the end.
Thanks to all the interviewees:
Heidi Hewett, Autodesk blogger
Lynn Allen, Autodesk blogger
Melanie Perry, blogger
Robin Capper, blogger
Brian Benton, blogger
Todd Shackelford, blogger
Jon Page, Autodesk person
Matt Stein, Autodesk person and personal blogger
Shaan Hurley, Autodesk blogger
Donnie Gladfelter, blogger
Ellen Finklestein, blogger
David Cohn, blogger
Mark Douglas, blogger
Guillermo Melantoni, Autodesk …
Thanks to Robin Capper for bringing this to my attention.
Disclosure: I’m a software developer, artist (of sorts), copyright owner and part of a company that sells software to allow copyright owners to protect their interests. I’m also the victim of clueless corporations counterproductively interfering with my art. Most of all, I’m a supporter of the fair use of copyrighted materials.
This law in New Zealand needs to be turned back now. If it succeeds in Robin’s country, it will be mine next, then yours. I encourage you to support this viral campaign so it attracts some press attention. Excuse me while I go and turn my gravatar black.
You can expect a lot of AutoCAD 2010 news to start appearing in this and other blogs today and over the next few days. I’m just about to start interviewing some Autodesk people about this and other subjects. Watch this space!
Although I want to keep my list of links reasonably compact, it should not have taken until now to add the AutoCAD Insider blog of Autodesk’s Heidi Hewett to the list. Heidi’s idea of going through the AutoCAD alphabet is a great one, and I wish I had thought of it.
blog nauseam has been light on for AutoCAD tips and information lately. Although that’s going to change for the better soon, there’s plenty of that kind of stuff on Heidi’s blog to keep you amused in the meantime. It’s useful stuff for all AutoCAD users, explained well.
Oh, and Heidi, the Boundary command was (kind of) added in Release 12, except it was called Bpoly at the time. It was renamed to Boundary in Release 13. The Bpoly command lives on to this day, doing exactly the same as Boundary.
Thanks, Ralph, for this little gem of a typo in the latest upFront.eZine:
IntegrityWare announces tits new Extreme Performance Library