using both c3d 2011 and 2012

[rfg018]

I want to test 2012.

Can the other whom are using c3d 2011 use my drawings, such as surface, aligement, parcels, data links, etc.?

[AllenJessup]

I haven't tested that but I would think not. You'd have to share any Civil 3D objects through XML.

Allen

[Jason.Hickey]

No, they absolutely cannot. It has been this way for every single release of Civil 3D. Once a drawing is opened in 2012, it either remains in 2012 or is exported to 2011 as an AutoCAD drawing and XML data. You cannot work alongside 2011 users with their data unless you want to upgrade them immediately as well.

[rfg018]

too bad, 

I like it when we had different user on different version. It gave me a chance to test, and if something didn't work or I couldn't figure it out, I could jump back and do the task.  I also did this with old rountines. 

and  Some people just do not want to change or use the new and improved comments.

thanks, I will keep this in mind.

[Anonymous]

It's sorta like ground combat, with ADSK the enemy.  Once we get to an entrenched position, and start to feel a bit safe, ADSK starts shelling us with a new version.  So, it's either stay in one place & get plastered, cause we can't share with the newbies, or run to a new postion, dig in & start to feel safe again, until the shelling starts over.  Unfortunatly, sometimes the new position is a fall back & we loose ground while we try to adapt to the new program.

I knew this was going to happen when ADSK bought SDSK.  They're forcing the upgrade cycle so they can make money, not us poor end useers.  Too bad we don't have any artillery of our own to shoot back with.

Reid

[rfg018]

In the early days, we look forward for the new relases. Since each release had many new and inproved commands.  Plus we could use different version.  We ran into a problem when they change the DataBase.

The problem Autodesk needs to look at is that we share our DWG files with other user and consultants.  Autodesk wants us to share drawings (not data base file), However if every year the DWG is not compatible with the earler version, this make it hard to share.  And if you think that I should use my time to convert/explode and create XML files every time someone need the data, think again.

here is the example how thinks should works.  Autocad 2005 and 2006, you can share DWG files.  However 2006 had Dyn block, and 2005 do not.  But the Dwg file works with both.

This is how I will have to slove this problem.  I will use C3D 2011, and 2012 ect base on the project needs.

This should work until by accident (not reading the warning), I open 2011 dwg in 2012

that for your input

[Anonymous]

For as long as I can remember plain autocad has always been able to save back and still can. Since the very first release of Civil 3D I think 2005 civil has not been able to be saved back. If you think about it this is because civil3D is always advancing with new objects and commands which it must. How can a developer design a piece of software today and have the foresight to know what another developer may develop in the future.

Subscription is a way to keep going forward and from day one we have not had any problems Installing and using the new release as soon as available. This approach also work out cheaper in the long run than missing releases and upgrading later.

[mikekillion]

Still, it seems amazing that with all the talk and encouragement for BIM, and collaborative sharing with the design team, that Autodesk would create a divide between each release. If the solution is to eTransmit with AEC Objects exploded and export the XML files for each Civil 3D object, they should be able to incorporate this into the software as an option ("Save to previous Civil 3D release format"). Especially on the same dwg platform, such as releases 2010-2012. I understand the evolving landscape of the object model and enjoy the exponential increase in how the software performs, Civil 3D rocks. But this is a painful loose end considering the marketing campaign to collaborate between disciplines. Why not run a lot of training on how to use each products XML files?

We don't look like pioneers adopting the newest release of Civil 3D, We look like poor team players delivering our design in pieces we hope the other team members can put back together correctly. And we receive a lot of phone calls regarding the impact this has on the other consultants workflow, when they grind to a halt as everyone tries to determine why they can't use our deliverables. This causes greater confusion, not greater collaboration.

My apologies for the vent. I was hoping to find I overlooked a way to share my Civil 3D 2012 product with a team that requires my work to be in Civil 3D, and I can't provide them anything but a 2010 drawing format and XML files. But please keep blowing the BIM trumpet. At least the tune sounds good.

Mike Killion

[Sinc]

I agree completely.  If Autodesk insists on forcing us into this yearly incompatibility, at least give us a Super-eTransmit that can create all files needed to get the data into an earlier release.  By that, I mean one that will not only do all of the normal eTransmit stuff (with CTB/STB files, fonts, etc.), but also take care of issues like the background mask headaches at the same time as it creates the old-format DWG files, also correctly including all XREFs (without blowing up for random unknown reasons), and also including the LandXML output from the project, along with options for creating a CSV dump of Cogo Points, and other sundry things that we generally need to send back to clients.

Something like that would be FAR more useful to us than many of the new features I've been seeing over recent releases.

[rfg018]

I think Autodesk should put out releases evey two or three years to keep team on the same database and be campatible.  Autodesk can provide the subscription team updates/plugin which would enhance the product during releases dates. 

The way it's now, I may have to wait before I use 2012 products.