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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Didn't get the change to properly thank you again, so, thank you once more. :)
I'd like to add that the registry key may differ from person to person. In my case, it was:
So, I had to make a simple edit to your .reg file (using Notepad) and replace:
With:
Yes, it does.
*Edit*
Of course the moment I look back and casually try it one more time without changing any steps, it does successfully change to the right entry. That said, I am still curious as to what would cause this issue. Any suggestions are welcome so I can avoid this in the future.
If I were to guess, there was probably some Windows update that messed with the configuration. Example being my Sound Blaster AE-9 has an SBX profile (basically an EQ profile) simply called "Gaming", with pre-configured audio settings. One day the gaming profile just disappeared. The configuration files for SBX profiles are stored in .json files, and the 'Gaming.json' was there, but all the configuration information contained in the file was gone. Basically, the file was blank. The rest of the 30+ files, remained intact though. No idea what happened. I just grabbed the text that belongs in the file from the net, and that fixed it.
Hey, fIreChuckEr! If you're still around, do you know if there's a way of preventing the Astro C40 from reverting to an Xbox controller after Windows restarts?
I'm still using your scripts, but every time I want to play with the controller as a DS4, I have to not only make sure that the controller is off, but also manually unplug the USB dongle before running the script, or else, it won't work.
Since I game from the couch, if I could simply run the scripts and be done with it, it would be a non-issue. But remembering to remove the dongle before doing anything, including starting Steam (or it'll identify the incorrect controller and apply different configurations) is a little cumbersome.
Hope you're doing well, mate, take care!
Doing well, thanks! I can replicate what is occurring, but I do not believe there is much that can be done, because this looks like how the driver behaves. Being that even having a "PS4 Mode" is more of a hidden feature with this controller.
From what I can tell, on boot up it selects the Xbox (PC) configuration by default, and when removing and reinserting the dongle, causes it to flip to the other configuration (PS4) as long as it detects the Logitech driver (yes it is a Logitech driver) is in its alternate mode.
Looking at everything, there is an order of operations that is occurring on boot up and it always follows that order. Reinsertion of the dongle causes it to shift the configuration. I will keep messing around with it, see if I can find something to change how it boots.