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'm on w10
Note: I had to install the driver (link in main post) and restart my PC before it stopped spinning the camera.
Note that I couldn't use an 360 controller, it just didn't work.
This needs to be stickied
However, if you read the text in that link, it says the driver link is for Windows 7 and 8.x only as Windows 10 comes with its own (apparently bugged) driver that does not work properly in a number of games, mainly Unity Engine ones in my experience (Ori and the Blind Forest, Beyond Eyes, etc, etc).
Those Windows 7/8.x drivers DO work in Windows 10 though but the side-effect is that you lose the Xbox/Guide button functionality for accessing the Game bar in games (used for taking screenshots and DVR footage). If that doesn't bother you then it is not a problem but I do use it and use the Xbox One controller for the majority of my PC games so it is not ideal for me.
I am beginning to regret (a) having sold my Xbox 360 controller; and (b) upgrading to Windows 10 so quickly because of these kinds of issues. Issues, which IMO should not exist as Windows 10 has been in public beta for at least six months (possibly longer). I find it hard to believe that no-one has reported the Xbox One controller issue in games until now.
Same here
*edit*
I got it functioning correctly.
what i did was uninstalled\reinstalled the controller driver "without" uninstalling the Xbox one controller peripheral in device manager, this prompted a restart.
-----
after restart I loaded up game setting first and changed the camera rotate controller buttons to the same as already selected but when I clicked the buttons the listed button names changed from RShoulder\LShoulder to RightShoulder\LeftShoulder.
It all functioned correctly afterward, I am not sure exactly which did the trick though the reinstall of the driver or changing the button assignments.
Not sure if this will help anyone, but I hope it does.
What I did exactly in case anyone else gets confused
-Leave controller plugged in, download the driver from the link in the main post and open it
-If your driver is already installed you will be given an option to repair or remove it, choose remove
-Now go and activate the driver install again, this time it will automatically choose install
-With my controller still plugged in and drivers reinstalled, i shut down my computer, and turned it back on
-Loaded up Grandia II Settings, and Re-bound the Turn Camera Left to LeftBumper, and Turn Camera Right to RightBumper.
-Hit play, load up my gamesave, boom no more rotating camera
Hope this fixes it for all Win10 users
That's why as a general rule, wait for first SP to update to a new OS if it's not mandatory for a game/program. You have a full year to update to W10 anyway.
- As I mentioned before, the triggers will now be bound to the same key, and making them on an axis messes with other games in weird ways. Take DMC, for example. Unless you press the trigger all the way down, Dante's weapon will disappear off his back and sound effects won't play. You also won't have access to demon mode since both triggers are the same map.
- You WILL have double inputs since the system will think you have an Xinput and Dinput controller plugged in at the same time. This makes Steam Big Picture un-navigable and, as you know, some games that use both protocols to have dual inputs as well.
This is a good stop-gap solution but having to switch driver versions all the time is a huge pain in the ass.
This is for W10 only, BTW, with an Xbox One controller. I guess there's a reason that updating the drivers automatically in the device manager wants the controller to use "Xbox Controller" instead of "Xbox One Controller" drivers.