Civil 3D 2012 SP3 (Update 3)

[JeffPaulsen]

Has anyone installed SP3 yet? Are there any issues with it?

We are about to roll out 10 new computers and I am debating whether or not to put SP3 on them.

[bendavisasce]

I have been using it since roll out and the fixes seemed to help make an improvement for me. I would recommend it.

[Jeff_M]

Same for me. I have had no issues with SP3, highly recommended.

[nwtayeb]

For me I couldn’t import from Google earth when I updated to SP3

[Ed.McGriskin]

No issues here with SP3. Seems to help performance a bit. 

[Jeff_M]

Update! The issue introduced with SP2/2.1 where you are unable to create Data Shortcuts if you have Assemblies labeled with MText using Fields has been brought back with SP3. The fix is to install the HotFix released in Aug 2012.

[tmullins]

Update to your Update Jeff....

The issue I found earlier with data shortcuts and Update 3, I did not have any assemblies labeled with Mtext. I simply could not create a shortcut at all. It continued to tell me to save the drawing.

So extracted the AcFdEval.arx from the hotfix (file version 18.2.205.7 dated 8/14/12) and then I could create shortcuts again.

(Update 2.1 actually fixed the issue, then it appears Update 3 broke it again - verified on another machine just running Update 2.1 on the same file I could still create shortcuts.)

http://forums.autodesk.com/t5/AutoCAD-Civil-3D/Creating-Data-Shortcuts-Problem/td-p/3277507/page/5

[JeffPaulsen]

Can anyone else confirm that the Google Earth import is broken with SP3?

[JeffPaulsen]

I just installed SP3. So far so good.

Insert Google Earth Image and Surface worked just fine and I was able to create a data shortcut in a drawing that contained fields for assembly names.

[Jeff_M]

Update to my update. Looks like I had a bad ARX file on my PC which had nothing to do with SP3. Installing SP3 on another computer shows that it works just fine after running a number of tests to try to duplicate the previously reported issues. 

I again highly recommend installing it.

[colby_phelps]

Hi Jeff --

EDIT: Oh shoot, Jeff - I just saw in another thread that you warned another user regarding SP2.1 and disappearing profile information. So I have nothing new for you below 😞

In my office we have experienced an issue when we went from Service Pack 1 to Service Pack 2.1. I have read that SP 3 contains all fixes brought forward in 2.1, so I consider SP 3 an offender in the same vein as 2.1. SP2.1's issue is a known problem and was not remedied in SP 3.

Anyway! What I'm getting at is this: If you have a computer that has built profile views that contain pipe network objects inside them, with service packs that pre-date SP2.1, you are vulnerable to SP2.1 & SP3's issue:

*profile view grids go haywire and display beyond their borders, for thousands of feet

*pipe network objects no longer display in these profile views

-----> find relevant thread here: http://forums.autodesk.com/t5/AutoCAD-Civil-3D/Civil-3D-Service-Pack-2-1-HEADS-UP/td-p/3603270

Beware, Sir.  Hopefully you will not need to touch projects and re-publish any pipe network content contained, as that is now impossible unless you go back to SP1. I have verified this issue on my own machine (I installed SP2.1 & SP3 and experienced the issue). We have uninstalled C3D 2012 and re-installed with 2012/SP1 on 3 machines to handle the continuing work on the project. That was the only solution.

[Jeff_M]

Colby, I don't know if you saw any of my other posts regarding this issues (I've made plenty  ), but I did find a workable solution for MOST of my current projects. All of the strange issues created by SP2.1 have been remedied by insuring that I do not have BOTH a DataReference to a Pipe Network AND an Xref to that Dref's Source file in the same drawing. If I have one or the other, all is good, but when they both are brought into the same drawing then all bets are off. I am now happily using C3D2012, SP3, with mostly great results.

[colby_phelps]

Killer tip, Jeff! Thank you -- I will try this workaround 🙂 

[sboon]

My problems reported previously in this thread after installing SP 2.1 have reappeared after installing this one.  I suspect that I will be uninstalling it soon.

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

[colby_phelps]

Thank you -- I will proceed with caution on a test machine.

[Jeff_M]

Steve, I almost replied this morning that I had never seen this issue with the corridor featurelines. I have a corridor which is ~3.5 miles long, lots of cuts & fills, adjacent swales, etc., which has always looked great in plan view (we won't talk about the 3d views or during the Drive command). Until this afternoon, when I had to edit one curve to get the EOP to avoid an existing drainage inlet. The change in curve shifted the midpoint of that arc ~5'. Once I rebuilt the corridor, I saw this featureline issue in one place and that was in the area of this modified curve. Due to other fixes that 2.1 made, I do not want to go back to an older SP so I will live with this. I may change the subassembly in that area to try to eliminate the problem linework.

[sboon]

Other users in our office have reported a possible solution where they add one or two stations near to the point where the featureline jumps, so that the corridor can find another section to connect to instead of jumping way down the alignment.

Steve
Please use the Accept as Solution or Kudo buttons when appropriate

[Jeff_M]

What I found in my corridor was that, where it jumped, the corridor switched from a cut condition to a fill condition then back to cut, where just one section was in fill. It jumped from there to the next section that was fully in fill for the remainder of that corridor region. By adjusting the profile to eliminate that one fill section fixed my corridor.