No need for such drama, just buy a PC?
I reported this issue back in 2019 when I still ran Rhino 6 on my MacBook Pro (x86).
Wasn’t Rhino 6 back then still using OpenGL on macOS?
I’m not trying to be clever, I just find it astonishing that the same or at least similar bug happens with Rhino on Metal.
Most definitely different problems. Back in Rhino 6 it was more the integration code (written by me) that was to blame.
1 Like