Everything about this node is pretty much the same as the Form.ByLoftCrossSection, except it can create multiple loft forms based on the lists structure passed into it and assign them to be solids or voids based on a list of boolean values (true / false).
Form.ByLoftCrossSections is one of two OOTB Dynamo nodes available in Revit that produces a type Form geometry (native Revit geometry). It requires the input of a ModelCurve which you can get from either a Modelcurve.ByCurve or a ModelCurve.ReferenceByCurve. You can only use this node in a family as both the ModelCurve and Form.ByLoft nodes will only work in family environment.
If you pass a false into the isSolid you will get a void rather than a solid.
If you need a more complex geometry in Revit, take a look at the Form.ByGeometry node from Spring Nodes.
Form.ByGeometry “bakes” any solid, polysurface or surface passed into it into the active Revit family environment as a Free Form Element type (native Revit geometry). This should be used in the place of ImportInstance.ByGeometry in every instance. (a similar result can be achieved with the FamilyInstance.ByGeometry from a project level). In some cases you should even see handles appear which will allow you to manipulate the goemetry to some level once it is “baked” into Revit.
Using some python coding which you can find here, it is rather easy to set a section box to a scope box in a 3d view.
There are a couple of ways to go about this (all of which require Springs Nodes):
- If you are in a family environment it is as simple as this:
- If you are at the project level of a Revit project then there is a just a bit more that needs to be added:
In the end though, the results are pretty much the same. You should end up with native Revit, free form elements, some of which will even display handles which can be used to edit this geometry (usually simpler, rectilinear geometries such as boxes will be fully editable, other times things like lofted geometries might have and end face that is editable).
Be aware that there is a scaling issue currently with dynamo’s SAT import nodes where the they only read the geometry as though it were in meters, but this can be easily fixed through some creative scaling before “baking” it into Revit.
This workflow can also be used to bring SAT information into Revit from Inventor as well.