The GeneralSegmentLabel.ByObject one. See error below. This only happens for closed feature lines.
Can you share a basic DWG with a closed feature line that gives this same result? I do not experience the same thing.
1 Like
Glad it works on your end! Before wasting more of your time, I am thinking maybe itâs a version issue? I tried downloading the latest but it is missing the GeneralSegmentLabel.ByObject node. Which version do you recommend using?
That node only appears in versions 1.0.0 and 1.0.1. And both give the same error.
I cannot upload the file since Iâm a new user, but here is a wetransfer link to it.
Youâll just need to update your Civil 3D version to the latest. That will vary whether youâre using C3D 2020, 2021, etc. but just install the latest update and then you wonât have installation issues with Camber. Once that is done, I recommend the current version of Camber (v4.2.6).
1 Like
Hi, thank you very much for your work! I found useful nodes in the Camber package. I was able to build up a very fast pressure pipe network. I have points without height and a surface, and of course a pressured pipe network of pipes.
Could you help me how I can place Appurtenances into the network?
hi everyone
i try to add pressure parts in a profile view used by Camber. its getting an error as below.
This capability is not available in Camber at the moment.
Hi all. I wanted to create profileview labels for an alignment with multiple profileviews. When I am using Profileviewstationelevationlabel.bystationelevation, I am only able to label a single profile view; it is not working fine with multiple profile views.
@aravind.akhil007
Itâs probably just a matter of setting the appropriate list levels and/or lacing for the node.
Iâm grateful for your response. I understood; I had to segregate the station and elevation values into lists according to the profile view range.
Hi @mzjensen 
Iâm using the mleader.bypointblock node and was wondering if there is a way to create mleaders into sheet layout? Thanks!
Hey @KirkWM - hmm, Iâm not really sure why I didnât include an input on that node to specify the destination block. I will explore it a bit further and try to put out an update as soon as Iâm able.
3 Likes
Hi @mzjensen
Using your âExternalBlockReference.SetAttributeByTagâ node, I attempted to change the attributes in the blocks that are in the external reference. But I wasnât succeeding in doing this. Dynamo indicates that the attributes have changed despite the dwg xref file remaining unchanged.
Do I have this rightâit is theoretically possible to change the objects in the external reference file?
If so, what am I doing incorrectly?
Iâve attached the test files in the section below.
test_ExternalBlockReference.SetAttributeByTag.dyn (33.6 KB)
test_ExternalBlockReference.SetAttributeByTag_file.dwg (806.7 KB)
test_ExternalBlockReference.SetAttributeByTag_xref.dwg (820.3 KB)
Hi @ana.ortizMPU5K,
Iâm not at my PC and so I havenât looked at the files you provided, but it sounds like maybe you need to save the external document and then reload the xref?
Dear @mzjensen
To make it clear, I expected it to work like this: the host file is open, and it contains an external reference file. Running #dynamo should change the attributes in the #xref file.
I did some tests: with an opened #xref file, and a closed one, but the result is the same. There is no change in the #dwg model.
Yes, exactly. You need to save the ExternalDocument after youâve modified the attributes, then reload the xref to see the changes.
2 Likes
âManage Data Shortcutsâ node would be really really useful.
input0 = CIVIL3DOBJECT
input1 = data shortcut CIVIL3DOBJECT
I wish i were smart enough to figure this outâŚbut iâm not 
