Opening 2010 dwgs in older version disables commands

[ronpemberton7479]

When I open a 2010 version dwg in V2008 I get the following message.

"This drawing was created with a newer version of Civil 3D. All entities created by Civil 3D within the drawing are in a proxy state.
Additionally, all commands, settings, and displays of Civil 3D are disabled for this drawing."

I can see why objects created with new features are in a proxy state but why are all commands, settings, and displays of Civil 3D disabled?

I tried having the drawing saved back to V2007 but I get the same message when I open it. How do I get around this so I can continue
editing the drawing in V2008?

[Anonymous]

You will NEVER be able to edit the 2010 file in ANY previous version. You
can XML out all of your design data from 2010 then open a new file in 2008
or whatever, then XML in that data.

--
Matt Kolberg
Global CADD Systems - A division of Cansel

"ronpemberton7479" wrote in message news:6343594@discussion.autodesk.com...
> When I open a 2010 version dwg in V2008 I get the following message.
>
> "This drawing was created with a newer version of Civil 3D. All entities
> created by Civil 3D within the drawing are in a proxy state.
> Additionally, all commands, settings, and displays of Civil 3D are
> disabled for this drawing."
>
> I can see why objects created with new features are in a proxy state but
> why are all commands, settings, and displays of Civil 3D disabled?
>
> I tried having the drawing saved back to V2007 but I get the same message
> when I open it. How do I get around this so I can continue
> editing the drawing in V2008?

[ronpemberton7479]

Is 2010 coding that much different or is this just a strongarm sabotage by Autodesk to force upgrades?

[Anonymous]

Unfortunately, you can't. You can take the 2010 dwg, export it to Acad,
then open it and go to town, but as long as you have C3D objects, you'll
be locked out of C3D commands in prior versions.

HTH,
JW

[Anonymous]

Your guess is as good as mine, but this is how it was explained to me.

It would take an enormous effort to make everything backwards compatible.
It would effect the price of the software negatively. We could think of
maybe showing the new objects as proxies and allow us to add objects from
the current version. I have no idea what goes on under the hood, but I
doubt it's a conspiracy. I just think it's pretty tough to make everything
round trip-able.

--
Matt Kolberg
Global CADD Systems - A division of Cansel

"ronpemberton7479" wrote in message news:6343650@discussion.autodesk.com...
> Is 2010 coding that much different or is this just a strongarm sabotage by
> Autodesk to force upgrades?

[Sinc]

It could be done without having a dramatic impact, but not without fundamental changes to the current design of Autocad. At this point, it would take extensive rewriting of existing code, including a lot of code that has been there for years or even decades, and essentially require a replacement of much of the current "DWG technology". That's probably why it is considered to be "not worth it", despite the nightmare it creates for the users.

That's why I'm such a big advocate for a change to the annual release cycle. A new incompatible release once every two years would create less than half as many problems as we have now. If we must have incompatible releases, it would be much less disruptive if we had fewer of them. Then just give us more in the way of Subscription Advantage Packs in those off-years that don't have a new release.

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

[Anonymous]

Would you be willing to wait two years, or likely four for new features
to be considered? As a rule, new full-blown features can only be
included at full releases, based on the language and support
requirements. There is a certain amount of flexibility afforded by the
current system that allows Autodesk to focus on market requirements and
user demands much quicker than they could in a two-year cycle.

I'm not saying there aren't problems with the annual release treadmill,
but I think many people overlook the advantages in terms of their own
demands.

JW

[Sinc]

I don't really understand why those are the only choices.

Why can't we have a major release every other year, with a major add-on upgrade in the off-years? One that doesn't require a new incompatible format every year. True, that won't work with the three-year DWG format cycle, but that was always rather artificial, too.

It is frankly impossible for every company to switch versions of C3D at the same time. Working in multiple versions of C3D at the same time is distasteful on many levels. But working with others who are on a different version of C3D is pretty much impossible. A two-year cycle would naturally result in a lot fewer disconnects, as people would tend to switch more together. As it is right now, there are an awful lot of people who seem to be skipping every other release, and that causes problems when one company is on odd-numbered years, and another is on even-numbered years, and they need to do a project together.

This problem may not be so bad yet, but I think that's only because hardly anyone is using C3D right now. Personally, I think the software has gotten much better, and a lot more people will start to adopt it in the near future. As more and more people start using this software, this problem will get bigger and bigger and bigger...

Not to mention, all of those people are going every other year without even getting bug fixes, under the current system. Every other version simply sits on a shelf, and they wait it out. It seems to me like things could be done better. And a two-year major release cycle may give Autodesk more time to focus on making sure new features are stable - after all, stability is the most important factor in making this software usable. Right now, stability and reliability are far more important than new features.

-- Sinc
http://www.ejsurveying.com
http://www.quuxsoft.com

[Anonymous]

I love this debate. Carry it on for a bigger audience here:
http://www.civil3d.com/2010/02/resolved-the-one-year-release-cycle-is-good-for-civil-3d-users/

JW

[ronpemberton7479]

Some of our seats are just now switching over to 2010 and that’s the problem. Different groups in our office are now not able to work on the same drawings which is a major problem. I’ve never noticed this problem in earlier versions. Our company has over 45,000 employees world wide. I don’t know how many Autocad seats we have total but we cannot switch to a new version every year. Transfering work between groups and offices will come to a screeching halt until we get this compatibility problem resolved. I can’t believe this issue was not anticipated by Autodesk. The whole AutoCAD world is not going to upgrade with every release. We need to have a huddle in the company to try and figure out our options.

[Anonymous]

how would a 2010 product know what to do with a brand new object that was
added to 2013? Yeah there are issues but it isn't anything others haven't
had to deal with, go ask the Revit guys how they feel about it.

--
Lance W.
______________________________
my advice is congruent and factual..

"ronpemberton7479" wrote in message news:6344166@discussion.autodesk.com...
> Some of our seats are just now switching over to 2010 and that’s the
> problem. Different groups in our office are now not able to work on the
> same drawings which is a major problem. I’ve never noticed this problem in
> earlier versions. Our company has over 45,000 employees world wide. I don’t
> know how many Autocad seats we have total but we cannot switch to a new
> version every year. Transfering work between groups and offices will come
> to a screeching halt until we get this compatibility problem resolved. I
> can’t believe this issue was not anticipated by Autodesk. The whole
> AutoCAD world is not going to upgrade with every release. We need to have
> a huddle in the company to try and figure out our options.

[ronpemberton7479]

As stated above I can see why an older version couldn't deal with new features created in a new version, but when I open a 2010 dwg even created in "vanilla" AutoCAD in C3D 2008 it disables all C3d commands. I can't even label a line created in a 2010 version.

[Anonymous]

[...hardly anyone is using C3D right now....]

You base this information on what? In my experience with my clients the
number is far greater than "hardly anyone", at least in my region.

--
Matt Kolberg
Global CADD Systems - A division of Cansel