Return to Level1Techs.com

Microsoft capture API bug, please vote to get this fixed!

While I am looking to have this issue fixed for Looking Glass, it actually affects any windows capture using Microsoft DXGI Desktop Duplication and has widespread ramifications across both recording and streaming software including OBS.

Please help me show Microsoft that this is important and needs fixing by voting on the below issue (Note: You must use the Windows 10 Feeback Hub App)

https://aka.ms/AA7a4d4

Here is this behavior profiled, the below log is showing the total frames per second, minimum time and maximum frame time in ms. The cursor information is completely ignored in this test.

This is while the cursor is idle

frame time cnt:   60 min: 13.42 max: 20.22
frame time cnt:   60 min: 12.65 max: 19.22
frame time cnt:   60 min: 13.78 max: 19.62
frame time cnt:   60 min: 13.23 max: 19.21
frame time cnt:   60 min: 13.71 max: 19.08
frame time cnt:   60 min: 13.66 max: 19.07
frame time cnt:   60 min: 13.64 max: 18.40
frame time cnt:   60 min: 14.49 max: 19.03

This is while the cursor is active/moving:

frame time cnt:   57 min: 13.85 max: 33.84
frame time cnt:   55 min: 14.64 max: 34.02
frame time cnt:   51 min: 13.70 max: 35.10
frame time cnt:   51 min: 14.96 max: 41.89
frame time cnt:   50 min: 14.69 max: 35.13
frame time cnt:   54 min: 14.50 max: 34.11
frame time cnt:   58 min: 11.39 max: 33.70
frame time cnt:   53 min: 5.96 max: 35.88
frame time cnt:   51 min: 13.64 max: 50.76
frame time cnt:   53 min: 14.73 max: 35.26
frame time cnt:   50 min: 14.89 max: 34.78
frame time cnt:   51 min: 12.96 max: 35.02

As can be seen, simple cursor movement can cause up to 10 frames dropper per second at 60FPS (imagine how bad it is at 144FPS or higher) which for an API devoted to capturing is completely unacceptable.

1 Like