I agree that yellow could be confusing.
Layer color may be the simplest choice.
Try with a transparent color, 35% gray (as a ghost) could be fine.
While youâre at it, please add a transparency slider to the selection color for Rhino too. I would prefer if selected objects could be less obstructive to the view.
Weâre currently doing the layer color for the shaded patch, and ChooseOneObject.HighlightColor for the control point lines, this is also used in previews for e.g. ArrayPolar etc.
Note that adding transparency to the selection color is possible already, at least from v7 upwards, maybe even in earlier versions.
Go to Tools > Advanced and change Rhino.Options.Appearance.SelectedObjectColor and add transparency there.
9.0.25112.12305, 2025-04-22
- Running FillSrf first time should also bring the user to the selection phase (without needing for an additional click âSelect constraintsâ), this would give a bit more consistency with the most of other Rhino commands.
- FillSurf preview color should be different from selection color (yellow)
- after changing the selection with âSelect constraintsâ curve elements are still selected
- after changing the selection with âSelect constraintsâ the preview is not always shown
- internal details works properly only if they are curves and set as âIâ (Internal?)
- it is not possible to use surface edges the same way, âIâ as âinternalâ
- it is not possible to use surface edges to give G1 or G2 information for an internal part of the resulting surface
- moving an âIâ internal curve while FillSrf is running and then doing Undo will create a double selection of that curve and make impossible removing them from the selection
Edit, about selection, for now I would totally UnselectAll at start, before âSelect constraintsâ , and once that selection is completed, unselect every geometry used. See video.
If a user have a selection outside the screen, clicking âSelect constraintsâ would add that geometry to the constraints.
Maybe itâs better to have âSelect constraintsâ not accepting pre-selections? Not sure about this but currently it feels strange entering âSelect constraintsâ with no selection and finishing/exiting with something selectedâŚ
Are you kidding me? And we have asked so many times for the ability to turn off selections for when moving large meshes and THIS has been right in front of us all these years? This is super nice, thank you! And PLEASE update the color selector for âSelected Objectsâ to include this in the GUI.
Having it hidden in the Advanced settings doesnât help many people ![]()
(Just putting it here in case anybody else finds this info)
Thanks @maje90 for your detailed video, it really helps to see users exploring the tool and explaining what works and does not work for them.
- The selection color will change in the next WIP version, expected on Tuesday/Wednesday this week.
- Seeing multiple buttons upon undo: this has been fixed and will also get into the next version
- G1/G2 for internal edges is an existing feature request that I will come to later
- Start with selection is also coming to the next version
- Jagged updates are also fixed in the next version
I have created a ticket for the color chooser to be updated here.
Not sure if itâs possible right now, at least I canât get it to work:
When I select a surface edge as an internal constraint, I canât set it as I.
Means I have to _dupedge before.
I think it should be possible to set an edge as I.
Yes, that will become possible together with higher continuity for internal edges. This is what is in the existing feature request you quoted.
A next example for a nice result:
CP_2025-05-12_FillSrf.3dm (1.5 MB)
The original black polysrf shall be replaced by a single srf without much effort.
I used the duplicated border of the original srf and some projected points for the internal constraints.
Why is the tolerance for the internal constraints max. 1?
Iâd like to see if a looser tolerance could make a smoother result.
The model is large (~23000).
Makes sense, Iâve made a ticket for that https://mcneel.myjetbrains.com/youtrack/issue/RH-87391
While that is not yet possible: a scaling by 0.01, FillSrf with boundary tolerance also divided by 100, but internal tolerance left unchanged, follwed by un-scaling by 100, could already help maybe?
Why didnât I think of that? ![]()
This gives the expected result, great.
Scaling is good for an intermediate test, but Iâd still prefer free access to the tolerances.
Or restricted by a bounding box factor or whatever.
Yes, this will come when the ticket has been done.
ExampleX.3dm (545.5 KB)
This Was done with Xnurbs. The 6 sided hole. I found it to make a better match than the new fillsrf. just putting it out there. Thanks for the work youâve done.âMark
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.




