Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Hozzászólási szabályok és irányelvek
Hozzászólás jelentése
I had a kind of similar problem, but with a ps4 dualshock controller.
I just fixed it and it works now.
What I did was: steam -> settings -> controller -> general controller settings -> TURN OFF the playstation support -> TURN ON the generic gamepad support. If all goes well you should be able to use the controller without it inputting inputs that registers the controller as a keyboard, and it should also still work for emulators.
This fixed my problem. Not sure if this also works for other controllers like your switch pro, but I thought this could mayby help. Let me know if it works or not
So far, I've also learned that these days, third party clients are sometimes unavoidable, and that's an issue. It wouldn't be an issue though, if the controller function wasn't designed to work with the first thing that launches. It can be enabled when the game properly launches, but hitches happen and it forces me to restart.
The problem is, the industry decided that even if you don't have the game on Steam, they force you to use the client anyway. That's a whole discussion for another time, but it conflicts with the way the controller function works in Steam especially when the games don't have native controller support.
Games > "Add Non-Steam Game to My Library"
However, I don't think this works with stuff like Origin or Twitch Games
When you do that, your controller will work fine, but only for games launched through Steam. Your controller will do nothing in other programs while Steam is running. No key pressing or mouse movement, but also no playing with the controller in non-Steam programs. If I closed Steam, they would all work fine. But I didn't want to have to do that constantly.
So adding the non-Steam programs to Steam solved that problem for me.
As it so happens, there's already a type a bug which also fails to kick in, which shouldn't happen if you already had it added in in the first place.
What happens on the client is that the desktop configuration is configured by default. It basically can't really be turned off unless you turn off the controller option. Then everything is turned off, and you're not really solving anything because it negates the purpose. You can also turn that off if you need to, but also still avoid the desktop config from running and play as normal.
Whenever you launch something from Steam, the desktop config is disabled in the interim, so that the individual config is kicked in. You can only make that work if it's already added to your library, non-Steam game or not. If it's not assigned in your library, it doesn't kick in.
The particular bug I was referring to earlier was the part where you should actually have it in your library and configuration set. It should kick in, but it fails to. It did that to me in the middle of a game and subsequent launches, so none of the "solutions" actually made sense.
https://www.reddit.com/r/AlienwareAlpha/comments/52cwy9/psahow_to_fix_your_controller_from_acting_like_a/
1. Go to control panel, then go to Mouse. Click the hardware tab and you should see two of "HID-compliant mouse", find the one that has it's location set as AlphaMouse, then go to properties and disable the device....there is another step but I didnt have to do it.
Dude, you must have forgotten what this thread was about. Read the OP
The problem was that Steam gives keyboard and mouse control to the controller when on the desktop. Which is super annoying. Especially when you want to alt-tab when a Game is running. I wanted to rebind the controls to treat it just as a controller, but that wasn't an option.
So the SOLUTION was to unbind everything in the Steam Desktop Config. But this means while Steam is running, no other app can use the controller. Stuff like VisualBoyAdvance. Or any number of old PC games that don't need Steam to run.
So this created ANOTHER problem. But the solution to this was to add those non-Steam programs to Steam. PROBLEM SOLVED.
.
.
.
The problem is solved. At least for me. Albeit in a bit of a janky way.
You don't need to "unbind" everything in the desktop config. Controller support uses two separate functions: desktop and games. Only one of them is used at a time when properly kicked in.
The desktop config is the primary global config used when Steam is run with controller support enabled. That is typically used for using your computer; the BPM version is similar, used to navigate within the UI.
Games (either Steam or non-Steam) can be individually configured to have binds or no binds for as long as the controller uses the appropriate input the game can use. When any game is launched through Steam, the game's controller config should be kicking in, nixing the desktop config.
The problems began when the game config failed to enable upon launch. It's even happened in the middle of playing. Whatever the cause, you end up being reverted to the desktop config or so, since the game one bugged out.
Since not all games have controller support, especially the ones you add as non-Steam games, this situation causes quite an inconvenience. But no matter what, if you didn't add the game on Steam, in at least as a non-Steam game, you wouldn't actually be using the individualized controller support that you should've had the whole time. It just doesn't work that way. The inconvenience of having that feature malfunctioning though is primarily what this issue is about, and that just makes advertising "adding it as a non-Steam game" as a "solution" moot. It shouldn't be janky either.
The OP wanted a way to disable the default desktop configuration. And now I have it.
That's true. Actually, now the best way is to do this:
Steam > Settings > Controller > Desktop Configuration > Browse Configs > Templates > Gamepad
Works like a charm
I don't need to use the Steam Controller support to set my keybinds in my 3rd party programs. I just use the keybind options within those programs. I don't even need to mess with the Big Picture stuff.
That would have been obvious where the desktop config would fail to function as well. Our issue was that the config for games individually stop functioning where the client would normally work. It has nothing to do with connectivity. It's a software issue in the client itself. You're misusing the function in the client as a workaround where it's not actually doing what you think it is supposed to do.
That's only how you set up the desktop config. I just explained that's a totally different thing from game configs that are assigned per game. Game configs are what you were looking for to enable the controller to work in game. When it stops working, you're defaulting to the desktop config so you don't get the responses you already assigned to the game.
When you're using third party programs, you're unaffected by the issue the rest of us are having with the Steam client, and you're not addressing the issues with the client itself. You're bringing up a external workaround instead of figuring what the solution is internally in the first place.
Exactly! That's what I said! Get your own damn thread! This is mine. For A SPECIFIC problem I was having! And it's already solved. Stop trying to hijack it. You'll only confuse people and get 0 answers to your own problem.
First of all, I know what the issue is, because I've had the same experience. This is not even hijacking to put that information out there. You're misusing the client based on what you were trying to do, and you're missing the point of this thread; no amount of the fact that you started this thread ever makes you arbiter of how Steam works.
The problem you had was because your game config stopped launching. That's why you had the desktop config kick in and why you thought somehow kbm response was being injected into it. That's the whole issue. Although you wanted to switch the desktop config to use a gamepad only template, the reason I said that was not an actual solution is the fact that your game didn't launch with the gamepad config you had setup with it in the first place! So if you needed to fine-tune the config individually to a game to reduce the strain on your controller and playing experience, you couldn't use it because you were only accessing the desktop config the whole time. That's why that will not actually work, especially for other people.
Thus, as I was saying, your "solution" wasn't actually addressing the root problem.
So, when I said "that's a totally different thing", you completely dismissed the previous sentence and twisted my words for your benefit to be a stubborn, arrogant, condescending jerk. I was describing the fact that your so called solution was in fact not addressing the universal problem. Way to miss the point!