External display shows up as a new monitor, needs re-association

[draugvar]

Hi,
Sometimes, when I plug into to Mac book m1 pro the dock with the external monitor attached, It appears as the monitor was a brand new one:
In better dummy says "Philips (disconnected)" and a new "Philips" appear in the menu and I need to associate to the new one.

[waydabber]

Hi, if this is a DisplayLink dock, then this is the expected behavior on 1.0.10 as virtual displays (like DisplayLink) change their ID-s on every connection which interferes with association.

Please try the https://github.com/waydabber/BetterDummy/releases/tag/1.0.11-beta version and see if this fixes the issue.

Thank you!

[draugvar]

Yes, it seems that the Lenovo dock uses display link drivers. I will try the beta version asap. thanks

[draugvar]

Nope, same problem. Can I help somehow?

[waydabber]

You'll need to reassociate the display in v1.0.11 (the association made in v1.0.10 will not work).

[waydabber]

All right, I'll close this one, hopefully it works. Let me know if you still encountered any issues!

[T-Specht]

Hey, I have the same issue with a Dell S2721D monitor. Everything works great, but after reboot the previously associated monitor is "disconnected" and a new one with the same name is listed in the association menu. I am using version 1.0.12 (Build 1195).
Would it be possible to make the association via display name an option to select manually even though the screen is not virtual as described here #100 (comment)?
My "connection" is just an HDMI cable from my M1 Max MBP to the Monitor.

[waydabber]

Yes, I could make this an option. It is interesting that this happens, it should not be like this. I added an enhancement for this so it can come be implemented in a future version.

#211

[draugvar]

Yeah for me it's the same, and also when It come back from sleep monitor starts to flickering until close/reopen better dummy...

[waydabber]

I'll try to deal with this flickering problem in the future. Does this happen every time and is easily reproducible for you? Since I can't reproduce it, it is a bit difficult for me to understand the issue, but I might try changing the colorsync settings for the dummy and see if it changes things and give you beta builds, trying to find out what works. This would be useful if the issue is reliably reproducible in your setup, not something that happens infrequently.

[waydabber]

Yes, I could make this an option. It is interesting that this happens, it should not be like this. I added an enhancement for this so it can come be implemented in a future version.

#211

Please note that a setting for this was added in v1.0.13.

[T-Specht]

Yes, I could make this an option. It is interesting that this happens, it should not be like this. I added an enhancement for this so it can come be implemented in a future version.
#211

Please note that a setting for this was added in v1.0.13.

Thank you very much, I just got a chance to test it out and it works great!