Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Edit: I thought of a better way more succinct way to explain the above paragraph. I can say the only time any button, trigger analog etc. works in steam is during the binding process itself. Before and after, only A and B work, no matter how many times I do it or what I try to bind the buttons to... if that makes it more clear.
I'm really thinking about it, and I was having trouble with the elite paddles at the time and that's what had me tinkering in the settings. But I'm almost positive that the first time I Setup Input Devices, I set A and then B and then there's the option to "Skip with A" meaning skip the bind and I may have skipped the rest realizing this wasn't going to help me with the paddles. So I may have done this to myself.
I say that because if there's a bug it might be the skipping of binding buttons that triggered it. My assumption was that if I skipped a binding, it would stay as it was already bound... but I guess what could have happened is that I instead bound all of the rest of buttons to A and they are locked there somehow. Because I can't rebind anything now.
So if I were checking on the backend, I'd check:
that pressing A to skip a binding during that process is actually leaving the current binding.
that pressing A to skip a binding isn't unintentionally binding buttons to A.
that there is some measure or way to revert to default in the event someone dumb like me messes it up.
As its working for me now without the beta checked I'm hesitant to test further because I freaking love this new UI and don't want to break it again haha, but if I can help let me know.
then we know our own custom controller layout is being used and not the auto generated one created by Steam Input
Should i be trying to rely on newbigpictures controller layout ui? or is define layout from large mode still supposed to be functional too? Today the old one is FUBAR, though was working sweet as with 23rd Jan update after it being wonkly for months
all of these things seem broken in that newbigpicture uses differentr named controller layout configs compared to what large and oldbigpicture modews use - there seems to be conflicting or mismatching configs. Expected behaviour is Steam Input just to use the configs i tell something seems more hardcoded with newbigpicture
I think the new ui is not clear enough that new controller layout config is being made. We should be able to tell steam input which supported controller type we want to save that layout as too. Especially for controllers that support multiple modes or for third party licenced devices like PS type steering wheel used on pc. ref: https://github.com/ValveSoftware/steam-for-linux/issues/8293#issuecomment-1269535289
Additionally if "you skip a binding the assumption is that your controller doesn't have that control and so it's left unbound. " why is there no provision to add buttons that are missing?
Where is the "clear" button to leave everything unbound?
I appreciate that but, thats exactly what doesn't work. I've rebinded it multiple times activating it with the mouse, it always ends with just A and B working. I certainly must have tripped some kind of bug. That's why I was asking where the bindings were stored so maybe I could delete the file and revert it back to normal, because rebinding is definitely broken in the betas for me. Its as if its stuck on that first rebind indefinitely. Nothing I can do will change it.
It is pretty much broken for me too, as of today.
What controller type are you using?
For me MS Xbox One S controller (gen2 xboxone) and Thrsutmaster eSwap X Pro (gen3 xboxone) are working with more than A and B
Check controller.txt and controller_ui.txt log files. When i had controller locked to no input yesterday i could see some kind of lizard mode config was being told to load by Steam Input. Possibly because of the recently added
But yesterdays or todays hotfix fixed it. Desktop config now gets loaded like expecetd after exiting newbigpicture. Just exiting a game in newbigpicture is another scenario gamepad-navigation config maybe trying to load and steam input looses all input to controller.
I just saw this and, as a result, reinstalled the beta. Controller issue does seem to be fixed now, at least, my controller is once again working to navigate the Big Picture UI and working in game again.
I'm hesitant to test anything else right now, as its working, but if it stops I'll try these suggestions.
Xbox Elite Series 2, in terms of controller.
In terms of "Steam looses all input to the controller" on exiting a game, it does that to me too. But, at least in my case, it wasn't losing input, it was that the entire steam window (big picture) was somehow losing focus in windows when exiting games. All I had to do to fix it was to click steam with the mouse once to focus it. It isn't a perfect solution for a couch gamer like me, but I was thinking I'd write an AHK script to refocus steam after a while if the problem continued.
Thanks for the heads up!
Steam has so many options to configure controllers and play around with buttons and triggers yet iam not able to find any way to actualy input test the changes i made
for example iam tuning the left trigger of a controller to be more sensitive or vise versa there is no way to input test and actualy see how it would react.