Hi @zachri.jensen
Is it possible to use it on multiple files? Otherwise, I have no idea why “ExternalBlockReference.SetAttributeByTag” node is not working setting the attributes on multiple drawings at once.
I can’t really provide the drawing files - client standards etc, but the script is attached.
SetTitleBlockAttributes.dyn (32.4 KB)
hi @zachri.jensen
I’m trying to run a command in all drawing files in a folder. Id like to use the document.sendCommand node, but I want to be able to send a command based on the file name.
for example, I want to be able to read the selected folder, and if the file name contains “abc” it would run the command, but it would also work on all the other drawings in the folder so “xyz” would run a different command? is this possible?
Can you provide is some info about the error messages?
The last node return null on some values, would be good to know why.
I found that node MLeader.LeaderPoints works correctly with mleaders with two or more leaders but if it contains only one leader it returns error MLeader.get_LeaderPoints eInvalidIndex.
https://youtu.be/kCkBswmr450
dwg file
Using the profile view nodes to create pipe labels, running into this error but only when i use the profileview.findstationandelevationatxy node. For the profileview input i’m selecting an object and converting that object to a camber object, as i did (with success) for my input on the profileviewdepthlabel.bytwopoints node. However, on the station elevation node i’m getting an error that the expected argument should be of type autodesk.civil.dynamonoes.profileview, but is recieving type camber.civil.civilobjects.profileview. Any help?
Hi @safEWAE6,
That node is from the Civil 3D Toolkit, and unfortunately you can’t mix-and-match nodes from the two packages. If you want to stick with Camber, I’d recommend using ProfileView.GetStationElevationAtPoint
instead.
1 Like
I see that in 4.2.6 there is an Alignment Curve Label Styles node but I can’t locate an Alignment Curve Label creation node. Does one exist?
Running into an issue with the StructurePlanLabel.ByStructure node in the Camber package. I have a structure label for a structure at the intersection of two alignments. The label reads the reference alignment of the structure (Sta. 13+74.59, SWS Line 1 in the attachment).
The other alignment is pulled using a reference text component in the label in order to pull the station and alignment name of SWS Line 1A. So when I assign the alignment in the properties window, the alignment name (SWS Line 1A) shows up but the station shows three question marks ???
Label works fine if I was to manually place on the structure and then change the alignment in the properties window. For whatever reason, it seems converting to a Camber objects conflicts with Reference Text Objects? Any help would be appreciated.
Hi @luke.peter,
I was able to reproduce. Seems to only be an issue when the label is created by Dynamo. If you set the reference text component for an existing label using the Label.SetReferenceTextTarget
node, then it works. I’ll have to investigate. Thanks for reporting!
Hi @n.prokhor,
Thanks for reporting. I will take a closer look and see if I can figure it out.
Hi!
Im having some trouble with the “Folder.AddCivilObject” node, giving them the inputs but looks like the surfaces are not correctly stored in the desired folders.
Maybe I’m pushing too hard? Is the input not correct?
Thanks in advance!
Hi @JEdu_GM02,
I’m not exactly sure what is going wrong just based on the screenshot. Looks like the first two folders have nothing in them, the third folder has four items, etc. This matches the structure of the inputs. If that isn’t what you expect, then I would double-check those data structures. I see that the flattened list of folders has 255 items. The list of surfaces has 266 items, but it is split into a list of lists. Assuming you want to put multiple surfaces into each folder, then for this to work right you’ll want to have the same number of surface lists as the number of folders. So then the first list of surfaces (index 0) would be placed in the first folder (index 0). If the counts are different, then you’ll want to play with the lacing settings to decide which list length should govern.
Hi Zachri, could you please help me how to do Surface Elevation Analysis for TIN Volume Surface? The goal is to analyze cut and fill.
Hi folks,
Just wanted to provide an update on the current and future status of Camber. You may have noticed that there have not been any updates for quite some time (last release was 4.2.6 in March 2023). This is because I joined Autodesk in the summer of 2023, and so it no longer makes sense for me to maintain a side project when I am also working on Civil 3D directly. From this point forward, I do not have plans to make any more updates to Camber.
Regarding compatibility, the latest version was built and tested for Civil 3D 2024. Some of you may have heard that many Autodesk products (AutoCAD, Civil 3D, Revit, etc.) upgraded to .NET 8 in the 2025 versions, which meant that Dynamo had to upgrade as well. Camber has not been updated to .NET 8, although I expect that the majority of the nodes in 4.2.6 will continue to function in Civil 3D 2025. I have not done any testing to confirm this.
Lastly, I want to remind you that Camber is open source. The entire codebase is available publicly on GitHub, and this is not going to change. This means that even though I am no longer actively maintaining it, the doors are still open for contributions from others
5 Likes
Hi everyone,
I was able to squeeze out some time to update Camber to v5.0.0. This release addresses the issues with a couple of nodes that you may have experienced in Civil 3D 2025.1. It also upgrades everything to .NET 8, which means that v5.0.0 should not be used in prior versions of Civil 3D. Please continue to use v4.2.6 in that case.
I’ve added messages to a significant portion of the nodes to indicate that they can be replaced by equivalent nodes from the main Civil 3D library. The nodes should continue to work exactly how they did before, it just gives you a helpful nudge in the right direction
You see here a reference to a Migration Assistant. This is a simple little tool I built to help you upgrade graphs in bulk. You can find this tool in the extra
folder inside the package root directory.
It’s pretty simple to use, but consult the readme if you have questions. I didn’t have a ton of time to test, so it probably isn’t bulletproof. It will create copies of your graphs and doesn’t touch the originals, so you are safe to experiment.
As mentioned earlier, this will be my last major contribution to Camber. Moving forward, I will be focused on my role at Autodesk and making Dynamo even better inside Civil 3D.
10 Likes
I’m speechless, @zachri.jensen . Thank you very much.
Will check it out and also test the migration assistant tool.
2 Likes
how to design speed of alignment in dynamo?