Some nodes have a notification about being obsolete, like the Alignments node:
I don’t want to discuss here why a perfectly user-friendly node must be removed and be replaced by some generic but less obvious node. But I noticed another node that has such a message in Civil 3D 2026:
The Line.ByTwoPoints might be removed too, according to this message. But in Civil 3D 2027, there is no such message.
Does that mean the node will not be removed later or has someone forgotten to add the message in 2027? Or something else?
Hey @Anton_Huizinga,
I believe the node itself is staying. Line.ByTwoPoints has a few overloads (different input signatures), and my understanding is that only one of those was marked obsolete, which is what the 2026 message was about.
I’m not 100% sure why it doesn’t show in 2027 though, so I’ll confirm with the team and follow up here. Fair point that the warning could be clearer about which version it means.
Hey @Anton_Huizinga,
Following up on this.
They made it obsolete on purpose. It doesn’t do anything Line.ByStartPointEndPoint → Object.ByGeometry doesn’t already do, and it probably never should have shipped. That’s what the 2026 message was about.
They’re also simplifying the deprecation policy and tweaking those obsolete messages so they don’t say nodes will go away. Nodes won’t get fully removed, but they still need to be able to mark them obsolete and point folks at alternatives. So 2027 not showing the same message isn’t someone forgetting.
Official write-up of the Civil 3D Dynamo node changes is here:
Too bad that the simplifying is so extreme, imo it is making things less obvious for new users. But that is another discussion.
Thanks for looking into it!
I disagree.
Inherited properties are light years easier for new users. This also mirrors how Revit which is a more successful adaptation in terms of users count at any level, in part because nodes have less reuse in the Civil 3D environment. ‘No you can’t use that .Name node, you need a different one.’ is far too prevalent in the Civil 3D environment.
This also follows the standards of C# and the AutoCAD API. Case in point, does the Civil3D API have a separate property for ‘Layer’ on alignments? Nope, it’s inherited from Entity. As a result this shift should bring stuff closer to alignment with how most develop in Dynamo and beyond.
