Sometimes I can’t tell with a new version whether I’ve found a bug, or just a… new way to work. This seems buggy to me.
When I restore a Named Cplane, the resulting cplane seems to depend upon the View setting.
So if I’m in Top View, I’ll get a different cplane than if I’m in Front View.
Named Views seem to be working as expected, so I’m using those now instead.
Hello- - can you please post a file that shows this - can you also make sure Auto CPlane is not enabled when you test- just in case.
-Pascal
Named Cplanes.3dm (286.0 KB)
Hello- this is the plane that is called Front Pull - it does not corrspond to the ‘Pull’ planar surface - is that what you expect?
-Pascal
No, but it works correctly when I’m in Front View. Try restoring the user-created named cplanes in both top and front view, and see if you get different results.
Hello- it seems consistent here.
-Pascal
Hi @hanscad,
You just linked this old topic from Named CPlanes disfunctional? - #7 by hanscad so I took a look.
I noticed that your views are set to cplane top, cplane front etc. which made me wonder whether you had been setting views in between trying to work with your three named cplanes. If so, you may have been changing the CPlane each time you set the view. If you have ‘Named views set CPlane’ turned on, try turning it off and see if you get more expected behaviour.
I found, like Pascal a year back, that your Named CPlanes behaved consistently. I had that setting turned off. When I turned it on and changed views things became much harder to follow (but were happening as expected once you understand the effect of that setting).
HTH
Jeremy
Hi @jeremy5, thanks for looking into this!
I already had Named views set CPlane turned off. But now I found this advanced option Rhino.Options.ModelAid.AutoCPlaneAlignment. Changing the value to 0 seems to be fixing it for my particular Cplane issue. It’s unclear what the difference is between the first three settings tbh:
I’m also seeing this Construction Planes setting, and it seems like it must be related too. Standard makes Named Cplanes work as I imagine it should, and Universal brings the original issue back:
That setting is where the Auto CPlane alignment selected in the GUI is stored. You access it by right clicking here:
In my limited experiments I haven’t seen a difference between 0 and 1, but 2 is weird and, I confess, I can’t see any use for it. I leave mine set at 0.
Note the Lock and Sticky settings here too. I think these can also be a trap for the unwary.
But you can read up about them in the Help here: CPlane | Rhino 3-D modeling
You can, of course, also turn Auto Cplane off by unhighlighting the button.
Standard means that the CPlanes in each viewport are independent of one another. Universal means that if you set a CPlane in one viewport then it gets set in the others too. I find this is only rarely helpful, and to some extent it is superceded by the Auto CPlane features.
I guess you didn’t see that part of the reply at the time?
-wim
Auto Cplanes and Universal Cplanes are not related.
Universal Cplanes links the Cplanes in all viewports. When a Cplane is changed in one view the Cplanes in the other views also change based on the direction of the view in each viewport. If the Cplane in one viewport is changed to a named Cplane and Universal Cplanes are on then the Cplanes in the other viewports will change.
Universal Cplanes can be turned on and off in Options
There are three Auto Cplane settings, I got two out of three.
But if I’m not using Auto Cplane, should this still affect my Named Cplanes?
Nope
