Sorry, I missed that post. Will have a look at it later this week.
Indeed a bug in the node library. I’ll put it on the backlog and will fix it as soon as possible.
1 Like
Hi,
A workaround solution you can find at
Good morning!
Thank you for your works.
There are comments to the node:
SlopePattern.CreateSlopePattern
Ah ok, that is indeed not desired. I’ll put it on the development list. Thanks for reporting!
1 Like
@Anton_Huizinga
Hello, Anton. I tested the latest updated version of the Arkance system node and encountered a problem with the alignment intersection node.
Is there any reason why the alignment intersection node, which used to record the intersection with the polyline in the model, also captures the points on the alignment geometry?
What is the basic functionality it is using to obtain the intersection points?
I have over 50 alignments and would like to record the intersections. it is giving unnecessary points.
If for any reason people want to know where the intersection occurs, they have to find the intersection point after finding the intersecting objects. So, this function does both already. You can use the points as a projection location or to calculate the station, for example.
But if you don’t need the points, you can ignore that output. To hide them in the Dynamo environment, you can turn off the preview of that node.
3 Likes
V7.2 is ready to download. Few fixes:
- Widening transitions are added at the correct widening
- Slope lines are now calculated to the shortest distance
And a few new things. Drawing properties for example:
Also you can merge cells in a table or break a table. You can raise or lower a Surface now. And there is an option to create multiple GUIDs if necessary.
Enjoy!
7 Likes
Fixed in v7.2.
Wonderful, Thank you for Sharing @Anton_Huizinga
1 Like
Time for an update: v7.3 is out now! Some minor improvements and small bugs are fixed. The package adds over 850 nodes to the library.
Two new object types can be created or read from the drawing: XLines and Rays.These objects also respect binding settings so you can update them, if needed.
Cogo Point Groups and Cogo Points have some new nodes. You can request a list of Cogo Points that belong to a certain Group and you can check if a Cogo Point is part of a certain group.
Select Similar:
To select similar objects you can use the new node for this:
It works with any object, not only the known types.
Tables:
Most work was done with the Table nodes. Working with Columns and Rows was a bit trial and error, so I added a new node to create a Table the easy way. Just feed it with a list of objects (or a list of lists with objects) and it is turned into a table.
You don’t have to transpose the data (it is done automagically), and this is the result:
Special lists with only Points or Coordinate Systems are turned into a table of seperate X, Y and Z values:
Results in this:
Numeric values are presented with the Drawing Units and Precision now.
Number column and headers:
With the automatic table, a generic column header is used. It is possible now to change that afterwards. Also a new node is available to add a number column at the left:
3D Faces, Triangles, Mesh:
There are also some nodes to create 3D Faces or Polylines from triangles. The latter are geometric figures that are used for several things. You can read triangles from a Surface and turn it into a Mesh, or 3D Faces in Civil 3D or PolyCurves in Dynamo:
Layer filters:
Also a few new layer filters are added:
With the Get Layers By Filter node you can easily create sets of layers you want to do things with.
Now available in the Package Manager!
12 Likes
Big thanks for all your effort creating and updating the package with new nodes. 
Regards,
Patrick
1 Like
Epic, Anton!
1 Like
Thanks for the Package Anton,
Noticed bellow issue with Alignment.GetDynamoGeometry Node. its not representing true geometry.
can you please suggest if anything i am missing here.
I don’t know? Does the Offset Alignment in Civil 3D differ from the geometry in Dynamo? A small test here looks fine:
Yes, as can be seen in the screenshot the widening and rest of the parameters are not seen. only a small section represented in Dynamo.
correct geometry is shown in this post - Civil 3D Toolkit Feedback thread - #988 by shahid.shaikh_C3D
I am working on 2020.6 version. Does this have any impact on the issue ?
Do you have an example graph and drawing?
The 2020 version is not updated anymore. You can install the latest version of the ASNL but I can’t guarantee it works.
Might be a bug in the latest package regarding TinSurface Dropdown.
I couldn’t see any TINsurface in the dropdown list after that upgrade to 7.3.0, neither surface in the file or DREF.
When I reversed to 7.2.0 everything looked fine again
Hey Patrick, I can’t reproduce any error here:
Do you have an example drawing perhaps?
Yes sure, here you go.
Offset_AL_Test.dwg (1.3 MB)
Offset Al_Test1.dyn (37.3 KB)