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
When is AutoCAD nor AutoCAD? When it’s AutoCAD WS. But it’s not quite that simple.
I’ve been correcting people for months when they say things like “Project Butterfly is AutoCAD on the Cloud.” No, it’s not. It’s a DWG editor of sorts, but anybody who has used both will know that it’s not AutoCAD or anything like it. Although it’s useful for viewing and markup and is improving all the time, Project Butterfly is still very restricted and is likely to remain so for a long time. You wouldn’t want to spend a significant portion of your day drawing with it.
OK, so Project Butterfly isn’t AutoCAD. I’m glad we’ve cleared that up. But wait! Now it is AutoCAD! AutoCAD WS, that is. AutoCAD WS is the recently-announced free iPod/iPhone/iPad app to access Project Butterfly. But it’s not really AutoCAD either, despite being named thus. Confused yet?
AutoCAD is Autodesk’s strongest brand …
AutoCAD Ribbon use (and non-use) may have been the hottest topic on this blog to date, but it’s a storm in a teacup compared with what has been going on between Revit users and Autodesk. More on that later, but for now I’d just like to pass on a statement made by Autodesk BIM Design Product Line Manager Anthony A. Hauck on the AUGI forums that:
Recent data on other Autodesk applications having both the new and “classic” UI show about a 2 : 1 split in favor of the new UI.
I would be interested to know the full details behind this assertion. Whenever I see a baldly-stated statistic like this, my first thought is “where did it come from?” Without full details of the data and how it was obtained, every statistic like this is suspect at best. It could just as easily be useless or misleading. …
Phil Read has, according to him, been re-admitted as an Autodesk University 2009 speaker. Yay!
Is this a victory for people power? A victory for the blogosphere? I rather think it’s just a victory for common sense.
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 …