Hi Jacob and all,
I’ve gone away and fiddled with DirectShape.ByGeometry, Springs.DirectShape.byGeometry, and the lowly ImportInstance.byGeometry.
As to my progress, I’ve only been able to realize geometry in Revit from what looks to be the simplest form of “dumb solid” import available. Niether DirectShape.ByGeometry, nor the Springs version get me past the solid preview image in Revit. I would like to bring solid geometry with text string parameters attached. Alah, a family type from which I can schedule the information in a simple table.
The geometry generation is on right side of the graph. When I do ImportInstance…
There are solids that are selctable in Revit.
Connecting the Springs.DirectShape.byGeometry node.
I have a preview of an object but not geometry is saved with the document. Similarly when using the Directshape node.
The watch node has 7 unique items. Good. Revit is previewing the tessellated ducts. However, I have no real or selectable geometry in the default 3D view. I would like to use this geometry and attach 7-8 text strings to each duct system, I would like to define these ducts within the Mass category and create simple schedules within this Revit family.
I would like to use the Springs.DirectShape.ByGeometry node because of topology concerns. Where’s the beef? or geometry rather…
One Last Thing…
I’m struggling with useage of the ScopeIf node I asked about in a previous forum posting Error Trapping an Empty List. It was suggested that a Scopedif would be the correct node for logical branching
test if a list is empty. List.IsEmpty node. Boolean determines empty list. If true, stop. If false, make a solid. Close up is below. I’m not sure how to connect this logical decision in a uml context.
The objective is to create geometry that is accurate for collision detection with a small amount of Family type information to support schedule creation.
Thanks for your Help!