You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlock the Twitch chat dock, or any other dock, and move it to another monitor, to allow for OBS to be on a third monitor without blocking my view of chat on the second monitor.
Current Behavior
OBS does not seem to handle 4K displays / high DPI scaling correctly. No issues prior when using 1440p displays, but now with 4K displays, text fields and other aspects of OBS are squished and hard to read. Resizing them does not help. The screenshot attached at the bottom of this report shows an example of what OBS looks like without overriding scaling. If I override the DPI scaling in Windows with the "System (Enhanced)" option, OBS looks as expected. However, this eventually leads to a crash.
After clicking to unlock the Twitch chat dock, nothing happens immediately. Once I click on the title bar and try to drag it, OBS pops up a window that is has crashed. Stream remains live until I click OK, at which point OBS closes, and the stream goes offline.
Steps to Reproduce
Using a 4K display, set to the default 150% or 300% scaling
Set the High DPI override in Windows to "System (Enhanced)"
Unlock a dock with the intention of moving it to another place on the same or other display
Clicking on the dock title bar and starting to move it will cause OBS to crash
The crash does not happen every time while offline, but it does happen to me whenever I am streaming (not sure why this is)
If I do not attempt to move a dock, OBS will run the entire time and not crash
...
Anything else we should know?
I have reproduced this with 2 different 4K monitor models, used in sets of 3, connected over combinations of DP/HDMI to my RTX 4080. All 3 monitors are set to the same resolution and DPI in Windows (150%). This was the default scaling for my current Acer XV272K V3 monitors, but my prior Philips 4K monitors defaulted to 300% in Windows and I changed them to 150%.
My screenshot is from the current Twitch Enhanced Beta build of OBS, but this also happened to me using the mainline build.
The text was updated successfully, but these errors were encountered:
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/SYXqOLTdz4TovGSX
OBS Studio Crash Log URL
https://obsproject.com/logs/h0m6NwBx2PkbvQvB
Expected Behavior
Unlock the Twitch chat dock, or any other dock, and move it to another monitor, to allow for OBS to be on a third monitor without blocking my view of chat on the second monitor.
Current Behavior
OBS does not seem to handle 4K displays / high DPI scaling correctly. No issues prior when using 1440p displays, but now with 4K displays, text fields and other aspects of OBS are squished and hard to read. Resizing them does not help. The screenshot attached at the bottom of this report shows an example of what OBS looks like without overriding scaling. If I override the DPI scaling in Windows with the "System (Enhanced)" option, OBS looks as expected. However, this eventually leads to a crash.
After clicking to unlock the Twitch chat dock, nothing happens immediately. Once I click on the title bar and try to drag it, OBS pops up a window that is has crashed. Stream remains live until I click OK, at which point OBS closes, and the stream goes offline.
Steps to Reproduce
...
Anything else we should know?
I have reproduced this with 2 different 4K monitor models, used in sets of 3, connected over combinations of DP/HDMI to my RTX 4080. All 3 monitors are set to the same resolution and DPI in Windows (150%). This was the default scaling for my current Acer XV272K V3 monitors, but my prior Philips 4K monitors defaulted to 300% in Windows and I changed them to 150%.
My screenshot is from the current Twitch Enhanced Beta build of OBS, but this also happened to me using the mainline build.
The text was updated successfully, but these errors were encountered: