Strange… the offset can be made and imported in Dynamo:
Yet it is not visible in Civil 3D, also it does not exist in the Prospector. I have to examine further.
1 Like
Glad to hear 
While debugging I can’t find anything wrong with the code. Only in the GetDynamoGeometry, a widened offset Alignment seems to contain MultipleSegments elements. That is the reason why you didn’t see the whole part of the Alignment in Dynamo, but in Civil 3D there seems no problem with the created Alignment.
In the next version of the package I’ll update the GetDynamoGeometry node.
1 Like
Thanks alot @Anton_Huizinga for looking into this and will be waiting for next release.
Thank you for creating the nodes on working with annotation scales.
After studying this set a bit and applying some of the nodes in my script, I have a suggestion: Wouldn’t it be more logical to have Object{} for the nodes in the image as an output?
In the script I insert the blocks, apply the desired annatational scale to them, and then to continue working with the updated blocks (with the previously added annatational scale) I need to get them again. In this case it would be handy to have updated objects at the output of the node.
1 Like
Thanks for your feedback!
I am not sure if objects would be a better output, because the list of objects you have put in, is also available to do other things with. But on the other hand, the same count for Annotation Scales. Maybe void would be better.
I’ll think about it, and if possible, I’ll improve the package soon!
I’m going by the logic used in Autodesk’s OOTB nodes.
When the action is either Set or Apply, the output is updated objects. And this is very practical.
Otherwise how to get the list of updated objects! Only to run the collection over the whole document. And if you chose the objects in a tricky way in order to apply annotation scaling to them, then you need to include a complicated filter.
And if the objects were selected through the “Select”. It becomes even more complicated.
Maybe you can make two outputs: Object and AnnotationScale?
I am not sure if the OOTB nodes give access to the updated objects only or to simply all objects that were fed through the input port.
Also, the output of objects might be set because of the group ‘Object’, so the logic I followed was to output the type of the category (in my case the Annotation Scales).
I’ll put it on the list and will reconsider the logic.
BTW, if you feed the node a list of objects, you already have those objects to reuse for other purposes?
You don’t have to wait until the Annotation Scales were added.
I always try to do things in sequence.
When there are parallel actions with the same objects, sometimes there are unexpected surprises. And to avoid this, it’s better to avoid working in parallel with the same object.
1 Like
I would like to use the Mpolygon.CreateMpolygon node but i am stuck at getting the neccesary polyline inputs for the exterior and interior.
I have those as Polycurves, sorted in Lists (first is exterior, all else holes):
those do not work in your node since they are Dynamo Polycurves and not Autocad Polylines
what i tried:
-
The OOTB Nodes allow me to create Autocad polylines which results in an object of type polyline which Mpolygon.CreateMpolygon can read. I need polylines with arcs though, which the OOTB nodes do not create.
-
Creating the Autocad polylines out of my Polycurves using the civil 3d toolkit nodes → Result:
Your node does not allow those to be used directly (not of type polyline)
-
your Createpolyline2D Node would create the necessary polylines, but i have no clue how i can get the bulges from the dynamo polycurve in order to correctly generate those.
-
The only way i found to get the polylines is by your all Objects of type node after i created the polylines with the toolkit nodes, but i loose all information about interior and exterior loops.
Is there any way to get from my organized Dynamo Polycurves to the Mpolygons directly?
My last resort now would be to bake the polylines with property sets containing the necessary information for the correct List structure and go from there.
Thanks in advance!
Yes, I see. It would be nice if the MPolygon node accepts objects instead of Polyline, or that a node becomes available to convert an object into a Polyline object. I’ll add this to the wishlist.
After fiddling around a bit, I might have a solution. You can request the handle of the object and convert the handle into a Polyline object:
The ObjectByGeometry returns an object of an unknown type, but the ObjectByHandle returns an object of the Polyline type. Then it works like a charm.
2 Likes
This works great, many thanks!
hi, I don’t know arkance, but for the definition of a dictionary you need different keys (you have 6 key 1305 and 3 key 1350) and in string format under Dynamo Sincerely
christian.stan
1 Like
Have you downloaded the source and drawing from this topic?
Questions about the legofying of Surfaces can be placed there, not in this topic
thank @Anton_Huizinga
Hi @Anton_Huizinga,
Great package for Civil3D.
I’m trying to change all the dimensionstyles of the all the dimensions in an existing drawing with Dynamo. I want to use your node Dimension.SetStyle to do this. My problem is that i can’t get the right input for this node.
Do you know how I should get the right input from my existing drawing?
Yours sincerely,
Gijs
Hi,
It seems not possible with these nodes. You need a dimension object, not a generic object. But with the package you can’t select existing dimensions, you can only set the style to newly created dimensions with use of the package.
I’ll at it to the wishlist.
Maybe you can look at Camber, this package contains nodes that can help you further:
Thanks!!!