upgrading to 2018 Civ3D

[tim_newsome]

I am hearing that 2017 Civil 3D will not support Civil 3d proxy objects from any previous versions.

Is this true?

What will be a simple process for transition with so many company projects done in 2016 hen we upgrade to 2018 here in very short time?

[Jmurphy]

I am hearing that 2017 Civil 3D will not support Civil 3d proxy objects from any previous versions.

Is this true?

What will be a simple process for transition with so many company projects done in 2016 hen we upgrade to 2018 here in very short time?

Those that know can't say yet, those that say don't know. Still a few weeks/months before it gets released.

[cadtag]

Historically, forwards compatibility has been maintained. Backwards --- not so much. Seems like the folk in the Adesk C-Suite are not fans of interoperability, even with their own products.

If suddenly Autodesk eliminates the forward compatibility path, and requires all users to recreate their C3D objects from scratch.... there would be a new C-Suite rather quickly.

(and as Murph noted, I don't _know_, thus I can say )

[rkmcswain]

I am hearing that 2017 Civil 3D will not support Civil 3d proxy objects from any previous versions.

Did you mean to say 2018, above?

Because 2017 is not backwards compatible with earlier versions of C3D. No secret there.

[tim_newsome]

I am not sure if my question (second line) was read before replying. I will try to reword it if it did not make since.

Once I upgrade to 2018 will the 2016 Civ3D 2016 dwg proxy objects translate to version 2018 just by opening them with 2018?

[rkmcswain]

I don't know what you mean by "2016 Civ3D 2016 dwg proxy objects".

Are you talking about general Civil 3D objects such as cogo points, surfaces, corridors, etc.?
If so, if they follow the same trend of the last dozen years or so, then yes. Drawings and object have always been forward compatible. But only backwards compatible in releases 2013-2016.