Rhino8, M2, slow command response i.e. delete, extend, fillet, split,

Rhino Rhino for Mac
8

Thanks for trying that.

I lugged my LG UltraFine 5K display info the office today where I have a matching MacMini M2 Pro (Mac14,12):

Rhino 8 SR4 2024-2-13 (Rhino 8, 8.4.24044.15002, Git hash:master @ 5d3f86ffffae3c2ed84d21147c008b3907a40a2e)
License type: Not For Resale Lab, build 2024-02-13
License details: LAN Zoo Network Node

Apple macOS Version 14.3.1 (Build 23D60) (Physical RAM: 16GB)
Mac Model Identifier: Mac14,12
Language: en-US (MacOS default)
.NET 7.0.0

Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
  Apple M2 Pro
    LG UltraFine (2560 x 1440 @ 60.00Hz)

USB devices
  LG Electronlcs Inc.: LG UltraFine Display Camera
  LG Electronics Inc.: USB Controls
  LG Electronics Inc.: USB Audio

USB devices
  None

Bluetooth devices
  None

[...]

and, unfortunately, I could not reproduce the issue. That said, I do not have an additional secondary display that is close to yours.

Looking at EveryMac’s entry on Mac14,12, I’m noticing there are a lot of caveats to what it supports:

Alternately, this model can support “up to two displays” – one display with up to 6016x3384 (6K) resolution at 60 Hz over Thunderbolt and one external display with up to 3840x2160 (4K) resolution at 144 Hz over HDMI or one external display up to 7680x4320 (8K) at 60 Hz or 3840x2160 (4K) resolution at 240 Hz over HDMI.

I don’t fully understand why they callout the connectors here - Thunderbolt vs HDMI. You said you were connecting the LG via USB-C. That makes sense. Does your LG HDR 4K display support HMDI connections? It’s a long-shot, but if you have a spare laying around, you might try that.

I still find it odd that it works fine when you were recording. To me, this feels like it’s not by chance and that there is some sort of refresh rate throttling going on when that secondary display is being recorded.

I’m afraid I’m at a loss. Aside from trying the HMDI connection (which I admit is a long-shot), all I can think are other long-shots, like trying the next Service Release Candidate and/or updating to macOS 14.4, but those don’t seem implicated here.