obsproject / obsproject/obs-studio
OBS rendering problem when dragging between two monitors if scaling is enabled on one of them.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
Other
Other OS
Nobara, Fedora
OBS Studio Version
29.1.1
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/RfLd6wUVldOBBslj
OBS Studio Crash Log URL
No response
Expected Behavior
I should be able to drag obs between my monitors without it's GUI rendering breaking.
Current Behavior
When I drag OBS from the display it was opened on to the other OBS's GUI rendering breaks:
Steps to Reproduce
This issue occurs on both GNOME Mutter in wayland as well as labwc (an openbox-like wayland compositor, similar to hyprland or sway). On GNOME you have to enable experimental fractional scaling https://www.omglinux.com/how-to-enable-fractional-scaling-fedora/ then in display settings set one monitor to something anywhere between 125-175% (not 100 or 200), on labwc you can use 'wdisplays' application to set a fractional scaling value (like 150% or 175%). I have not had this issue occur on any other applications except OBS.
Once fractional scaling is set, open OBS and try dragging it from one display to another.
Anything else we should know?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using OBS 29.1.1 on Nobara or Fedora with GNOME Mutter or labwc, fractional scaling enabled on one monitor, and the linked video and OBS log as references. Drag the OBS window between monitors and compare its rendering with the expected behavior; done means the GUI remains correctly rendered across the move.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100