I didn't want to hijack the other thread with my own related question so I started a new thread.
We're supposed to be switching from C3D 2012 to C3D 2014 "soon" (we originally expected to switch this past fall but that didn't happen). We've never had 2013 installed here at all. So based on the experience of everyone here, should we be concerned about our own files or does the "infection" seem to happen only after opening an "infected" 2013 file?
If that's the case, should we refuse to accept 2013 files (we OCASSIONALLY receive dwg files from consultants but MOST of our work is done in house).
Don Ireland
Engineering Design Technician
Solved! Go to Solution.
Solved by jmayo-EE. Go to Solution.
Solved by Jay_B. Go to Solution.
Also -- I just checked and we have C3D 2014 SP1. As long as we don't open any infected files, are we ok? Or should I tell the boss that we need to upgrade to SP2 before the roll out?
Don Ireland
Engineering Design Technician
My opinion & it's just that , would be to include SP2 right out of the gate due to the significant fixes it includes.
Some of the big ones included in SP2 readme for us are:
One major caveat here is SP2 was released recently on 7/9/14 so it hasn't been tested a lot yet but we've began installing it on all our 2014 installs here and so far it's been fine. The included fixes included far outweigh the problems of SP1 IMHO.
I can't say for sure if the Strange Site Name aka "unexpected characters and text" is completely fixed in 2014 SP2 but I think it might have been.
We only recently started noticing it in our files and the day before installing SP2 I had 4 files open at once and saw the **error** in the anchor of Contour Label Styles. (only place I noticed it checked for it) but it was present. Following the SP2 install I opened same files & went to Contour Label Style Anchor Point and it read "Feature" as expected.
I'll be watching closely for the "unexpected characters and text" in coming weeks but it seems fixed in 2014 SP 2.
I agree Jay. Even with our limited knowledge of the issue we do know that users have reported back that 14 SP2 fixes the issue. I wouldn't worry if this is true and you were moving forward. I think the big issue is for those who need to remian on 13. I would assume 15 SP1 will also include the fix.
John Mayo
Thanks guys!
Don Ireland
Engineering Design Technician