I start Rhinoceros 9 (office PC) with the settings before doing the reset.
From second 20 onward, I make the usual switch to show that the Z axis between perspective and isometric views is inverted.
At minute 1:09, I take the isometric viewport and move it to the left so that both views are visible (isometric and perspective).
At minute 1:30, I create a cube: as you can see, I start from the active isometric view with the Z axis pointing downward, so when I set a positive height value, the cube goes down.
At minute 2, when I switch to the active perspective viewport and create the cube, the height value goes upward along the Z axis, which is correct.
From minute 2:40, I start testing the CPlane command.
At minute 2:55, when I use “Set CPlane Z”, the camera automatically moves to a top view after executing the command. Is this supposed to be normal? It doesn’t make sense that it changes my camera view. I’m modifying the CPlane Z, not asking to change my point of view (I would expect this behavior from “Set CPlane to View”).
Even if this is considered normal, it still feels illogical. Also, if I’m in the active perspective view and use “Set CPlane by Z axis”, why does the change also affect the isometric view? Or vice versa? Shouldn’t it only affect the active viewport? The same thing happens again at minute 3:24.
Every time, I’m forced to open the viewport dropdown menu, go to “Set View”, and restore the isometric view. But who decided that when I set the axes (in this case the Z axis), I should see the camera aligned parallel to it? I’m modifying the axes from the isometric view, not the camera. Yet the camera changes anyway. There’s no clear logic behind this behavior.
Don’t tell me this is normal, because I don’t buy it.
Moving on.
At minute 3:58, in the active isometric viewport, I use “Set CPlane World Top”, and the camera resets itself. What’s the point of that? I’m telling it to modify the Z axis, and it moves the camera instead.
Then I have to go back to the dropdown menu, use “Set View”, and restore the isometric view again. It’s absurd.
Also, using that command in the isometric view flips the Z axis in the perspective view. That doesn’t make sense either.
From minute 4:35 onward, I test the other “CPlane World” commands (pressing F1 doesn’t provide any clear explanation of how these commands are supposed to work).
At minute 5:38, the point of view changes again (this always happens in the isometric view). After several tests, this is the difference I noticed:
– isometric viewport: using “Set CPlane World Top, Bottom, Left, etc.” changes both the view and the CPlane
– perspective viewport: using the same commands keeps the camera fixed and only changes the CPlane, which is the behavior I would expect
At minute 6:30, I go back to the isometric viewport and use the “normal” CPlane commands: I set the axes as I want, but the point of view still changes. It makes no sense.
So once again, I have to go back to the dropdown menu and restore the correct isometric view.
———
At minute 8, I perform a full reset.
From minute 8 onward, you can see how I’ve always customized Rhino: I split the viewports into two main groups.
On the left, I keep all orthographic views because I work with asymmetric objects and need quick view switching.
On the right, I place isometric and perspective views, so I can switch quickly without using the dropdown menu every time.
At minute 16, you can see that the Cartesian axes in both isometric and perspective views are correct and consistent with the gizmo in the lower-left corner.
From minute 30 onward, the recording continues, but I’m not at the workstation because I was called away.
I did the reset. I tested the CPlane World commands again and recorded another video with perspective on the right and isometric on the left. Now CPlane World works correctly, and the issue is gone.
Conclusion: it’s not that I suddenly forgot how to use this after years. The answers I received before were often superficial or presumptuous. I’ve always used CPlanes correctly. The issue was in Rhino, most likely a bug related to viewports and camera behavior with CPlane.
As usual, I ended up fixing it myself by experimenting. The only truly useful suggestion I got was: do a reset.
I had also opened a thread on the Italian forum to ask for help. This morning I received a suggestion while I was writing this reply. I tried following the user’s advice, and guess what—I discovered a new bug
Now I feel like crying. I’m going to grab a coffee.
The command doesn’t work. At this point I’d really like to hear someone else, because after years of using Rhino, having people keep explaining the CPlane to me without seeing that something is clearly wrong is getting frustrating. Have a good weekend.