Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 128GB)
.NET 7.0.20
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA RTX A5000 (NVidia) Memory: 24GB, Driver date: 11-13-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 553.35
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
Secondary graphics devices.
NVIDIA Quadro K2200 (NVidia) Memory: 4GB, Driver date: 11-13-2024 (M-D-Y).
> Accelerated graphics device with 4 adapter port(s)
- There are no monitors attached to this device!
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 11-13-2024
Driver Version: 31.0.15.5335
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 24564 MB
Rhino plugins that do not ship with Rhino
C:\Users\martinsiegrist\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
I’m afraid I don’t know what that means. Without anything selected, do you first type _Split, then _Pause, and then click the command line option Isocurve.
-wim
No I just right click the button to run the Split by Isocurve command and then I clicked Isocurve in the command line. This is stupid because the command is already in the isocurve mode but then why is the option available in the command line?
This bug has been around for 20 years.The bug was created by making split by isocurve an option inside the split command instead of a standalone command.
I assume the button you clicking on has a macro that looks something like this:
split pause isocurve
So what its doing is looking for you to pick anything that can be split instead of looking for a single surface which is the only thing that can be split by an isocurve. If you remove the pause it should behave more like you are expecting when nothing is pre-selected but then it may still misbehave when something other than one surface is selected.
I understand I don’t need to pick _Isocurve again but as @jim mentioned, the bug has been there forever and I can confirm it’s the exact same thing in V7, V8 and V9 WIP.
Start Split by any method, then click on Isocurve or type “i” so that “Select surface to split (Shrink-No)” appears.
Type “i” and
“Unknown command: i” appears.
Split started by typing “Split” on the command line.
Isocurve otion selected.
“i” typed.
That doesn’t even begin to describe the bugs in Split by Isocurve.
Split by Isocurve can only work on one surface. If you pre-select what you think is one surface but is not, you will find there is no Split by Isocurve function and Rhino will send you off on a wild goose chase. For instance, if your pre-selection accidentally includes a curve you will find Rhino, instead of allowing you to split the surface you selected, tells you there is no Isocurve option and sends you off looking for a “cutting object”. Or suppose you select what you think is one surface but is actually 2 surfaces that are joined, again Rhino wants to go do something different than what you requested.
The idea that the user is not allowed to Split by Isocurve a joined surface is an absurd limitation. If a user wants to split a joined surface by Isocurve the user has to first extract the surface make the split and then join it back. There is no possibility of Rhino doing that for the user due to the bugs in Split by Isocurve. As far as Rhino is concerned Split by Isocurve function does not even exist if your surfaces are joined.
