Thank you for reporting this — it's a clear and well-documented write-up. I was able to reproduce this on a MacBook M5 Max running macOS 26.3.1 (25D2128). I built a small test app that exercises both CGSetDisplayTransferByTable and CGSetDisplayTransferByFormula with several different gamma tables (identity, warm tint, inverted, red-only, gamma 1.8). On the M5 Max: Both APIs return kCGErrorSuccess Reading back the table with CGGetDisplayTransferByTable returns the correct values that were just set No visual change occurs on the display The same test app works correctly on an M5 (non-Max) machine running the same macOS build — all gamma changes are immediately visible on screen. This suggests the gamma tables are being stored correctly at the CoreGraphics level, but are not being applied to the display pipeline on M5 Max hardware. Tested on both built-in and external displays. I've related your two bugs (FB22273730 and FB22273782) together and attached the sample project I used to reproduce the problem to your
Topic:
Graphics & Games
SubTopic:
General
Tags: