Vanquish-
New Member
Hi everyone.
>>> First off: Sorry in advance if this topic is posted already, but I was unsuccessful in finding a thread addressing this issue.
In the latest stable release of OBS (v32.1.1), the names of the displays are no longer unique.
Previously, in older versions (ie: v20.1), the display names in the "Display Capture" configuration menu used to look like this:
In the latest version (ie: v32.1.1), the display names now look like this:
Because the new naming convention update allows two monitor names to look identical (ie: "ASUS VP249" before the colon symbol ":"), OBS is now unable to target the two independent monitors as unique displays while both are active. It will prioritize to one of them, and the other monitor is unable to be targeted.
This issue will only affect users with multi-monitor setups where they have 2 identical monitor / display models in use.
I rolled back to v20.1 and noticed this issue is not present in that version. I am currently experiencing this issue on v32.1.1.
I am unaware of which version in between these that the issue was introduced, but I believe I have provided enough information here to help bring attention to this issue.
Thanks in advance.
Vanquish-
>>> First off: Sorry in advance if this topic is posted already, but I was unsuccessful in finding a thread addressing this issue.
In the latest stable release of OBS (v32.1.1), the names of the displays are no longer unique.
Previously, in older versions (ie: v20.1), the display names in the "Display Capture" configuration menu used to look like this:
In the latest version (ie: v32.1.1), the display names now look like this:
Because the new naming convention update allows two monitor names to look identical (ie: "ASUS VP249" before the colon symbol ":"), OBS is now unable to target the two independent monitors as unique displays while both are active. It will prioritize to one of them, and the other monitor is unable to be targeted.
This issue will only affect users with multi-monitor setups where they have 2 identical monitor / display models in use.
I rolled back to v20.1 and noticed this issue is not present in that version. I am currently experiencing this issue on v32.1.1.
I am unaware of which version in between these that the issue was introduced, but I believe I have provided enough information here to help bring attention to this issue.
Thanks in advance.
Vanquish-