Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
I usually don't use controllers, so I have very little other advise in that regard, but maybe it helps.
but i tried it already when realizing there was no easy way to disable the control ingame
it's not a major issue
still kinda wondering why you cannot simply disable the pad in the options menu..ah well.
to go library panel, right-click on CY2077, pick Properties, Controller, then Override for Cy2077, and then disable steam controller input.
did that right as my first move
does literaly nothing
not just do the commands still flicker, but also i can/could still use the pad just like nothing ever happend.
@Bogmore i realy don't want to plug'n unplug. i play 99% of the games only with M/K, while my better half pretty much only plays with pads; i like my rig...and it's ports.
again it's not some major issue. i thought maybe there was a command line you could ad to the steam startup menu, but alas as far as i can tell (web search) there ain't.
If you buy an extension USB lead, type A male to female then you are not unplugging from your machine but the female end of the extension, they are cheap and will save wear and tear on your machine USBs.
PS4 controller (Micro USB) to USB A leads are cheap too, but I seem to get that type with just about everything I buy. I must have 5-6 in the lead drawer.
You could try blanking it out, fresh controller install as it were... wherever your steam is installed, underneath config will be a config.vdf , so maybe it's C:\Program Files\Steam\config\config.vdf... if you edit this file it's xml-ish, search for a key SDL_GamepadBind, and as it's value it'll have a long string with your controller by name, platform, all your mappings, etc. (it'll look obvious, like layouts look like ...a:b2,b:b1,y:b0,x:b3,guide:b11,back:b10,leftstick:b8,...
If you whack everything between the quotes for the value field, it basically just forgot your controller(s) setup. Restart steam and see if things are better?
Are you familiar with x360 controller emulator? https://github.com/x360ce/x360ce it's open source and free... lets any controller emulate xbox controller, up to and including disabling it, just run it and leave it minimized and it should intercept all your controller input before steam can get it.
Yeah I don't think there's a global -disable-gamepad-input or anything that handy for the steam client command line options... feature request!
that's freaking funny
i completely forgot the device manager
signs of getting old, eh?
thanks for the reminder.
that's as perfect a solution as i'm gonna find without downloading 3rd party software.
DS4 controllers are notorious for this. One fix other than plugging it out is adjusting the stick's deadzone. This is a degree of stick tilt that your pc will ignore, and can be increased to counter stick drift. From my own experience, though, I have not have much success increasing the deadzone because some games or programs simply ignored the setting change.
It is also not a permanent solution, because stick drift can only get worse once it sets in. Let me save you and your partner a lot of headaches by saying, get a new one.
these deadzone-settings work for sticks: still got an old flight-stick for ED and it just works despite it beeing as old as the vanilla ED release, but i've never seen much change when it comes to pads.
usualy this ain't an issue, since many games allow you to disable controllers ingame, or you can hard-switch. but modern games often "recognize" what sort of controls you are using and then begin to start showing you ingame-prompts accordingly. it's a great system, but when your pad constantly sends out pings...i dunno i think the option to disable pads ingame should be kinda mandatory nowadays.
atleast the steam settings should work, which they obviously don't. i love steam, but that's something they could take a look at.
disabling the pad in the device manager works, but it's still kinda anti-intuative.
funny enough Cyberpunk works pretty well with a pad , but i just can't. M/K is still king unless you play some sort of From game.
I have a bit of nerdOCD. So when I tried turning off the Steam Input for Cy2077 and the damn game just went ahead and used the controller anyway (this is definitely confirmed) I got a bit... obsessive. :-)
So then I went and disabled all the checkboxes under the main Steam settings for controller tab, both regular and bigpicture, in case the settings aren't 100% duplicated... and of course, you know already - every other Steam game respects this and the controller is in fact disabled, but the second you fire up Cy2077 and see the button icons vs. the keys icons, you growl at this without even testing a thumbstick. GRR. Growl with me. Yes it's annoying. It's not disable-able.
So we're not unplgging, and we're not tolerating the dumb controller staying active.
BRUTE FORCE, choom! OK here's the drastic solution:
Note I don't know if you're technical, apologies for over-explaining something basic. Others will find this by searching and we have no idea of their skills, either. So please bear with.
First, open cmd.exe command prompt. You'll need to navigate to the Cy2077 config directory, it's wherever you put your Steam install, under the tree as <blah>\Steam\steamapps\common\Cyberpunk 2077\r6\config\ ... if you've customized your directories, that's on you to find it, just search for *2077\r6* and I'm sure Windows Explorer will help you. (if you don't want to type the whole path for the 'cd' command just go there in the GUI and then copy the path from your Explorer window's bar.)
So the file in question is inputUserMappings.xml... and let me explain now that what we're doing is stripping out EVERY SINGLE REFERENCE to button controller mappings... this way, the controller can stay plugged in but won't interfere nor can ever be used inside Cy2077 without undoing this change.
So first, we'll move the original to keep as an original, so we don't risk wrecking it. Then we'll do a regex command called findstr, that will find all references to the controller button mappings, namely IK_Pad and IK_PS4, and filter them out, we'll output that into an edited file, and finally copy the edited file to replace the active inputUserMappings.xml and no more controller input for Cyberpunk 2077.
(If you want to learn how to use regex with findstr, it's actually got a pretty comprehensive help with just 'findstr /?' but for is, it's basically findstr /v (invert selection - show what you didn't find not what you did) /r (regular expression) ".*button\ id.*IK_Pad .*button\ id.*IK_PS4" (a regex that finds every line that contains button id and either IK_Pad or IK_PS4)
There might be an easier way. I didn't find it. For all I know there's a command line option -nojoy and it'll disable joysticks ala Unreal Engine or Valve Source... I looked on the CDPR forum, on nexusmods, etc. No one knows and some people have completely reverse-engineered the main exe already, but even just a strings dump would probably tell you.
At any rate, this definitely works. Not a bit o controller input, but running calibration or testing shows it's definitely connected and active.
There is one downside - when it first sees there's a controller, it tries to overlay the button icons but nothing is defined, so you see [INVALID] [INVALID] [INVALID] [INVALID] but once you start playing it goes back to the keys icons and it's not an issue (so far, 2 hrs testing.)
It's a bit of a palava doing it that way.
it's only the non-technical gamer who's like, "what's regex?" I get that some people never leave Windows GUI and can't even connect to their own network manually without the little icons to click; but a lot of gamers code, write games/shaders, build their own rigs down to the component level, are into linux/3d/cuda/opencl/electronics, are it admins, etc. many have technical degrees. Not just beer-swilling pot-smoking no-collar labourer types wanting to game to escape from their boring lives. (nah those guys are clearly console gamers! ha.)
I only typed it long-form for someone that opens a cmd prompt and is staring at the blinking cursor and doesn't even know the simplest commands, dir, cd, etc. That's got to be intimidating.
That CDPR didn't just give us a simple <event name=enable_controller type=bool value=false / > is as maddening as the RangedALS being a hold not a toggle... they just didn't think about it. Or worse, they did, but consciously decided to deny giving it.
I'm sure someone will make (or already has made) a "mod" that does this for you. I hate that, because most "mods" aren't mods at all, they're like this, they're acting cool like they're doing something elaborate when really it's one line of code or script. Like and subscribe! lol.
it's easier too,
1. Right click on start
2. left click device manager
3. expand controllers
4. Right click controller
5. Left Click Disable.
Or 3 seconds to unplug it from a USB extension lead.
in theory it should make using the device manager obselete
not having tried it yet, but used the devive manager; but if it works i think i'm gonna keep it
it's only me playing CP on this rig, so having the pad hard-disabled is the best solution.
unplugging again is not the best solution; especialy in the evenings we switch places (my rig is the modern one) pretty regularly and i realy don't want to do this to either the pads ports or my babies...saw what happens with more than enough MP3 players and most pad-ports are as cheap as humanly possible.
none of this changes the fact that either steam or CP needs to adress the controller issue. in 2022 both games and the platform needs to have the option to turn individual devices off. it's not that hard to code.