Wireframe displays random pointy objects that aren't there

Something really weird happens to my wireframe displays. I am not 100% sure how to reproduce it because it doesn’t go the same way every time and doesn’t go away again (even after reverting the file to last opened, restarting Rhino or my MacBook).

The best I can do to describe is
Open the file > enable the clipping plane in top view (already weird things happen with curves in top view) > set the display mode to “Pen_IV” in top view -> all other (wireframe views go wild).

It happened for the first time after the latest update. I am assuming it has something to do with the clipping plane and the custom pen display mode I was using when it came up.

Sorry for the bad description but I really have no idea what I’ve done to cause this. Has anyone ever even seen anything like it?

It makes Rhino unusable so I would prefer to go back to the latest working version in the meantime. Could you please provide a download link?

Rhino Version 6 (6.20.19323.01022, 2019-11-19)
MacOS Catalina 10.15.1 (19B88)
MacBook Pro (Retina, 15’, Mitte 2015)
GPU Intel Iris Pro 1536 MB

Pen_IV.ini (5.8 KB)
Preferences_20191120.plist (428.4 KB)
PVZH-PW1-Ergonomie-20191121.3dm (5.4 MB)

Hi - I can see something similar with your file on my system but I’m not completely sure if this is the same issue. 1) I don’t need to use any special display mode - just using factory-default wireframe also shows this; 2) going back to 6.18, I can still see this happening.

Which version were you running before updating to 6.20?

Note: apparently several other users have reported something similar - this is logged as RH-54879 but this report is not open to the public.
-wim

Hey wim, thanks for your reply and sorry for not reporting back. I am not sure about the version I was using before, maybe it has to do with the way the file is set up after all. It’s just I never experienced this type of display error until the last update – anyway, good to hear that it is being worked on. Meanwhile I’ve worked around the issue by not using the clipping plane. Thanks anyways

Hi - apparently it’s hard to find computers that we can reproduce this issue on. Could you run SystemInfo and attach the result here? Perhaps we have a machine somewhere on the US West Coast that resembles yours.
-wim