I see what you mean. By default, FillSrf tries to meet the document absolute tolerance for the positional constraints and the document angle tolerance for the normal constraints. Your document has quite strict tolerances that increase the refinements of FillSrf unnecessarily, ultimately not giving a result with default settings. I’m not saying that having strict tolerances is bad, but in this case it does not give the result you’re looking for.
If an angle tolerance of 0.5 or 1 degree is used, FillSrf produces a similar result as xnurbs. Even 0.2 degrees works, but 0.1 does not.
Correct, trimming is only supported in cases where a single, closed trim-loop is present, made from G0/G1/G2 border constraints. Having surface edges as internal constraints with continuity is an existing feature request.
Right now, it should be possible to trim the result obtained with the constraint curves you selected in a next step after FillSrf. Looks like it is necessary to duplicate edges, trim edges to form a closed curve & join prior to using these edges as trim cutters though.
In a 4 sided situation like this, I get different results when I select a curve or an edge.
The constraints are all G0.
The area where the mouse pointer sits is to be filled.
Does this mean that the tool is incapable to inherit the same properties (number of control points and degree) as the input curve? VSR for Rhino 5 used to have such an option to eliminate any deviation around the border, along with a real-time deviation reading. Having an automatic deviation graph will greatly reduce those cases that lead to inaccuracy and overly-complex surfaces.
@Rhino_Bulgaria that particular case, if the tolerance is lowered, it will still generate the untrimmed result. In some cases, with a starting surface, it is possible to maintain the same structure. But in general Fillsrf patches are not going to be single span surfaces.
the FillSrf command has been renamed to Patch. The buttons and menu items for Patch will now work for the new command that was formerly known as FillSrf
if you accidentily type FillSrf from muscle memory (I know I do ) this will start the Patch command.
the existing Patch command is still available as PatchOld but you need to type the name into the command line as it will not autocomplete
the original post (scroll up) has been extensively edited to describe the current state of the command
Why did we do this? Two reasons:
The command formerly known as FillSrf does almost (*) everything that Patch did, and better
The name of the command got confused with FilletSrf.
* the new Patch command cannot (yet) preserve the edges of the input surface.
“Kids these days go and model everything with the Patch tool. When I was a young lad, we used to make fun of the patch tool, we built all our surfaces by hand with edgesrf, changedegree and then building like metal panels with an ironworker, but with our mouse”
) this will start the Patch command.
