obsproject / obsproject/obs-studio
Lots of constant screen tearing with full screen preview but not with windowed preview
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
Windows 11
Other OS
No response
OBS Studio Version
Other
OBS Studio Version (Other)
29.1.0
OBS Studio Log URL
https://github.com/obsproject/obs-studio/files/11669569/2023-06-02.23-02-14.gaming.PC.txt
OBS Studio Crash Log URL
No response
Expected Behavior
There should be no screen tearing and minimum latency to allow dual PC setups to stream properly.
Current Behavior
Lots of constant screen tearing with full screen preview but not with windowed preview.
Here I attached a video showing the behavior of the full screen preview VS the windowed preview. I also attached the logs from the OBS instance on my gaming PC as well as the logs from the OBS instance on my streaming PC.
In the video I used https://www.testufo.com/stutter to show the problem with display capture but I can assure you the result is the same in games with game capture.
Here is the video:
VIDEO
Here are the logs:
Gaming PC LOG
Streaming PC LOG
Steps to Reproduce
I use two PCs, one for gaming and one for streaming (with a capture card). The gaming PC does not clone/duplicate the display to the capture card, instead I configured the capture card as a second monitor (extended mode) and I use OBS preview to "copy" my main screen on the capture card. This configuration is used by a lot of streamers (see why in "Anything else we should know?").
You can use https://www.testufo.com/stutter to reproduce the problem with display capture or you can try a game with game capture, it will be the same.
If you don't have two PCs, I guess you should be able to reproduce the problem with two screens. Just use OBS to project whatever is on your main screen on your second screen and compare full screen preview (tearing) VS windowed preview (no tearing).
Anything else we should know?
Why using OBS on the gaming PC instead of just cloning/duplicating the screen? Here are a few reasons:
- no need to have a capture card with the same capabilities as the gaming monitor
- no screen tearing because of mismatched refresh rates (at least when it works properly...)
- better control of what is on stream via OBS scenes and sources
- no short black screen freeze when starting/closing full screen exclusive games
- no short black screen freeze when alt-tabbing in and out of full screen exclusive games
- color settings in NVCPL can be different
- no input lag related to unstable clone/duplicate mode
- DSR/DLDSR works properly while it does not work in clone/duplicate mode
- clone/duplicate implementation seem bad overall https://forums.blurbusters.com/viewtopic.php?f=10&t=6965
Could it be a Windows 11 bug? If I use AutoHotKey to turn the windowed full screen preview into full screen borderless mode by removing the window's borders and decorations and resizing it, it starts tearing as well. I read somewhere that Windows 11 treats any window which takes the entire screen space as full screen and force applies some "optimizations" to it. I did try to disable fullscreen optimizations on obs64.exe but it did not help though.
Could be a reoccurrence of #6936 or something else.
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
Start by reproducing the issue with OBS Studio's fullscreen and windowed previews on Windows 11, using the attached testufo.com/stutter scenario and the provided gaming and streaming logs. Compare fullscreen preview with a borderless window across two displays or a capture-card setup; done means fullscreen preview no longer tears while retaining minimum latency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100