Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The sensors are extremely sensitive. Can you check that you're placing the controller down on a _quiet_ surface. Things like washing machines or loud music, or people pacing around, restless-leg-syndrome can cause jolts large enough for calibration to be interrupted.
Also, feel free to add the exact steps you took to help me figure out the problem if this does not resolve it. Video is a great help!
if you type steam://open/console in your browser, it'll open the steam console.
Enter the CVar:
gyro_drift_calibration_debug 1
You should see a spew of what is causing the the progress to fail while auto calibration is running. You might want to be running an actual game while doing this, also, since the polling runs a little differently if no app is running or the calibration screen is not open.
It would be interesting to see what values you are seeing.
Here's an example of what you'll see if your "Auto calibration" is turned on for that controller:
Failed After 2 Samples: Gyro Check Failed: ( 3.208927 ) > ( 0.848317 )
Failed After 1 Samples: Gyro Check Failed: ( 3.673424 ) > ( 0.848317 )
Failed After 7 Samples: Gyro Check Failed: ( 0.897951 ) > ( 0.848317 )
Failed After 11 Samples: Gyro Check Failed: ( 1.135395 ) > ( 0.848317 )
Failed After 2 Samples: Gyro Check Failed: ( 0.979745 ) > ( 0.848317 )
Failed After 1 Samples: Gyro Check Failed: ( 2.617636 ) > ( 0.848317 )
Failed After 1 Samples: Gyro Check Failed: ( 6.701656 ) > ( 0.848317 )
Failed After 2 Samples: Accel Check Failed: ( 1.787613 ) > ( 1.641838 )
Failed After 114 Samples: Accel Check Failed: ( 1.648412 ) > ( 1.641838 )
Failed After 878 Samples: Accel Check Failed: ( 1.701122 ) > ( 1.641838 )
New Gyro Antidrift value found: ( -15.985352, -2.095703, 8.599609 ) given tolerances: G:0.719642, A:2.695632 Num Samples: 1024
Applied Gyroscope Drift Per Second: ( -15.985352, -2.095703, 8.599609 ).
New Candidate for Gyroscope Drift Per Second: ( -15.985352, -2.095703, 8.599609 ).
The "Failed" messages are when the sensors are too noisy for the controller to be considered stationary. You can see that they are affected by accelerometer or gyro. The values on the left are the "noise" per sensor. The values on the right are the tolerances of the bars in the UI.
When enough samples have been found the drift over that duration is .calculated
Note that ALL controllers will have some noise. The calibration system does not remove the noise. That's better dealt in your Game Controller Config: use smoothing and/or Movement Threshold to help reduce noise.
When ingame, it drifts upwards nonstop (only using Steam; aiming with a bow in BotW works flawlessly using Cemu) and the calibration doesn't ever finish.
I'll check what the console outputs soon.
Applied Gyroscope Drift Per Second: ( 146.000000, -75.333336, -25.333334 ).
Saving Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
Applied Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
Applied Gyroscope Drift Per Second: ( 146.000000, -75.333336, -25.333334 ).
Saving Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
Applied Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
Applied Gyroscope Drift Per Second: ( 146.000000, -75.333336, -25.333334 ).
Saving Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
Applied Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
Applied Gyroscope Drift Per Second: ( 0.000000, 0.000000, 0.000000 ).
I wish I'd knew where tf this drift is coming from and why it's only present in Steam.
- no more upwards gyro drifting
- gyro calibration finishes flawlessly
I can also say that the problem is not in the controller, since I use JoyShockMapper and it takes 1 second to calibrate the gyroscope and it works perfectly. Only it doesn't allow me to configure it via Steam Input which causes some problems in Steam games.
https://ibb.co/2M0dP57 - auto calibration turn on
https://ibb.co/Bs5FqN9 - auto calibration turn off
I also took screenshots of the values that I can see in the console. I tried setting different threshold values, but it doesn't affect anything.
I can build a house of cards and put the controller next to it during calibration and it won't fall over. But these values are in Steam, like I'm kicking the controller like a soccer ball.