@pascal,
this bug seems to be an issue that is manifesting in v8.
During the ExtractSrf command -
Window select right-left or left-right over a polysurface, hide extracted surfaces and some random surfaces are left behind.
I even tried this on a simple object like a cube and one of the faces will get left behind.
Same thing with window selecting over only have of the polysurface - some of the surfaces that should have been selected are not and remain attached to polysurface.
The ExtractSrf command will not allow you to select a single surface by directly picking on the surface - as would be expected - there is nothing to extract. But if you window select a single surface in the ExtractSrf command, it will allow it to be selected and the command line will report âExtracted one surfaceâ. If you have copy=yes, it duplicates the surface.
If you start ExtractSrf first and select one surface, it does what is expected.
If you start ExtractSrf and window select the entire polysurface, it acts like Explode, and Hide makes then all go away.
Please run SystemInfo in Rhino and post that in a reply.
Also please describe the steps you are following to duplicate the issue you are seeing.
I have the same issue in v8âspecifically in Shaded viewport. Extract doesnât like to select surfaces that it canât see, so the command either has to be done in Wireframe or spin the model around and manually select whatever surfaces werenât initially selected.
Trying it a few more times, maybe itâs not a visibility issueâright now I have some geometry where a window selection isnât grabbing the front surface, regardless of shaded or wireframe.
I can repeat this to some degree - interesting. Below is a file with 1000 cubes, I used ExtractSrf and ran a right to left crossing selection. The red line is just there for reference (use the saved view), select from the bottom right to the upper left and hit the red line. In theory, as itâs a crossing window selection, all surfaces below the red line should be should be extracted and remain selected. But if I move the result to the right with the Gumball, there are a bunch of surfaces - all cube âtopsâ - that are not selected. They remain there while all the surfaces around them are moved away. Same if I unselect first then SelLast, those surfaces are not selected. So actually they didnât really get extracted, but the surfaces surrounding them did.
Actually this happens with one single cube, you donât need 1000. The top surface always stays. I guess that is sorta logical - all the other surfaces in the polysurface have been extracted (one-by-one I suppose) and whatâs left is a single surface that cannot be âextractedâ because itâs no longer part of a polysurfaceâŚ
Iâm not seeing any other âoccludedâ surfaces not extracted yet though.
Hereâs another strange detail with the cube example. If I window select over the entire cube twice it extracts all surfaces. If I only window select over the cube once, the top surface does not get extracted.
Hi John, Helvetosaur - thanks, I seeâŚ
I guess the logic must be that there should be some of the original object left after the extraction. The last face in the brep face list is the one left if all faces are selected.
I donât know how this should be handled, to be honest⌠it kind of makes sense.
Hm - it is not consistent though, so it just became a bugâŚ
In this part I was trying to extract the entire pocket to copy it to another similar part. In wireframe I drag a box left-to-right that includes all the surfaces of the pocket, but the base of the pocket is not included in the selection. I moved the extracted surfaces to the right in this example for easy illustration.
I tried to replicate it using a simple cube-shaped pocket but then everything selected fine. That made me wonder, if the untrimmed version of the surface that makes up the trimmed base is larger than the window that I dragged, maybe a glitch was keeping it from selecting that trimmed surface. To test that theory I right-to-left dragged in the Extract command, but I get the same result so thatâs not the problem.
Canât post anything proprietary.
When I water it down by taking away the rest of the part and then trim to a more simplified shape, the Extract actually works. All pocket surfaces, main adjacent surface, and opposite surface (away from camera) are all the same data as before just trimmed differently. For some reason now it extracts all the pocket surfaces with a single selection window.
Unfortunately the only way to be able to determine what the problem is is to have a repeatable example. Without that, nothing will get fixed, because thereâs nothing to test and debug.
