But, the gyro data can be received when an overlay is open, like open the quick access menu. I don't know which one is bugged but I can't see why gyro data should be blocked.

The steam gyro settings is about whether to use gyro to emulate other behaviors; whereas we just want raw gyro data handled by that software, then feed to emulators, I guess?

No, I do agree with @kisak-valve take. None should block gyro data. What we actually want is an option to get raw gyro data. Not emulating anything at all. But None should still be an option to block gyro inputs.

I don't think this is a bug. Gyro data is recived in the overlay if the gyro is enabled for the default layout. Because game specific profiles only apply to the game not the overlay. Otherwise navigating the overlay is impossible if actions are mapped to keys for gameplay.

Why is this happening?
So many people have gyro to use DSU. This change will affect a lot. Why all of the sudden gyro set to none (which means no translation) suddenly turns gyro off? Please allow gyro to be set to gyro (seems obvious).

If the setting is for what the gyro emulates, wouldn't setting it to "None" indicate you want no emulation and just raw gyro, with a separate "Off" option to fully disable the gyro for that profile?

Yea, having to set the gyro emu to a random non-None value to be able to use raw gyro, doesn't make much sense to me.

Hello @KrisCris, I'm failing to see how this is a bug. You're getting exactly what you told Steam Input to do.

Closing in favor of #8804.

Closing in favor of an issue that's a year old with no responses, classy.

Wouldn't this also break any games that natively use gyro for aiming? Quake 2 Remaster for example