AeccContent_Dir, C3DStockSubassemblyScripts.codes and custom coding

When developing custom subassemblies for Civil 3D using MS.NET there might be a need for custom coding.
There are three ways to do it.

1. Rely on module "CodesSpecific.vb" provided from autodesk.
Developer may add custom codes. But none of it will be avalaible unless the file named "C3DStockSubassemblyScripts.codes" is informed with latest codes.
This file is in the directory which variable AeccContent_Dir points to.
This variable is readonly and its initial value is set when installing Civil 3D. If user does not change its location proposed by autodesk then it points to...
C:\ProgramData\Autodesk\C3D 2017\enu\C3DStockSubassemblyScripts.codes

2. A variation of the above approach is to alter the path and/or the name of the file it points to.
Path is get from the variable "AeccContent_Dir" and file "C3DStockSubassemblyScripts.codes" is set into the constCodesFile. Even alter the whole apporoach of getting the codes.

3. Totally ignore the autodesk coding approach and set codes directly which i think is the best approach.




 

Trimble TGO GPS site calibrations tips (2)

Beware of the rotation units GON vs Degrees.

On site calibrations can be saved to TGO Coordinate System Manager as Sites and get used to other jobs.

Adjustments is only for Trimble. A site calibration can be reproduced as Datum with TGO GPS calibration as 7 parameter. Original on site job required.

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.