obsproject / obsproject/obs-studio
Window Capture causes crosshair cursor in Noita to disappear
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
31.0.3
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/vnZtrqhFIBOv6OT4
OBS Studio Crash Log URL
No response
Expected Behavior
Cursor shouldn't disappear
Current Behavior
In-game cursor does not render
Steps to Reproduce
- Add Window Capture to your scene
- In Window Capture select any window (not necessarily Noita's window), so that it starts capturing something
- Start Noita and notice that cursor does not render (i assume this could happen with any game that uses a custom cursor, but Noita is the example)
- Delete Window Capture
- Notice that cursor is back
...
Anything else we should know?
Apparently, capturing any window in Windows causes custom cursors to break.
It's unknown whether the problem lies in OBS or in Windows's window capture system itself.
Contributor guide
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
Start by reproducing the Windows 11 behavior with OBS Studio 31.0.3 using the listed Window Capture steps, then inspect the supplied OBS Studio log. Compare Noita's cursor with and without an active Window Capture; done means the in-game custom cursor remains visible while Window Capture is active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100