AutoCAD Civil installation causes problem with existing Map installation

If you install AutoCAD Map 2017 and afterwards Civil 2017 exporting a Map drawing (FDO layers) as CAD drawing (command: _MAPTOACAD) might fail.

In particular if a template is used when exporting. Map will perform the export but will not finish the process - the dialog box won't disappear and the process cannot be cancelled. Map still uses CPU resources and needs to be closed forcefully. The drawing will be created and can be opened - but I'm not sure if all elements have been exported or not.
I had to reinstall Map to solve the issue.

Map 2017, SP1

DWG-Export - Missing/wrong z-value

With Map 2013 height information (attribute data in Industry Model) of point features will not be exported as z-value for AutoCAD points/blocks. 
In newer versions of Map the attribute value will be exported but apparently there is a bug so that the AutoCAD points/blocks might get a wrong z-value.

Here is a little tool which assigns the z-value to blocks after exporting the drawing. DWG export needs to include XDATA:
- export the drawing (command: maptoacad) and include XDATA
- configure the XML file according to your needs
- open the exported drawing and run the tool.

Configuration file explanation:
<Block>
        <Infotext>AV - 17.7.2014</Infotext>                    
        <Layername>AV_Höhenfixpunkte</Layername>
        <SpaltennameHoehe>HOEHE</SpaltennameHoehe>                  
        <SpaltennameNummer>PUNKTNUMMER</SpaltennameNummer>
</Block>

<Infotext> - just some information, not processed
<Layername> - AutoCAD layername where to find the blocks
<SpaltennameHoehe> - name of the attribute containing the z-value (your feature class or view needs to have the z-value as attribute in order to get it exported as XDATA)
<SpaltennameNummer> - name of the attribute containg a point number (appears in report)

attribute names in FDO feature source - data needs to be exported as XDATA

This is a stripped down version of a tool containing further dwg export post processing features. Sample drawing is included. Tested with Map 2013, should run with newer versions as well. In german language only.

a) download
b) extract ZIP and unblock DLL (otherwise it won't load in Map)
c) open sample drawing
d) command: netload to load DLL file
e) command: WIN_DWGEXPORTPOSTPROC to run tool
f) load attached sample XML configuration file

Download

DWG export - lineweight missing

When exporting to CAD drawing (maptoacad, editable, with template) some polylines got the default lineweight of "0" although the Map display model assigns certain lineweights to them. In Map these lines displayed correctly. For the polylines affected the lineweight was set using an expression:

<Override>
 <SymbolName>LTYP20</SymbolName>
 <ParameterIdentifier>LINEWEIGHT</ParameterIdentifier>
 <ParameterValue>0.35 * 500</ParameterValue>
</Override>

To get the lineweight exported correctly one has to put the expression in brackets:

<Override>
 <SymbolName>LTYP20</SymbolName>
 <ParameterIdentifier>LINEWEIGHT</ParameterIdentifier>
 <ParameterValue>(0.35 * 500)</ParameterValue>
</Override>

Map 2103, Sp2

DWG Export - Linienstärke fehlt

In der exportierten DWG (_maptoacad, Bearbeitbar, mit Vorlage) hatten einige Linien die Linienstärke "0", obwohl im Darstellungsmodell ein anderer Wert eingestellt ist. In Map wird die Linienstärke auch korrekt dargestellt. Bei den betroffenen Linien war im Map-Layer die Linienstärke über einen Ausdruck festgelegt:

<Override>
 <SymbolName>LTYP20</SymbolName>
 <ParameterIdentifier>LINEWEIGHT</ParameterIdentifier>
 <ParameterValue>0.35 * 500</ParameterValue>
</Override>

Für den DWG Export lag die Lösung darin, den Ausdruck in Klammern zu setzen:

<Override>
 <SymbolName>LTYP20</SymbolName>
 <ParameterIdentifier>LINEWEIGHT</ParameterIdentifier>
 <ParameterValue>(0.35 * 500)</ParameterValue>
</Override>

Map 2103, Sp2

DWG-Export - hatch pattern missing

We used some hatch patterns in our display model which we loaded via StyleEditor from external files (xml, pat). We also made sure that corresponding AutoCAD hatches with the same name were available when conducting DWG export - but theses were always missing in the drawing file.

It turned out that the following tag in the layer is responsible:

<ExtendedData1>
 <FileName>S:\GIS\...\Vorlagen\HTypWAV_Wald2.xml</FileName>
</ExtendedData1>

It automatically gets created when you load a hatch from an external file. After removing the tag DWG export worked as expected. Same happens by the way with lines styles.

Map 2103, SP2

DWG Export - eigene Schraffuren fehlen

Im Darstellungsmodell wurden einige Schraffuren aus externen Dateien verwendet. Für den DWGExport standen die entsprechenden Schraffuren als AutoCAD Schraffuren zur Verfügung - trotzdem wurde keine dieser Schraffur in der DWG erzeugt.

Ursache ist der folgende Verweis in der Layerdatei - dieser entsteht, wenn das Schraffurmuster aus einer externen Datei geladen wird:

<ExtendedData1>
 <FileName>S:\GIS\...\Vorlagen\HTypWAV_Wald2.xml</FileName>
</ExtendedData1>

Entfernt man den Eintrag funktioniert der Schraffurexport auch mit eigenen Schraffurmustern.
Ähnliches gilt auch für Linientypen.

Map 2013, SP2