Trimble TGO GPS site calibrations tips (1)

In order to manipulate Trimble GPS calibrations using TGO it is absolutely critical to keep original controller's JOB containing the on site GPS measurements for calibrations.
Or else only a point to point (*.csv, *.txt) transformation is possible.

TGO does not import a job other from controller. So copying a job to another media is useless!
eg It is not possible to import it from a desktop backup! But this backup should exist so that it can be copied back to controller and import it from there!

Civil 3D custom subassemblies created with previous versions of SAC may not work as expected when imported to later C3D versions

Custom subassemblies created with previous versions of SAC may not work as expected when imported to new c3d versions (although if already in a drawing of a previous c3d version will work fine when opened with later version!).
I met such a case. All previous version subassemblies worked fine except one! Worked fine when opening a previous version dwg file already containing it. But did not work if imported from scratch to a later C3D version!

Civil 3D corridor export feature lines tip : Baseline Profile layer locked

I have used Corridor feature lines export to Polylines, Alignments with profiles and Profiles lots of times.
But this time nothing worked right. All elevations were not absolute but relative to baseline profile not matter what trick i tried.
Finally i found out that if profile baseline layer is locked then all elevations exported, no matter what method used, are relative to this profile, not absolute!

Not as single mention in C3D help. Not a single relative result in Google Search. Am i the first one to fall into this situation ? I do not think so.
Should autodesk warn users about this behaviour ?

Thanks God, i found that just one step before losing my mind and only after several hours stall!
So the damage is done. Other partners, that do not know anything about C3D, think that i am too slow and that simple projects are difficult for me. Yeah...if you say so...

&*&^%%$%#@$!*@&^

Leica vs Trimble software support

Trimble has published its Civil 3D 2017 export/import set of applications since the first days autodesk announced it.
September ends and Leica has not published its X-Change sets of applications although there are already Infrastructure and Building Links for 2017 editions months ago.

Yet another Civil 3D major bug (and a minor one) : Assembly properties​...get value from...end elevation (not getting it)

I really can not understand how is it possible for such a bug to exist after so many years and so many users.

http://forums.autodesk.com/t5/autocad-civil-3d-general/assembly-properties-get-value-from-end-elevation-not-getting-it/td-p/6426929

Assembly properties​...get value from...end elevation (not getting it)

07-08-2016 11:51 PM 

I create an assembly with a subassembly that is capable of getting value from a "Target elevation" (eg LinkSlopeToSurface) when in "Assembly properties>Construction>Input values". In Parameter reference i check the "Use" next to "Target elevation". I select a "xxx.End elevation".
Elevation applied is wrong. It is the default constant value of the eg LinkSlopeToSurface.
If i change the target to "xxx.Begin elevation" the correct elevation is apllied.
This happens to what ever subassembly can get a "Target elevation".
My conclusion. "xxx.End elevation" property is not exposed.

This also takes place when using my custom SAC subassemblies and i almost got crazy trying to find the bug in my coding.

Three notices.

The good one.
Having opened both assembly properties and cross sections window when changing the get value target there is an immediate response to the graphics at the cross sections window without rebuilding corridor although corridor at toolspace is marked as needing rebuild !!!

Althought graphics response to this property value change is immediate, when changing a subassembly name, the "Get value from" is not immediately informed and the old name is used. User must close and reopen "Assembly properties".

The bad one.
The rule is that property values among different subassembly groups are not exposed.
Group eg B cannot see group A values. BUT if names of subassemblies are identical the property values exposed are the ones of the first whatever group!!! The rule is not applied in this case!!! Leak it is. A serious mistake can take place.
I think this is a logical mistake that the Development Team should take care off.

MS Visual Studio NET : Civil 3D and custom references copied local

There is no need for Civil 3D DLL references to be copied local and they should not be.
But other custom DLLs, that are referenced by custom Civil 3D DLL, should be.
Or else when in Civil 3D custom Civil 3D DLL is loaded but no command is executed.
A Line Editor message informs that command is unkonwn !!!

About 64 bit debugging and Edit & continue...

https://cadblognews.com/2016/05/11/debugging-autocad-2017-using-visual-studio-2015/

http://adndevblog.typepad.com/autocad/2016/05/debugging-autocad-2017-using-visual-studio-2015.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+AutocadDevblog+%28AutoCAD+DevBlog%29

http://through-the-interface.typepad.com/through_the_interface/2013/11/debugging-autocad-using-visual-studio-2013.html

 

Civil 3D net Corridor Baseline Regions getting Applied Assemblies tip

Each corridor baseline region has its own applied assemblies. One for each corridor section.
I thought that all of them point to the same assembly. So i always used to get only the zero index one.
Each baseline first region zero index applied assembly always exposed the correct assembly.
But i noticed some of the rest were wrong.
I found the reason.
If a region has the same starting station with the previous one ending station (up to 2mm difference) then the first applied assembly, the zero indexed, points to the one of the previous region!!!
So i had to check the items.count of applied assemblies. If more than one then i get the index 1.

Notice : C3D 2012 API did not expose the Region Name. C3D 2016 API does expose it. It was time for the autodesk to do it. So simple.