Known issues

Summaryatesio calculation does not provide a link between street centerlines and possible trenches
DescriptionWhen calculating networks with NET Design and atesio, information from the street centerlines is not transferred to the possible trenches. The error occurs with atesio version 2021. Here, after the preprocessing and the creation of the possible trenches, no relations to the original street centerlines are returned.
WorkaroundCurrently there is no way to work around the problem, but atesio is already working on a solution, which is expected to be available with atesio version 2022.
Affected versions12.3.4
StatusOPEN
 
SummaryProject validation error in NET Design
DescriptionDuring project validation in NET Design, after calculation with Comsof Fiber Designer, sometimes an error occurs when project validation is run again after the selected optimizer has been changed.
WorkaroundIn project validation, do not select all validations, but only those that are really relevant.
Affected versions
StatusOPEN
 
SummaryThe list of cluster types in the NET options is loaded only once when the project is opened.
DescriptionIf a new cluster type is created after the NET options are first displayed, then the list will not be updated until the next time the project is opened.
WorkaroundClose the project and open it again.
Affected versions12.3
StatusOPEN
 
SummaryMap 3D 2024 - Icons does not load correctly
DescriptionIn Map 3D 2024 some of the icons does not load correctly. They only show as the Autodesk standard icon, which looks like a big black dot.
WorkaroundPlease copy the icons from "C:\Program Files\Autodesk\AutoCAD 2024\Map\Pics" (if standard installation path is used) to "C:\Users\USERNAME\AppData\Local\Autodesk\Autodesk AutoCAD Map 3D 2024\R24.3\enu\Pics". Please replace "USERNAME" with the folder for the Windows User.
Affected versions
StatusOPEN - solution expected for version PATCH
 
SummaryTNIM Import - Validations fail to identify issues for objects not directly related to the import
DescriptionThe validations of the TNIM import are limited due to the most recent performance improvements. The changes had the side effect, that features in the database, that are only indirectly affected by the TNIM import, are not checked anymore. This only affects imports in case the TNIM data model is enabled and the update function is used. In that case, it is possible, that for example a cable models number of fibers is changed due to the update. If that happens, only the cables present in the current TNIM import are validated, but not those that are already stored in the database and referencing the changed model. This also affects other object types.
WorkaroundThere are currently no workarounds, other than making sure that especially models are consistent between multiple TNIM imports.
Affected versions12.5.1
StatusOPEN - solution expected for version PATCH
 
SummaryFiber optic connection editor creates connectors with multiple outgoing connections
DescriptionIf an action "Connector to technic port" is created first for an unconnected connector and then another action "Connector to fibre", then a connector with 2 outgoing but no incoming connection is created. As a result, overviews and reports are created incorrectly.
WorkaroundThe problem can be solved by removing all patches between the faulty connectors and thier ports. Afterwards, these patches must be recreated in the fiber optic connection editor using the "connector to port" action. To identify the relevant connectors, the following SQL filter can be used in the FO Connectors form: Fid in (select c.fid from tc_fo_connector c join tc_point p ON p.fid_attr = c.fid join tc_conn c1 ON c1.fid_to = p.fid join tc_conn c2 ON c2.fid_from = p.fid where c1.flow != c2.flow)
Affected versions12.3.4, 12.3.5
StatusDONE - Resolved in version 13.3.1
 
SummaryFlat Feature Search in Autodesk Infrastructure Administrator does not work with all data types under PostgreSQL.
DescriptionDuring the Flat Feature Search in Autodesk Infrastructure Administrator, an error occurs under PostgreSQL when searching for a number, for example.
WorkaroundUse the Sequential Search instead of the Flat Search.
Affected versions1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 2.0.0, 2.0.1, 2.1.0, 2.2.0, 3.0.0, 3.0.1, 3.1.0, 3.1.1, 4.0.0
StatusDONE - Resolved in version 4.1.0