I bet it’s easy and I’m doing it the hard way

To fill in the (flat/floor) area , I’ve been creating a face by laying out vertices at every intersection on the opposing sides, My face is laid out with a vertice matching every segment intersection on existing sides.

It’s very time consuming and the geometry is messy.

When I start bridging I have to fill two holes at the beginning of every face/plane I make, which leaves a triangle in the geometry, it’s all ugly around the bottoms
I want the geometry to match the linear lines if possible.

I’m positive there is a more efficient process with better results for the geometry.

I’m curious why you are using SubD?

To model this in NURBS I would do something like this (details depend on what is given):
Create a flat floor.
Create curves which will be at the top of the blends.
Project the top curves onto the floor.
Offset the projected curves with desired width of the blends.
Trim the flat floor with the offset curves.
Assuming the blends should be vertical at the top extrude top the curves upward.
Create blend surfaces between the flat floor and extrusions.
Delete what is not wanted.

“Different strokes for different folks”

1 Like

I’m looking for a monolithic shell, I’ll be offsetting this soon, but I believe I just figured out some technique with bridge and bridging multiple faces at once, the first bridge sets being the most important to get the system/sets going in order

I’m also going to try what you described, sometimes the floor is not flat and the top not level, Which is how subD becomes the heavy swinger at bat

You could simplify the amount of faces you need to support the silhouette of your model.

1 Like

Define the number of faces in a more clever way: either the inner elements define the number for the frame around- or reversed.
Use some of rhe following patterns where this is not possible.. .
Google or check pinterest for more of these…


Kind regards tom

That is a good technique, do as many edge pairs as you can and then fill in the gaps. Stitch is sometimes needed too. FYI, we’ve got an open request for Bridge to work on non-matching edge counts and I’ll nudge the developers on it (RH-62453). Thanks.