I am attempting to use a Steam Controller to play Destiny 2 on Steam. Mouse and keyboard inputs from the controller work, but any gamepad inputs from the Steam Controller have no effect in Destiny 2.
There are no problems with gamepad inputs from an actual Xbox One controller.
There are no problems using Steam Controller gamepad inputs in other games.
-
And my xbox one gamepad dont want to be configured in steam overlay, destiny 2 just ignore all my settings, i want just configure aim sensetivity ,,,=_=,,, in ALL other games everything works good!
-
So they added an official steam configuration for the steam controller but it is gimped as hell. Won't recognize mouse joystick so you are stick using analog movements in left pad which is the worst way to use a steam controller. It makes using gyro useless. Have to stick with GloSC.
-
Feburary 2020 still not fixed... lunching D2 with big picture, with a DS4 via bluetooth and the MnK controls shows. Gonna play wired but please Bungie fix this.
-
Me too, this is super annoying. I did have it working on GLOSC when it was on blizzard, but I deleted that when it came to steam, assuming it would work. Stupid me.
-
Same here. What baffles me is that it used to work on Windows 7 and stopped working when I installed Windows 10 yesterday.
-
same here. lots of posts like this, hopefully bungie maybe looks into it. lol.
-
Today, for a moment I confirmed that I can use GLoSC with the Destiny2.exe. While this seemed to do the trick when I utilized the Steam Controller configuration 'Gamepad with Camera Controls' - a default configuration which effectively turns the Steam Controller into an XBox one analog - I only did this for testing purposes. Friends warned me of the potential risk of a ban for using the GLoSC overlay. I'm hoping to get answers from Bungie regarding the risk before spending 70$+ on an XBox controller for casual play. I don't recommend using GLoSC to attempt to apply configurations which combine M&K and Gamepad controls. Those types of configurations didn't work with the Blizzard launcher and GLoSC overlay, I can't imagine they'd fare better now, or that they should.
-
Steam controller doesnt work - Check. Do anybody have a vibration work on xboxone pad? Me not.
-
Simillar problem, can't connect using my switch controller.
-
Similar issue. My setup: PC has monitor turned off, MnK connected. I have an Xbox One S controller wireless connected to SteamLink. I can launch the game via SteamLink, but the game won't recognize any input from the controller. It appears to expect only MnK input. The icon in big picture mode shows a keyboard, whereas other games show a controller. I am able to use the SteamLink-connected controller on Bioshock Infinite, and Portal 2. I was able to workaround by connecting a second controller wirelessly to my PC, and launch the game with SteamLink-connected controller, and play with PC-connected controller. Not ideal, but it works. Given the icon, I'm betting there's something Bungie needs to configure on their side to receive active controller input when the game is launched via big picture mode.
-
I can't get the Steam Controller to be recognized by Destiny 2 at all. The controller worked better when the game was on the Blizzard store! Not only that, the game wont start at all when Steam is in big picture mode. No error message, it just refuses to launch. Launches fine in desktop mode, but then, no Steam Controller. Very frustrating!
-
Destiny 2 does not support Steam Input. Destiny 2 has its own controller support.
-
Same here! Using Dual Shock 4 (gen 2). Only works when connected via USB, like some sort of caveman
-
I have an issue with an Xbox One wireless controller using a micro usb cable. It works with other games, but Destiny 2 says it is not controller compatible using big picture mode. When I plug the controller into the pc it works fine.
-
Edited by Eagle: 10/6/2019 7:37:32 AMI'm not able to use my PS4 controller with Destiny 2 either. Works perfectly in games like Rocket League launched from Steam so I know it is not a controller-to-PC or controller-to-Steam issue, definitely Steam-to-Destiny 2 or outright Destiny 2 issue.
-
I'm having the same problem.
-
seconded. I'm in the same boat.