AutoCAD 2010/2011/2012 DWG Format

[#1]

I will have to re-nstall Map to verify it but I don't recall having that problem. Also if it's true they plan on removing the classic menu either they have stats showing that very few people are using that UI or they are completely losing touch with what makes ACAD the best to use due to its flexibility.

[#2]

I agree, I prefer the classic menu.  I tried the ribbon, but it doesn't work for me.  I don't think Autodesk ever bothered to check stats on who is using what, it's just a matter of keeping up with the software industry leaders, i.e. microsoft, and what they are doing.  I don't mind the ribbon in Word, since I only use a handful of commands in Word.  But in Autocad I use multiple custom toolbars and menus, and I can't see them all at once on the ribbon.

[#3]

How the HELL did I not know about 'cal?! This is miles better than QC, ok ignore my previous post.

[#4]

What about something like this, for example:

Release 2013 (or whatever you have in development currently). When using that platform, let's say there is a release after it, like 2014, and someone sends you a file that is saved in 2014 platform.

Instead of saying 'file is incompatible' How about giving an option where you click on the file, and it offers you the option to save it to your desktop, in a version that you can view?

It certainly beats emailing back and forth with your client, architect, whomever, to please ask them to save it down to a release that is compatible with your system.

Every so often I do get files like that, when using rel 2012. Is it possible that it's not just that it's a file created by a later release, could a dwg file made by AutoCAD Architectural not show up on straight AutoCAD?

Alot of times incompatible files come from countries outside of the U.S., but recently I did get sent a file that was sent to me from a client in a neighboring state. It just seems unprofessional to ask your client to please resend a compatible file.

[#5]

Unfortunately BIll, that conflicts with the Autodesk business plan to extract as much money from it's users as possible.

If they were to make dwgs backwards compatable, that would remove the incentive for most users to upgrade or stay on the subscription service. We sure don't upgrade for the new bells and whistles. I can only see actual, functional performance/productivity improvements roughly every 3 years as it is.

Then you fall prey to their "implementation" scheme. Try learning to run Autodesk Storm and Sanitary Analysis without any training. There was nothing wrong with Hydraflow, but they see the need to integrate their software to the point of destabilizing the whole process. As far as I'm concerned... I don't intend to be a programmer or guru. I want to simply run the software without this xml file manipulation abominiation. Oops... rambling. Sorry.

It is a great idea, and Autodesk can fix it by requiring software subscriptions for all it's software. That's where the big developers have been leading us for the past decade, so expect to see it soon.

[#6]

Whaaaa...??? Make sure to watch out for those unmarked helicopters...

How do you expect software to suddenly work with a new format, new data, new features, without any sort of changes?  For a previous release (in otherwords, already released and installed!) to open a newer format, it would have to understand all of that.  Not going to happen without a patch or upgrade.  And that may not be possible without the supporting code for the new data in the file, and eventually you end up with the new release anyways.

Now, they *could* in theory create an forward compatible file format.  But that would require a lot of forward planning and thinking, anticipating operating system and programming developments for a decade or two, and for the users to accept that anything that can't be fit into that will never be implemented (storm systems?  To bad, won't work.).  On top of that, such formats require such work there is no budget to also engineer a system to translate older versions of that format forward.

Short version: there are genuine reasons, and it has nothing to do with moustache-twirling monocle wearing "bad guys".

[#7]

Forward compatible?? Umm isn't that all files. My Autocad R10 files are "forward compatible" to Autocad R19 

In all seriousness it isn't inconceivable for them to release a 'Save As' independent routine that existing customers could download at the next major upgrade. The routine would be useful for the 3 year lifecycle of the product and it would save many headaches and wasted time amoungst their customers. Also I would not expect it to save as anything older than the last version so for example 2013 > 2010 but not 2013 > 2007.

[#8]

Autodesk has released a freely usable, no cost conversion utility, that will open current version-level dwg files and save back to earlier versions....  Look for TrueView 2013.  It's been around for a few years now.

Helpful, but does not really _solve_ the issue of incompatible drawings.  Perhaps a better approach in contracts with subs/partners would be to specify that all shared desing files are required to be delivered in OpenDWG format?  As documented by ODA

[#9]

Good point about TV. +1

Still think it would be easy for them to also add an update to previous ACAD versions that would allow them to 'save as' a drawing upon opening. They've already offered a program that will 'save as' so why not just take it a step further. Again I don't think it would be that hard to do and helps productivity.

[#10]

Same problem though - everything which can do that saveas to previous versions, only operates as high as the version it was released for e.g. TrueView 2008 can't know how to read 2010 DWG format as-released.  It would require enough programming that it would be pretty much the same as TrueView 2009/2010.  Same thing with AutoCAD itself - by the time all the changes are made to the older product there isn't much difference from the latest release which has already been programmed.  Wasted effort all 'round.