Explode Node Bug?

In my attempts to create 3d polylines from feature lines, I fell back on the the inelegant solution of copying and exploding the feature lines, and moving them to a different layer. When I do this though, I notice that my original feature lines disappear after I do a regen.

If you look at the handles of the entities being passed to copy/ explode nodes, they are different. This should leave my original feature lines intact right?

What seems to happen is the feature lines disappear from view after running a regen command.

After running script:

After running a regen:

What is even more odd, is if I check the entities in the drawing after running the regen command, even though I can’t seem to see the feature lines they seem to still be in the drawing. The undo command doesn’t seem to restore the feature lines either, the only option is to close with out saving and reopen the drawing.

After running script:

After running a regen:

Feature Lines - Feat to 3D Polyline - By Site (V1).dyn (34.7 KB)
Feature Lines - Feat to 3D Polyline - By Site.dwg (914.2 KB)

1 Like

Great catch, @DevinLJackson. I just had a look at the code and understand exactly what’s happening. The issue is with the Object.Copy node and it should only occur when used with feature lines. This is a legacy issue that has likely been this way since the inception of Dynamo for Civil 3D back in 2019, but nobody had the eagle eyes to catch it :wink:

1 Like

Haha, I love when it is an easy find / fix!

Dynamo is becoming really easy to use, especially since 2025.1; but I feel like I’m always trying to do the odd things with it and finding new and interesting ways to break it. :smiley:

Keep doing it. We do our best to account for all the edge cases, but inevitably we miss some from time to time. Thanks for your patience and for reporting what you find :+1:

1 Like