Sergio David Ballen Gomez Glad I could help. As soon as I saw the free weekend I immediately thought of you and went to work putting this video together.

Dude... Learn to use mouse and keyboard, it's waaaay better for Destiny! I played D2 at release with controller for the first couple months and just stsrted playing again a couple months ago but this time with MnK and the game is sooo much more fun now. PC was def the way Destiny was meant to be played its so much better and smooth playing and navigating threw your character and everything with mouse and keyboard! Highly suggest making the move if you havnt already

Yeah dude I’ve been freaking out for an hour to figure this out lol

@@DirtNassty I'm a 20+ year veteran of m+k, starting with Quake 2 (because I hated mouse aim in Q1 and was sure it wad a fad that would die out....arrow keys plus auto vertical aiming was fine enough😂). I was one of those die-hard master race "shooters should only be played with mice" gamers. I picked up the Steam Controller almost 4 years ago and haven't looked back. M+k really only has the benefit of mouse aim and gyro aim is comparable. I now have a form factor that I find comfortable without sacrificing my ability to aim precisely and quickly. And even if I played like garbage, what does it matter to you? Stop gatekeeping gaming and input device preferences. If someone enjoys using a dual stick controller to play Destiny then you have no place to tell them they should be using something else.

@@criticalinput lol... You okay dude? First off I wasn't even talking to you... And secondly I could give a shit less how someone else plays a game I was simply making an opinion in a friendly way.. Not the aggressive negative way you obviously took the comment that again, wasn't even directed towards you. Chill out my dude And I disagree 100%... Even just navigating menus, character screen, settings etc... Is way better, quicker, and smoother on m+k then it is on controller, especially in a complex game like Destiny.

Thanks for the kind words!

Glad it worked for ya! Enjoy the game with your Switch controller.

@@criticalinput Thanks again.

I haven't encountered this myself but GloSC's FAQ has something that might cover this. "If running on mobile, open up NVidia control panel (right click your Desktop and select it). Manage the 3D-settings and have it auto select your graphics processor. Alternatively there is the _`bEnableOverlayOnlyConfig`_ setting in GloSC's .ini files. If this flag is set, the overlay is only shown if it is opened. This will, unfortunately, also prevent you from using touch- and radial-menus." The GloSC ini files are in the GloSC install folder and are per shortcut.

It's been like this since Day One, that is why we use GloSC in tandem with bnetlauncher.

100% safe guaranteed. GloSC isn't an overlay and acts entirely separate from the game. As far as Destiny is concerned, nothing else is running at all.

@@criticalinput thank you so much for your help

That Other Guy Nice! I think the only other way to do this same thing is with using OSOL rather than BNetLauncher. Otherwise, this is the only method that had a 100% success rate during my testing.

As long as you are using keyboard+mouse bindings then you don't need to jump through any hoops for the Steam version of Destiny 2. If you are using a k+m config then my guess is that the Analog Binding for the trigger is set. Make sure both Triggers have Analog Off set. It is the top setting in the middle column, to the right of the Full Pull Binding.

Apologies but the Steam Link is not my forte. I would suggest checking out the streaming settings in Steam or the Link and making sure that they are set to Best or Beautiful or whatever the top setting is. Otherwise, I would suggest asking at the Steam Link Discussions in Steam or at the /r/Steam_Link subreddit.

I wasn't aware that Destiny didn't support multiple simultaneous inputs. I prefer mouse/keyboard for FPS titles on the SC so I never ran into the issue. As for Mouse Joystick, it isn't a horrible mode but it does require a lot more game-specific work to make it feel right. I'm still not familair enough with the Input Style to make it work great but I've heard some people say that it is possible to make it feel close enough to Mouse.

I'm pretty sure that Destiny 2 does not support mixed simultaneous input. You'll need to make a config that only uses keyboard/mouse bindings or only uses XInput (xbox) bindings.

I'm working on an updated version currently. For DS4 your best bet is to use the native controller support (disable Steam Input) or bind a full mouse and keyboard config (if you want gyro aiming).

@@criticalinput excitedly waiting for an updated version. Having issues making this work with my steam link

@@knightwraith8666 Someone else has commented that they were having issues with Destiny and the Link and had to run Steam with admin rights to fix it. Might wanna give that a go.

Just add any shortcut to Steam first. GloSC is trying to edit a file that hasn't been created yet. You could add anything to Steam, even a web browser, you just need Steam to make the shortcuts file. After that you can remove whatever you added to get the file created.

Thank you. I was reading lots of info and yes it seems I need to add something first to steam. I will try that and let you know. Cheers

Yes that worked . Steam controller running good with d2. Thanks for your help guys

I'm glad it worked. Enjoy gaming with the best controller on the planet!

I've been hearing about this a lot recently. If you got GloSC running then you can manually load Destiny at that point. It isn't as seamless of an option but at least you'll get to play. I'm still looking into why this is happening for some users though.

@@criticalinput Yeah thats what im doing for now. would be great if we could get the seamless option back though. thanks for the reply and the great tutorials

Actually, do you even have aim assist with this? Because if not there is no point in doing this for me.

I believe that you'll have aim assist if you use XInput bindings. As for things not working, it sounds like GloSC isn't running and Steam has attempted to hook into Destiny, obviously failing. Alternatively, make a new GloSC shortcut but don't check the Launch Game button and don't fill in the path box. Run that just to make sure that GloSC is working. If you can get that working then just run Destiny normally (through Battle.net) after running this no-game GloSC shortcut. It requires an extra step but should definitely work.

@@criticalinput I had this working perfectly till today. Now steam says Destiny 2 shortcut failed. I tried doing the just GloSC with no path filled and launch game unchecked and that didnt work either. Any ideas?

@@TheDB503 the first issue, if Steam is throwing the error then it means that the shortcut is bad. Dunno how that happened but you could try removing the shortcut and making a new one in GloSC. Your second issue makes no sense. If you run a GloSC shortcut then all you need to do is run Destiny 2 via the Blizzard Launcher. If Destiny still doesn't run then you have a Destiny issue. If Destiny runs but the controller doesn't work then that's a GloSC problem and I would advise reinstalling GloSC.

Sure, though it's a really old config. I made this during the Destiny 2 beta and, since I don't own Destiny 2, I haven't made any changes. The core bindings look to be up to par with my other FPS configs but it might be missing some non-combat bindings that are specific to Destiny 2. Here is the link to the config: steam://controllerconfig/destiny%202/1440805409 If you don't know what to do with that link, just press Win+R (opens a Run Command) and put that in the box. If you aren't on Windows then you can just put that link in a browser and it should work as well.

thanks.

How are you creating the initial shortcut that doesn't work? Is it a GloSC shortcut?

I ended up uninstalling and reinstall GLoSC under /Program Files/ instead of in my games HDD and that seemed to have fixed it.

That's awesome! Glad to hear that you got it sorted out, as strange as the solution ended up being.

This is an issue that I've heard a lot about recently. I've looked into it and haven't really found a solution but as long as the GloSC window is opening then you can manually run Destiny 2 after that. GloSC doesn't hook into Destiny or anything like that, running the game with GloSC is just a time saver so you don't have to run multiple programs. I'll be making a new video soon-ish (I need to get a hard drive on Black Friday first) about using a new combination of programs for this that will hopefully cause less issues.

@@criticalinput I figured it out after I reinstalled GloSC. My antivirus was deleting some files which created a disconnect. Only took me 6 hours of reinstalling things to work it out

Thanks for sharing. Now I have something to go off of when I'm asked about this in the future.

OK. So this happens whenever ViGEm doesn't get installed properly, usually due to Powershell not being the newest version. To manually install ViGEm, just follow this guide docs.vigem.org/#!vigem-bus-driver-installation.md

Rei Senpai Really, we should thank Bungie for doing the free weekend :) But yeah, even I got asked a lot about this so it's nice that I can finally point people towards a tried and true method.

CriticalComposer is your config final? I'd love to see how other people approach a config for D2. I put a lot of time into mine and wanna see what other people can do. I never got the OSK working right, so that'd be cool to see

Rei Senpai Nope, the config was leftover from the open beta. If Steam hadn't of remembered that then I would have probably just used a generic FPS config. I don't own the game so I didn't put much thought into it. Though I'm currently analyzing how to make my FPS configs more efficient and am heavily leaning towards using two radial menus, gyro only aiming, and movement on bumpers/triggers. I made a big thread about it on the subreddit and I'm updating that as I progress with the experiment.

CriticalComposer 2 radial menus? Would that be for more efficient strafing?

Rei Senpai Yup. I currently have Move Forward/Backward on RT Soft/Full Pull and Strafe Left/Right on LB/RB. Digital buttons for digital movement and one finger per button, just like WASD on a keyboard. My Stutter Step has improved greatly and the Left Pad has become more useful as it doesn't just do movement anymore.

Which site are you referring to? Because this setup will never not work based of how the different pieces interact with the game. In fact, there really isn't anything that Bungie can do to break this setup because it doesn't actually do anything directly to the game. As far as Destiny 2 is concerned, it's running all by itself with no other programs interacting with it. And if it somehow did stop working then I'd have heard about it at /r/SteamInput or /r/SteamController. So I'm going to wager that it still works just fine. Give it a shot and let me know what happens.

You just need to install the latest ViGEm. github.com/ViGEm/ViGEmBus/releases

So the GloSC window opens but it doesn't respond to your controller?

First of all, if you are using an Xbox Controller or Dualshock 4, Destiny 2 has support for both of them. Unless the profiling aspect of Steam Input is important to you then I suggest disabling Steam Input support on Destiny 2 and using the native support for these controllers. Alright, the Steam version of Destiny 2 doesn't block injected draw code like it did on BNet. This means that the Steam Overlay works perfectly in Destiny 2 without the need for GloSC. However, Destiny still blocks injected XInput code (as an anti-cheat method) so you have to use Keyboard and Mouse bindings in your config. This is actually preferable (to me) since the game doesn't accept mixed inputs (there is different code for gamepad inputs and mouse inputs such as totally different recoil for weapons) and I would much rather deal with digital movement than deal with imprecise aiming (with using Joystick Emulation or Mouse Like Joystick). If you still want to use XInput then I don't have a solution yet. I'm experimenting with ideas and as soon as I discover a method I will make a video about it and make sure that you get the link.

@@criticalinput do ds4's work wirelessly? my usb C slot broke

@@turtlehub2731 The PCGW doesn't have any data on which DS4 connections work but I would be surprised if it didn't work wirelessly. Hopefully they have support for both BT and the official receiver.

@@criticalinput Turns out this morning I found I could use GLoSC with the Destiny2.exe itself and that seems to have done the trick for my Steam Controller. Testing presently. Made it as far as the login screen.

@@adttada Thanks for this. I have been too busy testing out a new experimental FPS config to play around with fixes for Destiny. I just tried this and it works just fine despite some small issues that can easily be overlooked. I'll have an updated video out this week.

Uhh... I might still have it lying around....somewhere. I'll check it out next time I'm at my computer and I'll let you know what I come up with. If not then I'll link you to my current Destiny 2 config instead. It's similar but has some minor tweaks to it.

@@criticalinput Thanks. Also, I've been trying to get it working more efficiently, but I can't seem to get the game to not run at 30fps when I've got GloSC running. If I'm running without it, I'm playing just fine.

@@hartleyharms4404 Dude, I totally forgot about getting back to you with the config link. So sorry. Here's the link to the config: steam://controllerconfig/destiny%202/1564216668 As for Destiny 2 running worse with GloSC, my first intuition would be your CPU. Both Destiny 2 and Steam's BPM Overlay are CPU hogs and you could be pushing your processor by running both simultaneously. I suggest running Task Manager while playing D2 with GloSC and see if your CPU is maxing out.

I explained in a different comment, but the Steam version works differently than the Bnet version. You're best bet currently is to disable Steam Input support (either globally or just for Destiny 2) and use their native DS4 support.

Actually, I'll be streaming Destiny 2 in the morning (10a EST) over at twitch.tv/criticalcomposer if you wanna drop by. It'll be from the beginning of the game but at least it'll be gameplay. I won't have a controller cam but I am using a program to show which buttons I'm pressing on the SC.

Followed. Work tomorrow but I'll try to tune in

@@runescapa239 Thanks for the follow. The stream will remain on Twitch for a while so you can always check it out post stream as well.

I've done the testing and have most of a script written, I just need to pry myself away from Destiny to make the video :)

@@criticalinput Thank you so much, I really miss using my Nintendo switch pro controller for my games.

@@criticalinput Came across your video while troubleshooting, looking forward to the next one as well, I just subscribed so I don't miss it. GloSC didn't install VigEm and when I finally tracked down an installer and got it showing up in my device manager the Vigem error went away but I'm still getting a blue screen then getting sent back to the shortcut when trying to launch through the shortcut on steam link.

@@RoninKnightfall GloSC and the Link could theoretically create issues, though I've never tried it. I'll do some testing and get back to you with my findings.

Got it working last night finally, had to run steam as an administrator. It took a few seconds but the game loaded instead of hanging or failing.

OK. So this happens whenever ViGEm doesn't get installed properly, usually due to Powershell not being the newest version. To manually install ViGEm, just follow this guide docs.vigem.org/#!vigem-bus-driver-installation.md

I've done that and now all that happens in the glosc overlay launches and nothing else as if D2 isn't launching

So when you run the shortcut that GloSC created, Blizzard Launcher isn't running either? As long as you pointed the GloSC shortcut at bnetlauncher.exe and put the dst2 arguement in the argument box then everything should be running fine. If you could, upload a screenshot of your GloSC shortcut settings (inside of the GloSC application) and I'll see if anything stands out to me. However, as a band-aid fix, as long as the GloSC overlay is running then your config is loaded. So you can then manually launch Destiny 2 like usual with your mouse and keyboard. Having the game launch with GloSC isn't required, it just saves a bit of time.

@@criticalinput yep that works, thanks alot

@@criticalinput THANK YOU! I was about to give up after getting the same ViGEm error. Works perfectly now. You = saint

I'm excited about this but worried, simultaneously. Bungie hasn't said anything about asking back their policy be regarding application hooks. That wasn't something unique to Activision or Blizzard Launcher, that was an active choice by Bungie. If they still stand by that decision then it could make it a bit difficult to launch. GloSC works best with games outside of Steam since Steam Input only has one application to focus on: GloSC. But if you need to run GloSC and Destiny through Steam then Input will be trying to hook into both with a priority given to the one that has focus, which will be Destiny. Basically, Destiny coming to Steam might actually introduce issues for Steam Controller users. Non-SC users can simply disable Steam Input support for Destiny (allowing Steam to focus on GloSC) but that option doesn't work for the SC yet. Fingers crossed that Bungie allows application hooking now since Steam has an overlay (unlike Blizzard) but I'm not gonna hold my breath.

@@criticalinput Good thing I got other games that I can use the Steam controller on even if they stick to that policy after moving

DerDuke1981 Yup, and I addressed this within the first minute of the tutorial. We use GloSC to circumvent their anti-overlay code.

Huh. For some reason it won't work for me, still trying to figure out how to do it

DerDuke1981 What exactly happens when you copy this method? Does the GloSC window appear (you can alt+tab to it and it will appear in your taskbar)? Also, are you running Windows 10? I didn't mention it in the video because I covered it in the dedicated GloSC tutorial, but GloSC is only available on Windows 10.

I run Windows 10. GloSC says that it can not find a shortcut to destiny 2 anywhere altough it is installed and battlenet is running. I must admit I have not watched any other GloSC videos yet and it might very well be that I am missing something on that end.

Just for clarity, let's make sure you followed all of the steps. In GloSC, you checked "Enable Overlay" and "Enable Virtual Controllers," then you disabled "Use Desktop Configs," and you checked "Launch Game" and pointed that to bnetlauncher.exe. Then you added "dst2" to the Arguments box, named the shortcut, hit Save, and then Add All to Steam. But then when you run that shortcut in Steam it is telling you that it can't find a shortcut for Destiny 2? If so, then the process is correct so I would start with making sure everything is up-to-date. Get the latest version of GloSC, BNetLauncher, Steam, and Battle.net. If you need to update GloSC then I would suggest remaking the shortcut just in case.

Haha alright! Glad it's working for ya.

And Warface. Thanks for the video.

Adam Kallin Alright! You can expect Warface in the next week or two since it's F2P though I'm 99% certain that it'll work just fine as a Steam Shortcut, no extra software. I don't own BF4 so I can't promise anything there, but I do own BF3 so maybe I could do something with that. If you want to try things yourself, I highly suggest OSOL (OriginSteamOverlayLauncher) for BF4.

I'm going to check into it, just in case, but Warface is on Steam and has tons of Community Configs so I'm thinking that this game plays nicely with Steam Input out of the box. Are you currently having issues getting Warface to work correctly with Steam Input?

Final reply to this comment -- I promise :) I just tested Warface and everything worked as expected. Granted this was the Steam version and not the standalone launcher but it still opened the My.com game launcher. However, if you are experiencing issues with the standalone launcher I highly suggest moving over to the Steam version. Being that you have Steam installed and you'll be running the game through Steam anyways, this just seems like the best course of action.