Gyro unreliable on Legion Go even with gyro sync enabled in HHD
When the gyro sync feature was first added to HHD beta a month or two ago, it effectively solved the problem, but I think the implementation must have changed later, because the current stable and beta HHD both exhibit unreliable gyro behaviour, even with the gyro sync option enabled.
It's better than without it, but every 20 seconds or so I still get randomly super high or super low sensitivity and it's difficult to play like this. Can it be reverted to the first fix?
57 Replies
steam broke it
Again? 😢
Seems to be beta only
Stable works
Cool, thanks, I will have a look
I am experiencing the same with stable. I updated Bazzite earlier today with
ujust update and my stable HHD version is now 3.13.5, it has this problem.
UI version is 3.3.6Is there a previous version that works?
Is there an easy way to install old versions?
Look here
I have not touched it since we did the previous fix
No you can rollback bazzite
Maybe it's the game you're playing
I have the problem on multiple games and it worked fine with beta HHD on my old Bazzite version.
Literally yesterday, with my old Bazzite, and yesterdays Beta HHD, it was fine
I haven’t upgraded Bazzite since February before doing it today morning
I will try to roll back to an older Bazzite and check with beta HHD, I think it will work
You mean yesterday with yesterday's steam client
Yes, but I found the problem, I had to do the gyro calibration again. So it was a problem with controller. I’m sorry, I should have tried that first.
But on that topic. The Legion Go controller gyros are VERY noisy, they always max out the second bar during Steam gyro calibration, and it can take like 20 retries until it gets past the first part of the calibration.
Do you know if there’s a way if higher-than-maximum noise tolerance could be set for Legion Go on the Steam level? I think the Steam tolerance doesn’t go high enough for the Go controllers.
No it wasn't
Just checked the beta
It's off you're tight
Oh okay, it just felt better after the calibration
Use the built in calibration
I did that too, and then the Steam one, it felt better after that
But then probably it was just an improvement, and at the end of the day it’s still off, if you see that they made changes
I don’t understand why Steam has to do breaking changes to their gyro stuff every month 😔
Yes, I played more and it’s still off after the calibration.
@antheas I'm a software developer so if you could point me to the Steam code that has changed, I can take a look at fixing it.
its compiled
its steam
so youre cooked
tld
r
steam stable still works
Alright thanks. So for people with a Go who needs gyro I guess Bazzite's done, we must wait for public SteamOS 3
Or at least stay on old version of Bazzite until then
I tested my ally
Man steam beta is broken I don't know what you want me to say
It breaks every two months
They keep changing it
I know, I'm not blaming anyone, really grateful for all the work you've done so far
Just frustrating that Valve keeps breaking this
With official release of Legion Go steam edition I guess Valve will be forced to properly support Go gyro all the time
It won't support the go anytime soon
Go s is different
😢
And no gyro doesnt work on steamos main either on the go s. Or didn't when I tried it
Maybe through fixing that garbage they broke us
Didn't work properly
Yes could be 😢
@antheas I've been doing further testing and I'm fairly sure gyro is now messed up on Stable and also on the old version where it used to work. Then I remembered, I updated the Legion Go controller firmware about a week ago. Since the old Steam version is also affected, it must be the firmware that is the culprit. There might be another, separate problem on Steam Beta that also affects your Ally, but I don't think I have the same problem.
Also, with gyro sync enabled, the problem is significantly helped, but not stopped.
I'm thinking that the new firmware update in the Go controller maybe changed the sampling rate of the gyro slightly.
Do you know of any way to check this?
I'm thinking that maybe the gyro sync setting has to be tweaked to the new sampling rate in case of Legion Go, if that really is the problem.
Worst case, I can do trial and error with different values in HHD when I will have time...
Well, I have a go
I have winblows
I can check it out
Although I experienced your symptom
With my ally
Tomorrow though
Thanks @antheas that would be great
This is my current controller firmware version
I noticed that on this new firmware version, if you trigger the controller calibration with holding L3 and L2 for 7 seconds, you do NOT get the flashing green and red circles anymore, which are supposed to be the gyro calibration signal
You do get them if you do gyro calibration in the Legion Space app though
So I'm feeling they messed around with gyro in this firmware update
Maybe changed the sampling rate too
Maybe the sampling rate is the issue
Although the go has a timestamp
To me it seems so far that since old Steam versions are also affected, to be a firmware update issue
And since the gyro sinc setting helps it, but doesn't complete eliminate it, that maybe the sampling rate slightly changed
But all this is just a guess basically
Annoyingly, there doesn't seem to be a way to downgrade controller firmware
I remember now how your gyro sync works. It filters out new inputs if the timestamp is the same as the last one, right?
Right now, it feels like the sensitivity is randomly jumping up and then down.
So I'm thinking maybe the pacing of the inputs is wrong now, rather than processing the same input twice.
It's like the input sometimes get pushed too close together, and other times they are spaced too far apart, when they should be evenly paced.
So still feels like it's somehow the sampling rate at the heart of it. But in a different way.
new firmware is the same
no, it only sends an output when there is a new gyro timestamp
essentially it clamps the output to the gyro
because if steam sees an output with the same timestamp it divides by zero
because it is amazing software
I’m seeing fucky gyro behavior with the new firmware on stable Steam on Bazzite
Maybe that’s what you meant lol
i just checked the old firmware
and it was funky
the new firmware reports look the same
I see, thanks for checking
I was really hoping it would be something fixable lol
maybe it is
🤞🙏
film a video because i understand nothing
What do you mean?
I don’t think you would be able to see anything on a video
It’s a very subtle effect that is not very obvious even in person, you just feel that something is off if you play for a few minutes
It’s very similar to how it was before your gyro sync fix
It’s just off
ok so i get the same
maybe it is our bug
dunno what happened there
there seems to be a slowdown
19
seems like a kernel bug?
like gyro is limited to 140hz now
over evdev
Nope unrelated 🐛 on the report tool
@antheas Could you check how the gyro feels for you on Windows? Best would be if you have Handheld Companion rather than Legion Space. Because on the latest firmware update, I get the same "off" feeling on Windows with HC. So I'm thinking Lenovo just fucked up the gyro with their latest fw...
HC has always been broken in windows
For steam input
If it's kind of broken it's because of valve
Because hc used to be completely unusable
Ah yes I know, I just use the regular HC feature that maps to mouse, it works outside of steam too, I don't think it has anything to do with steam input
Like so
This used to work very well in the past, around January and February
@antheas I found a way to make it a bit better. I enabled gyro in Legion Space, deceased sensitivity from 75 to 25, and then disabled it.
The sensitivity setting seems to be saved in the controller.
I now have to turn up sensitivity quite a bit in Steam to compensate, but the "fuckyness" seems much less pronounced now.
I'm thinking now that maybe they added gyro acceleration on the firmware level in the new fw.
You can try maybe, make the same amount of movement with the device, but first do it very slowly, then do it very rapidly. The movement output in the game will be different in both cases, but in theory acceleration should be zero.
The whole problem could be caused by forced acceleration if this is correct.
Definitely much better after lowering sensitivity in Legion Space.
@antheas Out of curiosity, have you had other reports or learned anything about this gyro change? For me it has been OK after turning down the sensitivity in Legion Space. I read from Windows Legion Space users that the new firmware update somehow "made gyro better" for them, so they probably did change something in the fw.
I'm not sure if this helps but I just put in a post for a gyro related issue. Maybe it leads to a fix with behavior from gyro capable controllers?
My issue seems to be a much more exacerbated form of yours, so maybe it will lead to a fix.
Thanks @Ziphon good to know others are reporting too
Seems like gyro is much less popular than one would think haha
ive been having that horrible fuckyness for a while now, no matter the distro, would you recommend i boot into windows and turn the sensitivity down as you have done JC?
I just want to play my BOTW and TOTK cartridge dumps 😭
Also can't play games like God of War very well since Dualsense controllers also use gyro
It worked for me. I wonder if @antheas muted this thread because I posted too much lol
(don't like the latency of Xbox controllers, can't react fast enough)
thanks a lot, ill give it a go
heh
a "Go"....get it
It's not perfect, mind. But it's a lot closer to how it was before the firmware update for me.
ive also found that for me, the gyro is always in ''continuous" mode. rather than "instant", not sure how to fix that
and unfortunately, this doesnt seem to have fixed my issues
Well if it's continuous then no wonder it's fucked unfortunately
Isn't there a toggle for that on the same screen as sensitivity, in Legion Space?
there is, i even tried setting it to continuous and back to instant, but no luck
ive also been having some bad issues with ghost inputs
I remember reading there is some way to factory reset the controllers, you could look into that
i just did a controller factory reset using the button combo
Then unfortunately I'm out of ideas
looooooool this is so wonky, in order to have UP input, i litterally have to throw the legion go over and behind by head