Obs-studio: New window hook also capture cursor

Created on 18 Mar 2020  路  9Comments  路  Source: obsproject/obs-studio


Using new window capture, OBS captures also cursor without any option to disable it

Expected Behavior


OBS should capture window without cursor if there was an option to disable it

Current Behavior



OBS captures also cursor and there is no way to change that behaviour

Steps to Reproduce



  1. Set up a scene with a Window projector
  2. Select a window (my example: Microsoft Teams)
  3. Move your cursor onto window captured
  4. Cursors should be seen in preview panel

Additional information



Windows 10 20H1
OBS 25.0 stable
Dual monitor

Confirmed Windows

Most helpful comment

I agree. This should be open until it is resolved.

All 9 comments

Currently it is not possible to disable the cursor because Microsoft didn't add that feature yet. As of Windows 10 2004 it will be possible though and OBS will be updated accordingly.

He did say he was on 20H1, but the Windows SDK isn't officially released yet.

Currently it is not possible to disable the cursor because Microsoft didn't add that feature yet. As of Windows 10 2004 it will be possible though and OBS will be updated accordingly.

Shouldn't this be left open and closed when it's implemented?

I agree. This should be open until it is resolved.

My understanding is that the code on the OBS side already exists. It will start working as soon as the update is released from Microsoft.

The code is there, but we still need to build OBS with the new SDK, and do a release.

OBS Version 25.0.8 and Windows 10 2004 Build 19041, this still hasn't been resolved. Even if the captured windows is on a different virtual desktop, the mouse pointer is captured and relayed on the recording/stream.
Strange that the issue has been closed without a resolution. @derrod

Correct, "we still need to build OBS with the new SDK, and do a release" - this has not occurred yet, but soon.

Eagerly waiting 馃挴
Since the "build OBS with the new SDK" process hasn't been done yet, I'd suggest reopening the issue.

Was this page helpful?
0 / 5 - 0 ratings