microsoft / microsoft/Windows-classic-samples
BUG: DisplayCoreCustomCompositor tearing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
3 displays (1080p, 1080p, 2160p) connected to GPU, custom EDID flashed to ports as Special purpose display.
At the beginning it goes normal. But after GPU is highly loaded with third party software (like Furmark) for a few seconds, tearing appears on a 4K display. GPU is not loaded anymore.
Sample changed in few places:
changed final delay seconds to infinity
added check not only for HMD but for Special purpose too
OS: Windows 10 Pro
CPU: Ryzen 7 5800X
GPU: NVIDIA Quadro RTX 4000
Contributor guide
No contributing guide indexed for this repository
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
Locate the DisplayCoreCustomCompositor sample and first reproduce the reported behavior with three displays, the stated GPU, Windows 10, and Furmark load. Compare the sample changes described in the issue, then determine what evidence is needed to confirm that tearing no longer appears on the 4K display after GPU load ends.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100