![]() I'd suggest we set WGC as the default method for all captures, as I don't see why it shouldn't be. It is highly likely #4140 will fix the issue, as WGC capture works without any issues. The cursor again however, is still captured in this mode, making for almost identical behaviour. Steps to ReproduceīitBlt mode on all other capture methods also does not function, in this case not even hover events can trigger new frames. The display capture will then continue to work as it should so long as that window capture is still valid, though it may continue to work afterwards, so long as it isn't hidden. The cursor hovering over window elements can trigger new frame updates, but not always, and only for that one frame per element.Įlement render misses are mostly avoided when set to fractional FPS, to the display's exact FPS (144/1), but continued capture still does not happen.Ī trick workaround that forces consistent frame capture is to have a window capture source hidden behind the display capture (ie above it in the list), hide the display capture and unhide it. Often shows as a black display, or frozen display. GPU: RX 5700XT drivers 20.11+ (20.11.2, 20.11.3, 21.1.1 tested, consistent behaviour)ĭisplay: AOC U34G2G4R3, displayport 1.4, 3440x1440 144Hz 10bpc Expected Behaviourĭisplay capture to capture frames, and at the required framerate Current BehaviourĬursor is captured, display frames are not, or not consistently. Which part do you need me to re-explain? display capture isn't capturing frames, in admin mode. No, this is not a laptop, nor are there multiple GPUs present at this time. 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. But only so long as you perform this exact hack on every OBS start or when creating a new desktop capture. 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(?). I've checked the logs with the discord bot, no problems are reported other than a few false-warnings. Note also that capture cursor does not function on window capture, at all. 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. ![]() The report is as follows ĭesktop capture can only capture the cursor and only a single desktop frame, or otherwise just a blank frame. I reported it back at the start of january on the forums however it was never touched on. Operating system and version: Windows 10 20H2 19042.746 120.2212.551.0ĭisplay capture currently doesn't work correctly, either with modern AMD drivers, the 5700XT, a 3440x1440 144Hz display, or with the latest public builds of windows, I haven't been able to determine which of the ones it is.
0 Comments
Leave a Reply. |