The wall-by-face issue sounds like an easy one, we’ll look into it soon. Although being able to specify a mass face as the base one is a bit tricky, and we might not have a solution for it in the short term…
Would you see a benefit in being able to create these objects directly from Rhino instead of GH? We could see what’s possible as part of the mapping tool.
@teocomi thanks for your prompt response and the pointer to the mapping tool!
I don’t know how I missed this one. The mapping tool seems to be exactly what I need. Literally two days ago I was showing Speckle GH to a few of my colleagues in the office and the feedback was that they’d love to use the workflow under the condition that it is directly embedded in Rhino. For some, GH is still very intimidating.
So yes, if WallByFace was a direct mapping from the mapping tool (and worked bug-free) you’d make a few people happy in our office.
Especially, if the mapping could be defined in the receiving application (Revit).
For this particular project we have a Rhino and a Revit person. Data flows in one direction (Rhino->Revit) but the Rhino guru only knows basics of Revit and we’d like to keep things simple for them.
Just coming back to let you know we fixed this limitation and it should be making it’s way to the next release (2.13). We’re going to release a new beta version sometime today (2.13.0-beta1) which should contain this, in case you want to give it a go before it goes out officially.
The new result should allow for weird boundaries in walls and weirdly shaped holes. It will follow the same restrictions as our Brep → Revit conversion (i.e. if the Brep fails, you can expect the wall to also fail, at least for now!)