Out of curiosity, I looked back at the previous topic that initially raised whether the behavior in question was a bug in MacRhino. More than 50 comments later, the conclusion is Yes.
While a good deal of information was shared about CPlanes, UPlanes, etc, given the amount of time and bandwidth involved, maybe this has also been a “learning opportunity” for us? Given the dominance of WinRhino users (knowledge, features, and experience), one humble suggestion might be for us all to be clear whether we are actually testing things in MacRhino, WinRhino, or both?
Bug diagnosis is not always easy stuff; however, that one detail might have significantly helped streamline this inquiry (and others in the future).
~Dave