Community
Civil 3D Forum
Welcome to Autodesk’s Civil 3D Forums. Share your knowledge, ask questions, and explore popular AutoCAD Civil 3D topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Civil 3D 2017 is not backward compatable.

162 REPLIES 162
SOLVED
Reply
Message 1 of 163
ChrisRS
19247 Views, 162 Replies

Civil 3D 2017 is not backward compatable.

Civil 3D 2017 is not backward compatable.

I suspect that this is the cost of progress, so it OK. Just be aware.

When 2016 was backward compatible with 2015, AutoDesk clearly said so. It would be nice if they spoke as clearly now.

 

 

From the help File:

 

Interoperability Between Versions

This topic describes the behavior when an AutoCAD Civil 3D 2017 drawing is opened in prior versions of AutoCAD Civil 3D.

Objects in a drawing saved in AutoCAD Civil 3D 2017 are available only as proxies when the drawing is opened in a prior version of the software.

Within AutoCAD Civil 3D 2017, set the PROXYGRAPHICS drawing setting to 1 to save the graphics with the drawing, otherwise a bounding box is displayed where the object is located when the drawing is opened in a prior version of the software.

 

Notice whenyou open an older version file:

 

Open_older_drawing.PNG

Christopher Stevens
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

162 REPLIES 162
Message 121 of 163
MGrof
in reply to: ChrisRS

I have been using 2017 for weeks now.  I have yet to find one upgrade in the new version that is going to make me more effective or profitable at my job.  I can however already see thousands of dollars of lost production because of dealing with this update and non-compatibility.  Not to mention the headache of dealing with other consultants still on the old version.  We do not work within a bubble of one office or company. 

 

I used land Desktop 2009 from when it came out until switching to C3D in 2016 to not deal with update issues.  I didn't have an issue for the better part of a decade.  AutoCAD is now forcing everyone into subscription based licenses and mandatory upgrades in  a money grab.  I hope the company realizes these updates anger your customers.  I'm just trying to make noise so that they can think more about this when they try to pull this idiocy in the future. 

 

Autodesk needs to spend 5 years developing and testing a piece of software and get it bulletproof.  Then release it, and don't release a major update for another 5-10 years until they have something game-changing.  The yearly updates are infuriating. 

 

Mark G

Message 122 of 163
Glenn_Rimando
in reply to: rkmcswain


@rkmcswain wrote:
@jmayo and others.... don't get me wrong. I don't like it either. We've got 200+ C3D users here all on 2014 or 2017 or 2014+2017 and no end in sight.

And guess what? 2018 will probably be coming out in the next few months, and who knows if the format will be different again?

It's a huge mess, but what are you going to do? Switch to *****CAD ? No.

Autodesk knows this, so all of this is of little concern to them unfortunately.

They make money by renting new seats, not by making our life comfortable. It's easier to rent new seats when you have flashy new features, which in turn means you need new formats.


The toughest part to swallow is the lack of being able to switch between versions (2013-2016) which I feel in the past few years our local industry in the northwest as well as the rest of the country have gotten used and have become a integral part of the work flow.

 

Losing this flexibility is the root of most peoples frustrations as well as the lack of Autodesk to recognize the importance of this flexilbilty.

 

I mentioned before most of us using civil 3d in the northwest region are sticking w/ c3d 2016 for the time being and it maybe years before we jump to a newer version (2017 and beyond) since we depend on this flexibility for work flow within the office as well as out of the office when working w/ clients and other consultants. 

 

I have 2017 on my machine and i'll only use it to convert pdf's to cadd, other than that the functionality is the same. We've tested a few project in 2017 and have since painfully saved them back or redid them in 2016 since it caused more trouble than it was worth at this point in time. Other than the lack of flexibility w/ the older formats its a great product and I look forward to using it the future!

 

 

 

 

Message 123 of 163
jporter
in reply to: MGrof

A little history. . .

  • In order to get a Civil 3D 2007 drawing back to 2006 you had to export to AutoCAD and export to Land XML.  In 2006 you had to import the AutoCAD file and import the Land XML and then you can continue working.  
  • Same goes for 2008 to 2007
  • Same goes for 2009 to 2008
  • Same goes for 2010 to 2009
  • Same goes for 2011 to 2010
  • Same goes for 2012 to 2011
  • Same goes for 2013 ti 2012
  • From 2013 to 2016 the Civil 3D data had no major updates, therefore there was very little need to convert using the export methods described in the previous posts.  
  • In 2017, after listening to some requests on updating specific content, Autodesk upgraded the Civil 3D data.  Now we're back to the export methods.  

None of this is new.  

 

This is what the help files have stated for a years now:

Help2017.png

 

Help2016.png

 

Help2015.png

 

And it goes on and on back to the beginning.  

 

I have explained to many of my clients and it is understood that if you begin a project in 2017 it stays in 2017.  If you want to migrate a project to 2017 it then remains in 2017.  I also explained this to them with every previous release of the software.  

 

And you did have issues with Land Desktop.  You couldn't just save a 2009 file back to 2004.  You had to SAVEAS and convert it.  But the data remained external in the project file in Land Desktop and you were only reading from it.  The data is in the Civil 3D file and therefore must be converted (with the export of the drawing and the Land XML).  If all this is bothering people, then we should all fight to go back to the days of creating the external project files.  I don't think so.  Smiley Wink

Jason Porter
ASTI Civil Solutions Technical Advisor
www.asti.com
Message 124 of 163
Glenn_Rimando
in reply to: MGrof


@MGrof wrote:

I have been using 2017 for weeks now.  I have yet to find one upgrade in the new version that is going to make me more effective or profitable at my job.  I can however already see thousands of dollars of lost production because of dealing with this update and non-compatibility.  Not to mention the headache of dealing with other consultants still on the old version.  We do not work within a bubble of one office or company. 

 

I used land Desktop 2009 from when it came out until switching to C3D in 2016 to not deal with update issues.  I didn't have an issue for the better part of a decade.  AutoCAD is now forcing everyone into subscription based licenses and mandatory upgrades in  a money grab.  I hope the company realizes these updates anger your customers.  I'm just trying to make noise so that they can think more about this when they try to pull this idiocy in the future. 

 

Autodesk needs to spend 5 years developing and testing a piece of software and get it bulletproof.  Then release it, and don't release a major update for another 5-10 years until they have something game-changing.  The yearly updates are infuriating. 

 

Mark G

We made the jump then

We also used Land Desktop/Autocad but held to the 2007 version till 2013 came out. We made the jump then (6 years on 2007). Now we exclusivley use civil3d for design and drafting.  I feel we'll do the same waiting game thing for us to switched 2017+ version. I feel the same as you that the new version doesn't have any functionality that warrants us to upgrade 2017+. We because very reliant on the flexibility of the 2013-16 versions and that overrides any upgrades to 2017+ at this time. 

 

 

Message 125 of 163
rkmcswain
in reply to: MGrof

MGrof wrote:

AutoCAD is now forcing everyone into subscription based licenses and mandatory upgrades in  a money grab.  I hope the company realizes these updates anger your customers.  I'm just trying to make noise so that they can think more about this when they try to pull this idiocy in the future. 

Autodesk needs to spend 5 years developing and testing a piece of software and get it bulletproof.  Then release it, and don't release a major update for another 5-10 years until they have something game-changing.  The yearly updates are infuriating. 

If you have a perpetual license, you do not have to start renting today. I suspect we will all get there soon, but not today.

Once again, they don't have to care about existing customers nearly as much as they do about acquiring NEW customers. Once you're in, you're in. They got you. Do you know anyone dumping AutoCAD for M!cr0st@t!0n (or fill in the blank with other competitors) ? Maybe one person, but what about corporations of 100, 500, 1000, 5000 or more users? It's not happening.

They are no longer going to work on a version for 5 years before releasing it. Those days are history. If anything, it's moving more towards SAAS, where you'll use whatever they allow you to use. Do you think the licensing aspect is all they are going to use the "always on" connectivity for, down the line?

Obviously, these are just my opinions. I have no insider insight. Just observations based on the past.

R.K. McSwain     | CADpanacea | on twitter
Message 126 of 163
AllenJessup
in reply to: MGrof


@MGrof wrote:

 

Autodesk needs to spend 5 years developing and testing a piece of software and get it bulletproof.  Then release it, and don't release a major update for another 5-10 years until they have something game-changing.  The yearly updates are infuriating. 


This goes back to an old argument. When they started the first version of Subscription (VIP) you would sometimes not get a version upgrade for 3 years. Those paying the yearly fee started complaining about paying yearly and not getting anything for 3 years. So they went to yearly releases. I could see many complaints about having to wait 5 years while paying yearly. Also there are people waiting for new features that may not want to wait for 5 years to see them.

 

There are arguments on both sides. But whichever way it's done there will be a group that will be unhappy about it.



Allen Jessup
Engineering Specialist / CAD Manager

Message 127 of 163
steven_anderson
in reply to: dsimeone

Hi Dave, thanks for your post about this. I'm interested in the pressure content you mention, specifically the Pressure Network Catalog database file for Steel pipe "Imperial_AWWA_Steel.SQLite".

 

My company has an Enterprise License for C3D. Is the download available for R2016 subscribers as of yet... or is it something you can simply email to me? I have an immediate project need for this.

 

Thanks,

Steve

 

Steve Anderson

steven_anderson@golder.com

941-228-7818 cell

 

 

dsimeone wrote:

Few topics i'll try to respond to...

 

  1. Civil 3D Object Format - Yes, we made the hard decision to update our objects for Release 2017. This enabled us to properly implement the improvements in the initial release AND also provide us a platform for some things that we're hoping to deliver during the year.
  2. Pressure content - We intend on delivering the pressure content as a unique doanload for R2016 subscribers. Still working out the logistics but it'll be raw content that you import into Civil 3D 2016
  3. We're still actively developing Kameleon. The long term vision is that this becomes a general content creation environment... For C3D users, i see it as the future solution for creation of both gravity and pressure content. For now, Kameleon will remain on Labs so please continue to stay involved with that project.

Thanks

Dave Simeone

Senior Product Manager - AutoCAD Civil 3D


 

Message 128 of 163

Here's an interesting twist to this backward compatibility issue.

I received two drawings in 2017 format.

One had C3D content, the other one did not.

Even with the one with just vanilla AutoCAD objects, I had to insert it as a block into a blank 2016 C3D drawing in order to dumb it down.

I couldn't just Export to CAD and get it to dumb down. It refused to work.

Mike Porter
https://provostandpritchard.com/
Message 129 of 163
AllenJessup
in reply to: CADmgrMike

Civil 3D content is not always visible. If the second drawing was started with a Civil 3D template the there may be a lot of Civil objects that aren't visible. The drawing would have had to be started in plain AutoCAD with an AutoCAD Template to avoid having anything Civil in it.



Allen Jessup
Engineering Specialist / CAD Manager

Message 130 of 163
CADmgrMike
in reply to: AllenJessup

You're probably right. I forgot about that.

Oh well. Three hours later, I have both drawings converted. sigh!

I guess I better get on the upgrade train fast.

Mike Porter
https://provostandpritchard.com/
Message 131 of 163
CADmgrMike
in reply to: ChrisRS

I've spent the last 2-3 hours reading through this and trying to wrap my head around a solution or workaround.

The one thing that comes to mind is "Does anyone get any billable production work done anymore!"  LOL

It seems I spend most my time trying to fix something or figure out a workaround.

We haven't even switched to 2017 and we're dealing with issue getting drawings from clients and outside sources.

It will be even worse when we switch (very soon now) and have to supply drawings to our downstream sources.

I guess it's all job security, right?

Mike Porter
https://provostandpritchard.com/
Message 132 of 163
CADmgrMike
in reply to: ChrisRS

I did some testing here so I can be prepared as I know this issue is going to pop up, and I'm getting a result I don't think was mentioned previously.

When I "Export C3D Drawing", and then open that drawing in 2016, it opens with no proxy objects, but I get the message below.2017-03-08_1119.png

 

If all I need are vanilla CAD objects, I know instead of opening the exported drawing, I can insert it as a block into a blank drawing, and I'm good to go.

 

IF God forbid, by some chance, I need the C3D data, before I import the XML file as discussed previously, I would need to manually find and delete all the dumbed down C3D objects that were converted to line work in the export process.

 

I know this is a lot of discussion and effort for something we shouldn't be doing anyway, but I thought I would share my testing experience for awareness purposes.

 

 

Mike Porter
https://provostandpritchard.com/
Message 133 of 163
jeffinitely
in reply to: CADmgrMike

Somewhere I read that running the "Export Civil 3D Drawing" routine TWO times will beat it into submission, and ultimately into 2016 "format" 🙂  And it seems to work...  

 

In 2017, run the 'Export Civil 3D Drawing' routine.  Open the new exported drawing in 2016.  Run it again.  Open the new new exported file. Rebuild it.  Import styles & settings or thaw/turn on all layers and copy-paste into a fresh company template.  Import LandXML.  Stand on head, kiss elbow.  Hope the inter in your office doesn't open the exported file in 2017 and save it...

 

This method works great for a single base drawing, but if you need to convert an entire sheet set from 2016 to 2017 I say you'd have better luck finding a new career 🙂

 

Alrighty folks, the word for the day is: W-O-R-K-A-R-O-U-N-D.

 

Autodesk: where's my free toaster?

 

And this nonsense of our referring to 2016 and 2017 'format' drawings makes me ill.  They're both using a 2013 format, right?  And that just doesn't make sense based on the historical 3-year format upgrade per: https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/AutoCA...

 

I like your question of "does anyone get any billable production work done anymore?"  Let's exhume board drafting!

 

Good luck everyone, and happy CADDing

Message 134 of 163
AllenJessup
in reply to: ChrisRS

Good post on the workaround.
BTW AutoCAD drawing format and Civil 3D object format are two different things.


Allen Jessup
Engineering Specialist / CAD Manager

Message 135 of 163
cmistric
in reply to: jporter

With all that B.S. you show it still doesn't explain why I can work on a 2016 file in 2015 with full controls, point groups, surfaces, etc. etc. etc. but not on a 2017 file in 2015. It makes no sense what so ever.

Message 136 of 163
rkmcswain
in reply to: cmistric

cmistric wrote:

...still doesn't explain why I can work on a 2016 file in 2015 with full controls, point groups, surfaces, etc. etc. etc. but not on a 2017 file in 2015. It makes no sense what so ever.

What doesn't make sense? This is no different that every single version of Civil 3D from 2004 up to 2013.

 

From 2013 to 2016 we just lucked out and no incompatibilities were introduced (well, actually there were some, but they were minor)

 

Now, why didn't the C3D team just wait for 2018 when the DWG format itself was changing anyway? That is a bit more questionable.

R.K. McSwain     | CADpanacea | on twitter
Message 137 of 163
akevinzz
in reply to: cmistric

This issue isn't in the core Autocad program, it's in the 3D civil entities. In 2013-2016 Autocad and 2013-2016 3D Civil the coding of the actual entities didn't change or if they did, they "cross pollinated" so the Autocad core could still read and access the Civil 3D entities. Remember when we had to download the patches to display the new contour entities back in the LDD days?? Same thing. I imagine there are patches in the works or Autodesk is just being a bully and saying "Everyone, move to the current issue or tough nuggies"


Anyway - the real question is, will we have the same problem with 2018 this spring? Or will we have a 3 or 4 year run like we have from 2013 thru 2016? Autodesk owes its customers an answer to that question.
Message 138 of 163
dsimeone
in reply to: rkmcswain

Hi folks - Here's the way I explain the object version change and why these drawings cannot be fully leveraged (C3D operations) in earlier versions of Civil 3D.

 

The Civil 3D object model is built around a core that is then leveraged throughout the system. That provides consistency and efficiency wherever possible. During the development process the team makes an effort to implement new or improved workflows without changing anything in the core code for the model (or objects within the model). For example, between R2013 and R2016 we were able to implement various workflow improvements without impacting the objects at a base level. We focused more on UI, combining operations, or adding features based on the current model version.

 

With R2017 we determined that there were important improvements that justified making core object model changes. For example, adding DREF support for corridors, reference style support, Feature Line as baseline for Corridor, and more would require that we change the object model version.

 

The question then becomes - why can't I open an R2017 drawing in R2016 and still be able to leverage C3D operations.

 

When we implemented R2013 (remember, there was no object model change between R2013-2016) we didn't build in support for the changes I listed above. Therefore R2016 can't interpret these "future state" objects. Over the years we've investigated possible solutions for enabling our products to understand "future state" objects but determined that the only viable approach was to promote these objects to the future state - which then requires the infrastructure needed to support these future state. 

 

Note that we're trying to sync this object versioning change to be aligned with AutoCAD. This will make it clearer for everyone that there is a version change. We can't promise that this will be the case but this alignment is absolutely a key factor as we define our product roadmaps. We're also working to ensure that we clearly communicate in our help, product readme, and support materials when there is an object format change so that users are not caught unaware. Also, to reiterate, we understand the disruption that this causes and will continue to do what we can maintain a consistent object format. However there will be times where the critical need to deliver functional or platform changes outweigh the benefit of maintaining object version consistency.

 

Thanks

Dave Simeone

 

 




Dave.Simeone

Product Line Manager, Autodesk Infrastructure Products
Message 139 of 163
cmistric
in reply to: rkmcswain

I have 2014-2017 installed on my PC, I can open a 2016 file using 2014 Civil
and I have all the point groups, surfaces, parcels etc. but I cannot open a
2017 file in 2015 Civil and read the point groups, surfaces, parcels, etc.
This is how it is different.
Message 140 of 163
Cadguru42
in reply to: cmistric


@cmistric wrote:
I have 2014-2017 installed on my PC, I can open a 2016 file using 2014 Civil
and I have all the point groups, surfaces, parcels etc. but I cannot open a
2017 file in 2015 Civil and read the point groups, surfaces, parcels, etc.
This is how it is different.

As has been explained multiple times by different people, the C3D object format is not the same as the DWG format. Autodesk didn't change the DWG format from 2013-2016 and kept the same C3D format for 2013-2016. With 2017, Autodesk changed the C3D format, but kept the same DWG format as before. This is why a drawing made in Civil 3D 2017 is not backwards compatible. It's also going to make C3D 2018 drawings not backwards compatible because the 2018 DWG was changed.

 

The only time a C3D drawing can be backwards compatible is if the DWG format and the C3D object format are the same. 

C3D 2022-2024
Windows 10 Pro
32GB RAM

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Rail Community


Autodesk Design & Make Report