Just wondering if there could be a component to read all Reference plans Inside of Revit to then be able to assign a Structural framing Beam to that reference plan?
Also to Create Reference plans with a line in Rhino/Grasshopper.
This is so if you handed to project over to a non Grasshopper user and the roof awing plan changed levels the non grasshopper user can just move the reference plan.
Also some BIM Audit tools reviews if framing elements are attached to reference plans… not just randomly in space.
It would be great if you could add some images explaining what you meant.
What I understood is you link some CAD files into structural views and you want to create beams automatically from that linked CAD file. I did something like that in the past, generated columns and beams from the CAD drawing. But CAD file must be standardized.
Thanks @Japhy using a Beam Framing Family… are to be set out by lines as all elements can be different sizes.
Original Revit users will create a Reference Plan to assign structural framing beams that are on a angle.
So if a non GH User was to update a reference plan it would update all framing attached to a reference plan. Just like a level update. Then the user will not have to open or re run scripts to move elements on a reference plan.
Then if the script is re run it would still be set to the updated reference plan.
A plane in GH / Rhino is pretty straight forward. The particular workflow you want is possible, but will be a custom workflow tailored to a internal non-gh user.
I was meaning a reference plan inside of Revit that is created through RhinoInsideRevit. Not just a plane in GH/Rhino.
Beam elements can be attached to a Reference Planes in Revit.
So if a non GH user updates the Reference plane in Revit it will update the beam position and also the updated position will be referenced in grasshopper.
I’m not quite following. You want to add Revit functionality of a named reference planes that are created by Rhino.Inside.Revit that a user in Revit can select?
The Beam by Curve is pretty flexible. The non-GH user aspect of your proposed workflow is a different story.