Camber Feedback Thread

[mzjensen]

@patrick.ericson

I know that you are busy but maybe you can put it in your backlog.

Sure! Adding to the backlog is the easy part

[mzjensen]

@Drbohlav

is it possible with Camber to add sample section sources from TIN surfaces to section views? Is it posible to project objects (cogo points) to multiple section views?

No, not at this time.

[mzjensen]

@elliotgr2010

It looks like the CodeSetStyle.RemoveItem node only works with point codes.

Thanks @elliotgr2010, I’ll look into it further when I have time.

[mzjensen]

@aravind.akhil007

I am facing an error for the Profile View Style node, which shows “Dereferencing a non-pointer”.

Tough to say without more info. If you share the DWG I can try to take a look.

[craigp]

Hi Zachri,

Do you have any nodes to Extract Part(pipe) Geometry of Profile Views?

[mzjensen]

Not at this time.

[craigp]

Possible to add Pipe Network Parts and Pressure Network Parts on profile view in your package? I found this for pressure parts:

https://help.autodesk.com/view/CIV3D/2023/ENU/?guid=8cd967f8-ec32-d496-827e-9ea8c8880ff8

[Ken.HoGXTTP]

I would like to ask if your installation package has a node that can extract the actual path of Xref, because one of my changes is to write the actual path of Xref that already exists in the drawing into the EXCEL table. I don’t know if your installation package node has this function.

[mzjensen]

Hi @Ken.HoGXTTP,

The short answer is no, not at the moment. There was a similar question earlier:

Camber Feedback Thread

Hi @mzjensen I want to show you the tricky part when applying your ExternalDocument.LoadFromFile node. In a nutshell, the point is that if you feed this node with a relative path of a file, the node returns null. [Screenshot_null] It looks to me like an elegant solution to add to your package an additional node (FoundAt) which would return an absolute file path. [Screenshot_FoundAt] [Screenshot_Xref] I’ve attached all the source files below. test_ExternalDocument.LoadFromFile.dyn (8.5 …

And I haven’t had time to look into it further.

Camber Feedback Thread

It isn’t quite that simple, but I can add it to the to-do list for when I have some free time to make updates.

[Ken.HoGXTTP]

Thank you for your reply. Yes, I have the same problem as him. I also want to call that node to solve the problem. Unfortunately, the drawings of our drawing colleagues usually have hundreds of Xrefs. This FOUND AT node is really good It helped me. I hope you can post an announcement as soon as you update

[mzjensen]

FYI @ana.ortizMPU5K

I want to ask dynamo if there is any node that can extract the actual path of Xref

This node is available in Camber v4.2.5 [full_path]

[mzjensen]

Hi all,

I just put out an update (v4.2.6) that fixes a fairly impactful bug in the ExternalBlock.Import node. If you use that node, I suggest installing the latest version ASAP to get the fix. There was just a single line of code that resulted in the entire source DWG being inserted into the destination drawing as a block. Whoops!

[patrick.ericson]

Oups
Good work to find the bug.

[emilezankoulHGWH9]

Edited by @mzjensen
The following is a comment about the GeneralSegmentLabel.ByObject node.

---

This is great! However, it doesn’t seem to work on closed feature lines. Is that expected? If so, is there a workaround? Thank you!

[mzjensen]

The segment count should just be equal to the point count in that case.

[emilezankoulHGWH9]

The node itself doesn’t seem to work for closed feature lines. Not just the node with the segcount code.

[mzjensen]

Which node?