Select a few control points of the curve (note how the entire curve is still highlighted too).
Project onto a surface without changing the selection (note how the entire curve is projected).
Isolate.
What happens now if you leave the filter on is that error message.
However, if you are careful to turn the filter off before step 5, you still don’t get anything isolated, yet it appears as if both the projection and the original curves are selected (and the gumball is placed in between both the original curve and the projected result).
You can use any document. Just turn Selection Filter Control On and right-click on any object type to filter for only that type of object, select one of them matching the type and attempt to do Isolate.
You should see the error message.
Only with selection filter off (or all object types selected in the filter toolbar) does Isolate work.
I’ve hit this before as well but didn’t investigate. @eobet seems to have ‘isolated’ (haha) the conditions. I can confirm the error message here using:
Version 6 SR26
(6.26.20147.6511, 5/26/2020)
Commercial
It turns out that Polysurface section must be enabled so the Curves selection works.
If you replace the polysurface with a surface, the Surface must be enabled so Curve selection works.
One other object type in the scene must be enabled for selection or the filter does not work.
Change your filter to only select Polysurfaces, then try to Isolate it.
You’re get the same complaint with polysurfaces.
Very curious
Mikko should have this figured out pretty quickly.
I’ve just encountered this same problem in V6 in 2024, ‘Unknown Command $$Isolate$$’, although I can’t seem to reproduce it.
all unselected items then get deleted, rather than hidden. I can undo, so not a major problem, but could be an issue if I don’t notice and save before realising something has been deleted!
I don’t have selection filter open. I am just dragging to select various curves and surfaces.
Unknown command: $$Isolate$$
Appeared for the first time for me this morning. Rhino7. Some layers were locked and remained displayed. Seems like all of the instances this error can arise in have not been handled yet.
I cannot replicate this $$isolate$$ error quickly with the same file and am on another, unrelated to Rhino, project.
One more thing that entertained us this morning was that the perspective view in shaded mode with a locked object managing to hide behind another in error. Pictures added. It does not happen in other viewing modes. Like a 3D version of an optical illusion.
The ‘back’ view of the locked item is also problematic when in shaded mode. The main (brown) surface of the disappearing object has an element of transparency set in rendered mode.
