Paul17041993
New Member
Desktop capture can only capture the cursor and only a single desktop frame, or otherwise just a blank frame. Similarly, window capture does not work in auto mode (BitBlt), only WGC works and you must manually set it to that for every window capture. Note also that capture cursor does not function on window capture, at all.
I've checked the logs with the discord bot, no problems are reported other than a few false-warnings.
There is however, one trick/hack I've discovered that gets desktop capture to work, and its to have an active window GCI capture just below display capture, and to then hide and unhide desktop capture and it will proceed to capture desktop frames correctly(?). But only so long as you perform this exact hack on every OBS start or when creating a new desktop capture.
I would hazard a guess that desktop capure is using BitBlit by default, of which nolonger functions in 20H2, thus it doesnt capture frames unless tricked into WGC mode.
This is not related to multi-GPU or admin permissions, don't ask.
I've checked the logs with the discord bot, no problems are reported other than a few false-warnings.
There is however, one trick/hack I've discovered that gets desktop capture to work, and its to have an active window GCI capture just below display capture, and to then hide and unhide desktop capture and it will proceed to capture desktop frames correctly(?). But only so long as you perform this exact hack on every OBS start or when creating a new desktop capture.
I would hazard a guess that desktop capure is using BitBlit by default, of which nolonger functions in 20H2, thus it doesnt capture frames unless tricked into WGC mode.
This is not related to multi-GPU or admin permissions, don't ask.