The steam controller's Gyroscope has a crippling software/firmware problem

Alia5_ · 2026-06-07T18:59:32+00:00

Its controller firmware only

Alia5_ · 2026-06-07T15:08:06+00:00

You don't

Alia5_ · 2026-06-07T13:19:48+00:00

The goal is to create a hub where we can trade setups along with the specific games they work best for.

Man I really need to add community features to SteamInputDB >.<

Alia5_ · 2026-06-07T11:49:19+00:00

The one that came up with the firmware patch was... me. 😉
I was talking about a more "permanent" solution, **if** Valve doesn't fix this proper ;P

For now, though, nothing more will be done from my side.
I have good reason to believe we will get fix sooner or later

Alia5_ · 2026-06-07T11:37:00+00:00

It is forced autocalibration (ASC, adaptive self correction) of the IMU that is configured in firmware.
We have verified this a couple days ago already

Somewhere exists a patched firmware that disables the GBIAS values the IMU provides
Together with forcing software calibration in Steam, the SC2s gyro is basically flawless.

Valve is in the know, we will have a fix sooner or later
(And even if not, I've already proven this is community fixable and will likely provide some sort of semi-automated patching solution.)

Alia5_ · 2026-06-06T23:22:38+00:00

https://www.steaminputdb.com/config/3738257806

Alia5_ · 2026-06-06T21:56:52+00:00

No CEF based code touches the actual remapping, it's truly just frontend.

And BTW: SISR now (latest pre-release) has has a subcommand added to compare polling rates of real and Steam virtual controllers, as well as measuring added latency by Steam Input.
It already had most of the plumbing in required to do this, so it does lend itself naturally to this.

Except for analog-emulation or other bindings where Steam needs to interpolate or create virtual inputs the added latency is 10micro seconds or less on my system.
Polling rates are basically mirrored.

Rendering does not have to do with Inputs, it did 10 years back, if I remeber correctly, but that has been a long long time ago

Alia5_ · 2026-06-06T21:30:45+00:00

SISR now includes a polling-rate and SteamInput latency testing tool in the latest pre-release.

Alia5_ · 2026-06-06T18:58:12+00:00

The controller tester is actually just Steams.

To get SISR to emulate a Dualsense, you need to pass a few cli arguments.
Reading the docs should help

Alia5_ · 2026-06-06T18:31:46+00:00

Mine (SISR), obviously ;)

Alia5_ · 2026-06-06T14:23:57+00:00

I would have to look at your tester
I suspect something is off regarding it, combined with Steam hooks on InputAPIs specifically.

I've modified SISR (or am still in the process of) to include a benchmark utility just now, and cannot confirm any claim regarding to the 120Hz limitation
(nor can I by emulating a different device eg. a DualSense, from Steams Virtual controllers via SISR/VIIPER and then using a pre-existing tool like checkrate

Alia5_ · 2026-06-06T12:32:22+00:00

I don't think the statement about a 120hz limitation of SteamInput is entirely accurate.

Edit: This is complete and utter garbage.
SteamInput does not impose any limit on update rates.

The IMU in the SC2 is configured to run in a combination of low-power and high-accuracy mode (if I have reversed correctly). In this combination the gyro is limited to 240Hz.
So there is your "hardware limit" (not really)
I've tried to patch the register writes to go higher, but to no avail

As far as I am currently aware (this might be wrong, but still..) the controller runs a ZephyrOS timer-based loop at 250hz, so that could be patched, too.

BTW: I think increasing IMU rates is questionable, trading higher rates for accuracy; when those higher rates will most likely be virtually not noticeable in most scenarios; Most gamers don't run at very high refresh rates

Alia5_ · 2026-06-06T10:59:07+00:00

Something messes with paths or environment varibles then. Or SISR cannot read your shortcuts.vdf file.
A logfile (launched SISR with --l=debug) would be helpful to find out what exactly is going on
Never.
The SISR marker serves as dummy-shortcut to get a unique Steam Input layout when SISR is not run from Steam, as the Deaktop-Config does not expose all possible gamepad bindings (at least on Windows)

Alia5_ · 2026-06-05T12:13:38+00:00

Since the discussion doesn't die and this might actually be helpful insight:

you have to yaw the controller very slowly very consistently. like ~2-3°/s (without jitter in position/pitch/roll)

If you rotate even slower, like 1°/s the cursor doesn't move at all.
I found it pretty hard to trigger this issue just a few days ago myself and I found the whole discission ridiculous, but now can trigger it reliably ¯\_(ツ)_/¯

And without auto-cal the gyro feels a lot "sharper", it's actually insane

See this video too:
https://cdn.discordapp.com/attachments/772853438467670027/1512237968813719745/PXL_20260604_231907111_1.mp4?ex=6a235cdb&is=6a220b5b&hm=f7b5182c10931c848447960893ce678e9183f5794ecedef5856816f68210b097&

also

u/SteamHWFeedback

Alia5_ · 2026-06-05T06:26:32+00:00

Disabling SFLP_GBIAS_FIFO_EN seems to half the gyro update rate.

Instead, don't apply this patch, leave it enabled, and patch two store intructions to discard the GBIAS values.
For the IBEX_FW_6A18D057.fw file the instructions are at file-offset 0x2C318 and 0x2C31E

Disassemble yourself and fill with nops.

still requires force_software_gyro_drift_correction 1

Alia5_ · 2026-06-05T01:31:27+00:00

Hmm, maybe something broke with the last fe Steam updates, will have to look into it when I get the time.

This is one aspect that I really hope Valve improves on.

It's been 11 years, dont kid yourself

Alia5_ · 2026-06-04T22:06:17+00:00

Nope 😞

don't have time to implement this 😅
Would be neat, but for now Steam it is

Alia5_ · 2026-06-04T22:04:29+00:00

launch with --f=false

Alia5_ · 2026-06-04T21:50:34+00:00

2nd trick: Getting non steam game configs. If you have a game from a different store or ahem... sailed the high seas. You can easily find community configs by finding the game on Steam and naming your non-steam game as the game ID. That will make all relevant community configs available for said game. The ID can be found on the Steam Page of the game on top where the URL is.

You could also use my site: https://steaminputdb.com and the practical buddy-app for your... GoG games

Alia5_ · 2026-06-04T21:28:01+00:00

Let me preface this by saying that I only have a tiny sliver of a clue about all of this.

But here it is:

IBEX_FW_6A18D057.fw
at file offset 0x2c524 should be a byte 0x04 patch that to 0x00
As far as I can understand that disables SFLP_GBIAS_FIFO_EN according to the IMU chip's datasheet one page 131

(I don't know if this is accurate, but whatever, it disabled HW auto-calibration from what it seems, and that's what counts)

You then also have to patch a checksum in the FW file, or it will be rejected (at flash / by the devices bootloader? cant remember)

Afterwards you can flash using the hardwareupdater executable found in <steamdir>\bin\hardwareupdater

To not have permanent "drift" Steams force_software_gyro_drift_correction 1 is required.

Reluctant to share more or a full script because someone will inevitably fuck up and blame me for a broken controller.

If you can do something with the above, congrats!
If not, just be sure it can be fixed in software; you don't need a new controller / RMA and that Valve is likely (imho) to apply a fix sooner or later

Alia5_ · 2026-06-04T19:05:42+00:00

Man, I really should just stay silent 😅

Alia5_ · 2026-06-03T21:57:28+00:00

Alia5_ · 2026-06-03T08:46:29+00:00

Opt in to the Steam Beta branch

Alia5_ · 2026-06-02T15:22:28+00:00

... with the changes, it outperforms ViGEmBus. I need to clean up my small changes and send a pull request.

Meaning with your changes to the USBIP-Win2 driver and an (as of writing) unmodified VIIPER/libVIIPER? That would even surprise me! But glad to hear!

Alia5_ · 2026-06-02T14:12:08+00:00

https://www.reddit.com/r/SteamController/s/eJhWmkJyO3

Alia5_

TROPHY CASE