Friday, June 30, 2006

What Changed in Civil 3D 2007 Service Pack 1A

Well here it is! What was added to Service Pack 1A, beside the Parcel label issue, which looks to be some nice fixes:

General

• An issue with running Audit has been resolved. Audit no longer removes the points and all of the styles from the drawing when it encounters an issue with an individual style

Alignments

• An issue with invalid parcel creation when deleting alignment segments has been resolved.

Labels
• An issue with parcel labels not scaling correctly in paper space has been resolved. Parcel labels now display as expected in paper space.
• An issue with using the Undo command to remove parcel labels that had just been added has been resolved. The problem occurred if you later added more Parcel labels to that site. This issue caused the program to terminate unexpectedly when you tried to save the drawing, or when you tried to reopen the drawing if it saved successfully.

Pipes
• An issue with pipe network references creating dependent object data (such as alignments and profiles) has been resolved. Now when you create a pipe network reference, dependent objects do not get created.

Survey
• The Create Figure From Object/Update Figure from Drawing command now assigns the proper elevation values.


I took the lists from both SP 1 and SP 1A and compared them. What is interesting is, on the SP1 list there was a line item under Survey ("An issue with saving changes made to Equipment items in the Survey Toolspace Item View has been resolved). The interesting part is that it didn't show up on the SP 1A list, now I would imagine that it didn't get left out, since it was already released with the original SP1 but there is not mention of it, anywhere. Any ideas. . . anyone. . . anyone. . .Bueller!

1 comments:

Anthony Governanti said...

So you are right in your comparison that there is a fix missing from SP1A that was in SP1. Basically there was a problem found with a file version that runs part of the survey toolspace, and in order to make sure we get the fix implemented correctly, we had to pull it from SP1A.

Not great news, but at least we found it and are working on the fix for a future update.

Great catch!

Anthony G