Changing Configuration Override options affects several displays simultaneously #2797
-
I've got two displays of the same manufacturer and model (LG 29WP60G-B). While changing any option from Configuration Override/System configuration... group on one of them, same option on the other one is changed at the same time and getting the same value (toggles, display name). It seems like their options are unexpectedly synchronised. BetterDisplay reports different id values for them (serial, UUID, CGDirectDisplayID) except vendor and model. There is no other issues/conflicts with configuration except this one. Do you need any extra information? Affected version: 1.4.15 Build 15141 and 2.2.6 Build 27335. output.mp4output.mp4 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi there - yes, System configuration override works on a per vendor/model number basis (as it is noted under the small print for the "Edit the system configuration of this display" option), therefore this is the expected. You can rename the display in-app for differentiation but not system-wise. A solution might be to apply an EDID override to one of the displays (provided you are using Apple Silicon - on Intel the EDID override is also vendor/model based). App versions v1.4.x don't auto-update to v2.x (they are actually different applications with differing bundle IDs + not all macOS versions supported by v1.4.x is supported by v2.x. I might add one last v1.4.x update to inform users with eligible OS version about the upgrade. |
Beta Was this translation helpful? Give feedback.
Hi there - yes, System configuration override works on a per vendor/model number basis (as it is noted under the small print for the "Edit the system configuration of this display" option), therefore this is the expected. You can rename the display in-app for differentiation but not system-wise. A solution might be to apply an EDID override to one of the displays (provided you are using Apple Silicon - on Intel the EDID override is also vendor/model based).
App versions v1.4.x don't auto-update to v2.x (they are actually different applications with differing bundle IDs + not all macOS versions supported by v1.4.x is supported by v2.x. I might add one last v1.4.x update to inform users wit…