When drawing in 3d, Civil 3D will not allow to construct arcs with differing heights at the ends. Currently, it will only allows the construction of orthometric arcs, on horizontl XY plane. Please, implement 3D arcs as standalone, or part of 3D Polyline. Show More

So I have been hoping Autodesk would have added this feature (no pun intended) but it has been years of working with Civil 3D and they still do not have a way to data reference feature lines. Yes, I know, technically you can data reference the corridor itself and then extract the feature lines from the corridor in the data reference file, but what about feature lines that you generate yourself ones that are not dynamically linked?   I have always been looking for better ways to create grading designs that are more dynamically linked. It makes edits and even entire regrades much easier, more accurate, and less of a chance for issues to be missed in the revisions. A few years ago, I stumbled upon a video by Jeff Bartels (Seriously love this guys videos and ideas) and the way he grade a site was incredibly ingenious. He graded a small parking lot by creating a very basic surface and called it somethink like PG DESIGN. The grading of this surface only focused on the pavement elevation. He blew threw curbs and sidewalks like they were'nt even there. At first I had a hard time understanding where he was going with this, but then he created another surface by using a corridor, except he used face of curb lines as feature lines and then the baselines of the corridor. The assembly he used was only a curb and he set all of the elevations of the curb feature lines relative to his design surface. Basically, his design surface controlled the corridor entirley. This made so much sense because typically, your top of curb, back of sidewalk, etc. elevations are dependent on your pavement elevations so it made complete sense to use a corridor and the way everything moves together just based off of your pavement elevations and how tied together it was just completely blew my mind. It was such a simple idea but it made all the difference.   I took this idea and ran with it and I have been able to set up grading designs that are so dynamically linked and tied together that I can adjust nearly every elevation of a parking lot and never worry about what the sidewalk, curbs, or even the ADA curb ramps are doing. I even went ahead and create a post curb subassembly that had a curb height target to it so I could create curb ramps and it worked beautifully. The one issue I found was it was better to do this in two separate drawings in order to keep things clear. That wasn't a big deal. I would just data reference my design surface into my corridor drawing and I could still set my curb feature lines relative to that surface. The one headache I found though was that there are plenty of times where you might need to set elevations away from curb faces and interior to the parking lot. Since the corridor was only building the curbs, sidewalks, etc., I would have to copy over quite a few feature lines from my design file into my corridor file and also set those relative to my design surface. This is where data referencing Feature Lines would literally create the most perfect grading workflow (In my humble opinion).   I am not a programmer at all so I am not sure if it would even be possible, but if it is, please add this feature. Show More

The QSELECT command has object Styles as one of the properties that can be used to filter selection results.  However this feature does not seem to work.  Any value entered into a search that queries Styles always returns 0 results. Please can this be fixed!  There are many incidents where I need to select all labels / objects of a certain style but unable to do with using QSELECT, instead I have to select all of these objects manually and this can be very frustrating and time consuming.       Show More

The title is self explanatory  Show More

🔹 Description du problème Dans de nombreux flux de travail professionnels en matière de levés topographiques, les relevés sont fournis sous forme de fichiers DWG AutoCAD où les objets levés sont représentés par des blocs placés à des coordonnées XYZ précises. Chaque bloc : Inséré à l'emplacement exact du point de levé (X, Y, Z) Représente un objet relevé (arbre, poteau, bordure de trottoir, regard d'égout, etc.) Classé par nom de bloc et par couche selon une légende d'arpentage Ne contient pas nécessairement d'attributs (flux de travail hérités et éprouvés sur le terrain) Actuellement, Civil 3D ne propose pas de méthode native pour interpréter les blocs existants comme des points topographiques. Les utilisateurs doivent recourir à des conversions manuelles, à des scripts ou à la réimportation des données, ce qui entraîne les problèmes suivants : Perte de la structure d'origine Duplication des données Risque accru d'erreurs Flux de travail chronophages 🔹 Fonctionnalité demandée Ajouter une fonctionnalité native de Civil 3D permettant aux utilisateurs de travailler directement avec les blocs topographiques existants en tant que données de points de levé. Cette fonctionnalité devrait permettre à Civil 3D de : Lire les coordonnées XYZ à partir des points d'insertion du bloc Utilisez le nom du bloc et/ou la couche du bloc comme description et classification du point Créez des groupes de points dynamiques basés sur le nom du bloc ou la couche. Création optionnelle de points COGO liés à des blocs (non destructif) Conserver la structure et la légende du fichier DWG d'origine 🔹 Flux de travail suggéré (point de vue de l'utilisateur) Sélectionnez les blocs ou les couches contenant les blocs d'arpentage Choisir les règles d'interprétation : Nom du bloc → Description du point Calque → Groupe de points ou style Civil 3D reconnaît instantanément les blocs comme des données topographiques Des points deviennent disponibles pour : Surfaces Profils Cibles du corridor Quantités ne nécessitant ni conversion ni duplication 🔹 Avantages Gain de productivité important pour les géomètres Interopérabilité transparente avec les livrables d'enquêtes basés sur AutoCAD Courbe d'apprentissage réduite pour les nouveaux utilisateurs de Civil 3D Compatibilité améliorée avec les logiciels d'enquête existants et tiers Des flux de travail BIM et de gouvernance des données plus propres 🔹 Utilisateurs cibles Géomètres ingénieurs civils concepteurs d'infrastructures (routes, voies ferrées, tramways, métros) Travaux publics et projets urbains 🔹 Contexte industriel Ce flux de travail est largement utilisé dans : relevés topographiques urbains Projets ferroviaires et de tramway Conception des infrastructures publiques bureaux d'arpentage réalisant des levés topographiques basés sur le format DWG 🔹 Pièces jointes Exemple de fichier DWG contenant : Blocs topographiques sans attributs Plusieurs types de blocs Légende basée sur les calques Coordonnées XYZ précises Show More

It would be great to have an extracted/dynamic corridor feature line that is "targetable" as an Offset/Elevation within same corridor from a separate baseline.   Often times, we have one baseline that we could extract a corridor feature line from and then have another baseline that has a SA that can "target" the first baseline's extracted feature.  This works if the feature is static but fails if the extracted feature is dynamic, which is a bummer.     Show More

  Kindly requesting improvement of Vehicle Tracking reverse maneuvers for large vehicles, e.g. trailers, road trains, special vehicles, etc. As of today, the software is limited to some extent for reverse driving. Although ManualDrive offers better results than AutoDrive, it shows issues, particularly with large vehicles. This request is based on several users' comments.   Show More

Requesting to consider the development of Standardized Data Tool (SDT) for Civil 3D (C3D) to make it compatible with Autodesk Construction Cloud (ACC) projects. Request based on users' comments. As of today, SDT for C3D does not work with ACC--it does not open files directly form DOCs. Based on user's comments, it would be a great tool to be incorporated into ACC, considering that many of them are migrating from local to cloud solutions. Show More

Civil 3D does not have an option to dynamically label feature line properties—such as name, elevation, etc., when those lines are projected into a profile view. Consider extending the label styles to the projected feature line. To Work With Styles for Projected Objects in Profile View.   Show More

When targetting to all the geometry (feature lines) of a certain layer, sometimes you get undesired results such as targetting to the wrong side of the corridor, using elevations from geometry of the other side of the corridor baseline,... You can prevent targetting to the wrong side by using the option 'Use targets on the same side as the subassembly'. BUT, this option is only available when using horizontal/width targets.  This option should also be available with elevation/profile targets to prevent subassemblies target to e.g. elevations of feature lines in the other side of the corridor baseline. This could prevent the use of 'double layers' (layer_left and layer_right) to work around the lack of this option. Show More

In the 2026 version of Civil 3D. You can't us an OSnap in any Visual Style other than Conceptual or Wireframe. That included Custom Visual Styles. I would like to see the ability to Snap in any Visual Style returned to the program. It can be difficult to edit Surfaces when you can't snap to the Tin Line endpoints. Show More

Please, please please update Part Builder for pipe networks. There are so many structures that need to be created for many offices and Part Builder is just not up to the task or takes a significant amount of time to accomplish.   This has been needed since Part Builder was realeased.   PLEASE PLEASE PLEASE! Show More

Having all defined Surface targets being set to only horizontal severely limits the ability to debug subassemblies and also limits the ability to develop more complex subassemblies. I currently use a work arounds of creating a variable(s) that targets a link with a slope and then prior to saving the pkt for C3D testing and use I switch the variable to be targeting a surface via the Auxiliary Surface link. A simple target surface slope option would make developing end condition subassemblies easier to debug and give users more design feedback. Thanks for your consideration. Show More

Adjust Vehicle Tracking roundabout standards: Fastest Path Calculation. When assigning the Fastest Path Calculation parameters to the Roundabout in Vehicle Tracking in Civil 3D, when adjusted to a certain value (f.ex; 1 m) the result given shows 1.2 m. When reducing the offsets for the fastest path calculation (Island offset and Entry offset) from 1 m to 0.7 m and 0.6 m respectively, the design speed shows an increment. Whilst the 1m offset is minimum, the standard is not saying greater than that is better. The standard is looking for the fastest path with smallest radius without being closer than 1m to the kerb line.  Moving the entry path from the 1.2 m offset to the 1 m minimum increased the speed and entry path radius such that it changed from acceptable to not acceptable. It is the entry path radius that the standard is measuring. If the entry path is drawn with a greater offset than 1 m, we would need to demonstrate that entry speed has increased by using a larger offset. In nearly all cases the fastest path will be through the 1 m offset. VT should only be drawing an offset greater than 1 m offset if it has reached the fastest speed. Show More

I would like to be able to show delta angles in a label (on the right) for pressure fittings. Currently we pull this from an alignment label (shown on left).   the geometry is in the part; we just want access to reference it in the label either directly or through an expression. Show More

With the BIM4i, BIM for Infrastructure, transition to the model(s) as legal deliverables vs. typical flat PDFs, the creation of dynamic 3D C3D labels needs to be considered (this is addition to attached Property Sets) What do I mean? Labels placed on a Civil 3D object rotates to maintain visibility/readability when the view is rotated to 'model' view. Currently, all C3D labels stay at elevation 0 [except contour labels and COGO Point Labels. However, they remain oriented to the XY plane] To start, these new label types should be visible in the new Civil Model Viewer within C3D. Show More

When we are defining an alignment with a free curve by Radius we have to try several Radius value until it is accepted. C3d is saying, "There is no solution" with each typed radius. In my opinion, c3d knows the maxium valid Radius for that scenario so if I select typing a Radius, c3d should suggest us which maximum value is. Or more details about what " no solution" means: There is not any solution, typed radius is huge...etc..   Message like  no solution. Radius is too much big. Maximum accepted radius is... Thanks. Show More

For featureline creation and editing there are a couple ways to identify the vertex elevations and grades.   1. Elevation Editor Panorama: it is useful, but difficult to identify which vertex or tangent grade you are editing and is disconnected visually from what you are editing.     2. Quick Elevation Edit Button: This is also a handy tool that allows you to see and edit the elevation or grade directly onscreen by clicking on the vertex or tangent.  Yes, useful, but you can only see the single elevation or grade you are hovering over.       3. Create Line and Curve Labels: Last is to create your own labels that add the start/end elevations and a grade label on the tangents. Must create separate labels for curves.  Labeling is the only option to see the information fulltime.  It is time consuming and adds needless extra content in your dwgs. A big drawback to "Labeling" is, if you add another vertex somewhere along the featureline - All the labels shuffle to the left each time you add a vertex. Leaving the last segment to require re-labeling.   THE SOLUTION: Add a new button to the Featureline Modify ribbon to toggle on/off temp graphics that label the slopes/elevations for all feature lines. Perhaps it can by applied to only a certain site or certain featurelines within that site.   Add a new property to featurelines that would either Enable/Disable this new toggle of the temp graphics for that featureline. Then the user can control which featurelines show their information.   Add a C3D settings for this toggle feature that would control the: - size of text - color of text - decimals for elevation and grade/slope - preference for Grade or Slope display - only show temp graphics below a certain screen zoom height.   I feel this would eliminate a lot of labeling and management of text that is not even required.              Show More

When creating Infrastructure Parts Editor (IPE) content, you need to model 3 elements in Inventor: Underground Structure, Surface Structure and grate/cover. These are assembled in IPE as an entire Structure and used as such in Civil 3D via the Generic Pipe Structure Catalogs (or your own IPE based catalog). For documentation purposes, it would be helpful to be able to divide ('explode') those structures to their original components, e.g. to dimension the different parts per used structure in the network. Export C3D Drawing, 'ExportToAutoCAD', explode,... results in one single 3D solid or just AutoCAD Surfaces/Regions, which are unusable for this purpose. Show More