When using vo=gpu and dragging the border to reduce window size,the drag-border moving with the cursor within the window is not displayed
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Environment
windows 10 1607 (14393.4225) 32bit
mpv latest
intel hd2500/4000 Drivers 15.33.53.5161 (10.18.10.5161)
intel j1900 integrated graphics card

C:\Program Files\mpv>mpv --vo=gpu "f:.Download\DIABLO 4 Rogue Gameplay Demo in 4K 60FPS.mp4"
[autoload] Prepending bigsur-colors.png
[autoload] Prepending aohYF.jpg
[autoload] Adding highlight-color-options-mac-os-x.png
(+) Video --vid=1 () (h264 854x480 30.000fps)
(+) Audio --aid=1 --alang=eng () (aac 2ch 44100Hz)
[vo/gpu/d3d11] Failed to create a DXGI 1.6 output interface: No such interface supported (0x80004002)
AO: [wasapi] 48000Hz stereo 2ch float
VO: [gpu] 854x480 yuv420p
AV: 00:00:09 / 00:11:17 (1%) A-V: 0.000
Exiting... (Quit)
When using vo=gpu and dragging the border to reduce the window size, the drag-border that is moving with the mouse cursor within the window is not displayed, only the mouse curosr is there.
However, if you press the print screen key to take a screenshot, the border does appear in the screenshot. So I can only describe it in words.
THX.
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
Reproduce the issue on Windows 10 with mpv --vo=gpu and the supplied video, focusing on the d3d11 failure and the missing border during window resizing. Trace the vo=gpu window-resize path and verify that the border is visible while dragging, including in normal display output rather than only screenshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100