I have a mixed environment of 2013 & 2014 C3D.
I updated our template to 2014, and everything is running along smoothly until a user tried to change the coordinate system in a drawing while open in 2013. BIG error message (see attached file) and all the drawing setting tabs are blank.
I went back and created a new 2013 template, then imported our styles and settings separately.
Importing the styles didn't cause the error message, but it did after importing the settings.
Anyone else run across this issue?
I didn't get this error... But what I did to create my 2014 template was likely a different approach. I used the out-of-the-box 2014 Civil 3D dwt provided by Autodesk, then added my Civil 3D styles from my 2013 template. From there I changed my settings.It might be a little extra work to do that, but at least you know your template is mainly based on the 2014 settings and not pulling something from a past version. 2014 in general seems to be quite buggy so I'm looking forward to 2015.
That is exactly how I created our 2014 template, so I'm not sure what caused this error.
I've started recreating another template and the error isn't happening....yet.
Is there ever going to be a version that isn't buggy?
I started the migration from 2013 to 2014 because of pressure pipe networks and then found out I have a completely different issue I'm trying to debug with Autodesk now. Oh the saga of my love/hate relationship with C3D.
I'm curious as a side note, what methods do you use for getting all your layers and settings into the new template?
That works as long as the layers you are inserting are not already in the OOTB template.
We use NCS layering so a lot of the layers we use are already in the OOTB template, but the colors, linetypes, & descriptions are incorrect.
There are 205 layers in the OOTB template so checking those for color, linetype, and description is quite a pain.
Also how do you deal with the various ambient settings you can import, such as the abbreviations?
I was curious if you had figured out how to automate those two issues.
As for the Abreviations, that is a good point, I'd have to dig into this more but maybe you could likely build a script file to alter these abreviations to an OOTB original file.