DEV Community

Cover image for OBS 33 froze every controller overlay. The bug is three Windows input APIs deep
Crane Zhou
Crane Zhou

Posted on

OBS 33 froze every controller overlay. The bug is three Windows input APIs deep

On 23 October 2026 OBS Studio 33.0 shipped, and controller overlays stopped moving. Not one brand of overlay: all of them that run in a browser source. The pad on stream reacts while OBS is the window in front, freezes on its last input the moment you click into your game, and wakes up when you click back.

I build one of those overlays (ControllerOverlay), so I spent an evening reading the issue tracker to find out whether I had broken something. I hadn't. Nobody who makes an overlay had. The cause sits in how Chromium reads gamepads on Windows, and the history is a good lesson in what "the browser handles it" means.

A controller overlay over a game scene
What is supposed to happen: the pad in the corner follows your hands while the game has focus.

An overlay is a web page polling getGamepads()

A browser-source overlay is nothing exotic. OBS embeds Chromium (through CEF), loads a URL, and composites the page over your scene. The page runs a loop like this:

function frame() {
  const pad = navigator.getGamepads()[0];
  if (pad) draw(pad.buttons, pad.axes);
  requestAnimationFrame(frame);
}
Enter fullscreen mode Exit fullscreen mode

The page has no say in where those numbers come from. Chromium picks an operating-system API, reads the device, and fills in the array. On Windows it has had three ways of doing that, and they disagree about one thing: whether a program that is not in the foreground gets to see input.

Three fetchers, three focus rules

This is the table from the OBS maintainer's write-up in issue 14139, lightly reworded:

Chromium's fetcher Windows API Input while unfocused
XInputDataFetcherWin XInput Yes
WgiDataFetcherWin Windows.Gaming.Input No: "A Windows application must have focus to receive input from a controller."
GameInputDataFetcher GameInput No by default, but there is a focus policy you can set

An overlay needs exactly the behaviour in row one. The streamer is, by definition, focused on something else.

How we got here

Chrome 117. Chromium switched its default from XInput to Windows.Gaming.Input. In a normal browser this was barely noticed, because who polls a gamepad from a background tab? The people who noticed were streamers capturing a Chrome window. There is a Chromium issue about it; the answer was that the focus requirement is "imposed by the operating system and not something we can easily work around", and that a flag could switch XInput back on.

OBS 31.0. OBS updated its embedded Chromium from CEF 103 to CEF 127, crossed the 117 line, and overlays froze for the first time. OBS 31.0.2 fixed it by launching the browser with --disable-features=EnableWindowsGamingInputDataFetcher. That flag is the one you will still find in forum answers.

OBS 33.0. CEF went from 127 to 150. In that span Chromium had deleted XInputDataFetcherWin outright. The old flag now disables nothing useful, because the thing it fell back to is gone. Windows.Gaming.Input is the default again, GameInput is behind a flag, and Chromium sets no focus policy for it, so turning it on changes nothing.

The maintainer's summary of the situation in that issue includes a table flip. I think it's earned.

macOS broke in the same release for a different reason: a separate bug in that Chromium version, tracked in issue 14083. The maintainer reproduced it in plain cefclient at the same CEF build, which rules out OBS's own code, and found it fixed upstream in a later Chromium.

What an overlay can do about it

Nothing, from inside the page. I looked for a way and there isn't one, which is the part worth understanding if you write web code that runs inside someone else's shell:

  • getGamepads() returns stale data. It doesn't throw, the pad doesn't disconnect, and no event fires. From JavaScript, a frozen pad and a player who put the controller down look identical.
  • I know of no signal a page can trust for "the user's foreground window is something else". A browser source is rendered offscreen, and the page's own notion of focus describes OBS's embedded browser, not the desktop.
  • There is no second input path to fall back on. WebHID wants a user gesture and a device chooser, and an offscreen browser source offers neither.

So the honest engineering response is a status page. Gamepad Viewer, the oldest tool in this niche, put one up the day 33.0 shipped: "Nothing changed in GamePad Viewer, and nothing is wrong with your controller or your overlay link."

What users can do

Two workarounds have been published, both by people other than me, and I'll repeat them without pretending I verified each on every machine:

  1. Run OBS as administrator (Windows). Reported by a user in issue 14083 and confirmed as working on the maintainer's own Windows 10 machine, with the caveat that it does not work for everyone.
  2. Go back to OBS 32.2.2, the last release on CEF 127.

Adding the old --disable-features flag to your shortcut does nothing on 33.

The fix that is on its way

On 9 November the maintainer opened PR 14181, which moves OBS to a rebuilt CEF 150. Per the discussion, the plan for Windows was to patch Chromium to bring XInputDataFetcherWin back, and for macOS to backport the upstream fix. As I write this on 14 November the PR is open and the latest release is still 33.0.1, so check the releases page before you downgrade anything.

The longer-term note in the issue is the sobering one: XInput's fetcher will not be carried forever, GameInput's focus policy only helps on Windows 11, and Windows 10 users "will eventually be left in the dust".

What I took from it

Three things, for anyone shipping a page that lives inside another program:

Your runtime is whatever your host last upgraded to. I target "Chromium", but which Chromium is decided by OBS's release cycle, and a jump of 23 major versions arrived in one update.

Test the unfocused path on purpose. Every overlay demo is recorded with the overlay's window in front. The one state that matters in production is the one nobody looks at while developing.

Say what you have not tested. My own setup guide says we have not tested on OBS 33 and links the issue. That sentence is less satisfying to write than "works with OBS 33", and it is the only one of the two that was true.

If you want the non-technical version for a streamer friend, the short form is: your link is fine, your controller is fine, run OBS as administrator or wait for the next OBS update.

Top comments (0)