Configuration overrides might not be applied on Sonoma on display connect

[waydabber]

This seems to be a macOS bug. We can only hope for a fix by the time stable Sonoma comes out.

You can report this bug to Apple using the Feedback Assistant. Here is a sample error description:

---

With Sonoma display vendor/product specific configuration overrides located under /Library/Displays/Contents/Resources/Overrides are not applied consistently when connecting the display. The behavior was observed in various M1 and M2 devices.

Steps to reproduce:

• Copy a properly formatted display override directory and file to the .../Overrides folder or create one using apps like betterdisplay.pro.
• Disconnect/reconnect the display or reboot the Mac
• Observe the display override take action (for example added custom resolutions appearing in the resolution list etc).
• Disconnect/reconnect the display. The override is not working. A reboot solves the problem.

The issue is not observable on the same Mac running Ventura.

[waydabber]

Note: this issue affects the smooth scaling feature, custom resolutions, default and native resolution override, display name and type overrides.

[waydabber]

Also: #2218

[waydabber]

The root cause is now found, implemented a proper workaround in v2.0.10

[sarnason]

Fantastic. Are there builds available?

[waydabber]

@sarnason - do you have this issue? Can you check this build and report back whether it works properly?

https://github.com/waydabber/BetterDisplay/files/12690650/BetterDisplay-v2.0.10-b24461.zip

[waydabber]

Unfortunately the fix is not 100% according to my tests - there are times when Sonoma does not properly load the configuration no matter what, even if the app is not running at all, and I can't do anything about that. I identified some extra triggering factors and tried to avoid them when the app is running + added an extra option to force-reinitialize the display on configuration if things don't seem fine - this workaround (as it is a rather clumsy solution and might cause other complications) should be turned off only if without it there are recurring issues even with the updated build: