Shu Zhang While I do agree that Steam Input should have a way to work without hooks, it would make the process too complicated for the average user (and Steam Input is already very complicated). I do think that Steam Input should be removed from Steam eventually but it needs to get to a 1.0 release first and they would need to find an alternative to the BPM overlay to ship with the standalone configurator.

Its not a Steam issue but a Microsoft one. All their games are in fact using .exe's but are blocked. They use their UWP to unlock the .exe's. If they didn't block it like literally every other game there would be no issue for what we have already. If you add Origin.exe and Uplay.exe and launch from there all games work fine without third party.

MrKoronaaa haha thanks! Depending on how different the new version is I'll probably be making a follow up video. Be on the lookout for that if you're interested.

As of today I'd recommend using reWASD if all you need is to emulate an Xbox controller. It's super lightweight, doesn't require Steam's overlay, and uses a virtual driver that is nigh undetectable. Even EssentialEgg/RambleTan has found a game that only works with reWASD -- GloSC and Steam Input doesn't work. The only thing about reWASD is that it isn't free but it is well worth the asking price considering how often I use it.

hey hunter can you play with gyroscope in forza?

miketengu sorry dude i no longer have steam controller and don’t remember about gyro. I used left stick if I remember right

GloSC wouldn't be able to do anything running from the client device (the Android/iOS device running the Steam Link App). At best it would do nothing and at worst it would interfere with the input data getting to the host PC and subsequently to Steam Input. The Steam Link App already supports mobile touch input, though it isn't entirely fleshed out. A single tap is a Left Click, a two finger tap is a Right Click, Two Finger Pinch/Swipe is Zoom/Pan, and a three finger tap is to bring up the keyboard. Though I couldn't use this keyboard to transmit data in version 1.01 (current is 1.10). I managed to do some light web browsing with this as well as played a simple mouse-centric puzzle game just using the touch input on my phone.

Oops, I actually worded that completely wrong. Thanks for the reply, btw. It was regarding the steam controller BLE mode being used for android apps, nothing to do with streaming mode at all. Now that you can connect your controller to android/ios devices, would there be a way to use an overlay to play games that doesn't support the steam controller like pubg mobile, fortnite, or games like that.

myndgame This is completely speculative, but yes something like this could exist. In fact, there is already a configurator on Linux that allows you to program your Steam Controller without Steam running. I don't think the gryo works with the software (yet) but the fact remains that the SC does send outputs for every button even when in Lizard Mode. So theoretically, someone could write a program that reads the SC buttons and then translate them to on screen touchs a la TinCore or the Nvidia Shield Gamepad Mapper. Even the Sixaxis Controller app could translate DS3 button presses to touch inputs so the ability to both read the SC and output to touch inputs have been done before. Now someone just needs to combine that knowledge and put it into a single android app.

CriticalComposer, awesome information that it could possibly exist. Hopefully people love the SC enough to find it worthwhile to create a program that would tie everything all together in the near future.

GloSC shouldn't come in a zip, it should be a setup file. Make sure you're downloading the setup file from alia5.github.io/GloSC/. Click on the "Download Latest Release" button.

This video was made before Riot changed engines for LoL, back when it ran on Adobe Air. Steam Input no longer works with LoL. You can get keyboard/mouse input into it with various methods but there isn't any way to get overlay elements inside of LoL anymore.

The easiest way would be to make a GloSC shortcut with the Launch Game option unchecked. When you launch this shortcut in Steam you'll get your config loaded for your controller. Then just run your mod organizer and/or script extender as usual (with mouse/keyboard if necessary) and enjoy. It isn't a single step solution but it is guaranteed to work every time. I firmly believe there is a single step solution somehow but I have no experience with Bethesda games nor running mods for them so I wouldn't know where to start on making one.

GloSC got renamed to GloSI, so knowing that will probably help in your search. If you found the GitHub page, those release downloads are just master folders and you'd have to build the program yourself (that might be what you mean about just files and folders). To get the pre-built application you need to download it from Alia5's website: glossi.flatspot.pictures/

Seems the dev took down GloSC. As far as I know there isn't any backup of the original files unless you wanted to build it from the Github files.

GloSC is 100% safe. All it does is open a window for Steam to display the overlay in and it sends Steam's XInput calls to a driver called ViGEm, which is also safe and used in quite a few programs to flawlessly emulate Xbox controllers.

Just download the latest version of ViGEm and install it. github.com/ViGEm/ViGEmBus/releases

The two main questions for this would be: which game specifically is giving you issue and are you sure that you are adding the .exe to the shortcut box in GloSC? Aside from that though, you should be able to manually run the .exe after the overlay pops up and everything should work as expected at that point. It's not a great method but is a nice band-aid fix until you figure out exactly what the issue is and how to fix it proper.

CriticalComposer I fixed the issue!!! I was not running steam as admin!!!

Autocorrelato90 I'm glad that you got it working.....but I've never run Steam in Admin mode since it is just bad practice to do that for any application that opens other applications (the admin rights are hereditary). While I'm 99% sure nothing has will result from this, I do urge you to eventually discover the issue and find a more practical fix for the problem. Still, I'm glad you are able to play your game now.

For starters that doesn't sound like GloSC crashing, it sounds like an issue with Blizzard Launcher. Actually, it reminds me of an error I've seen before when using bnetlauncher but you didn't mention using that. I would suggest making a new GloSC shortcut. Check "Enable Overlay" and "Enable Virtual Controllers" but leave everything else unchecked. Then try manually running Destiny 2 and see if that gets rid of the error. If you are feeling a bit more adventurous, I would suggest trying to use OSOL (github.com/WombatFromHell/OriginSteamOverlayLauncher/) to launch Destiny 2 through GloSC's "Launch Game" option. This is my current method and works very well. I'm planning on updating my Destiny 2 tutorial video for this software rather than bnetlauncher so if you are having some issue, be on the lookout for that video which should be out soon.

@@criticalinput Thanks for the speedy response ! I am using the bnet launcher. Sorry I forgot to mention that. I tried it again and it seems that if I just ignore the prompt box that it is broken and needs to shut down, I can continue using the controller like normal. I thought that was odd. But it works. I will be on the lookout for your new video. I will look into using the origin system and see what I can come up with.

Also that link didn't bring anything up. Gave a 404

@@Henry_Jones_Jr Yup, just carrying on and playing past the error works too. With GloSC, it doesn't actually interact with the games at all so as long as the game is launched and working then GloSC will work as well. Ok, so KZfaq decided to keep the closing parenthesis in that url. Try this github.com/WombatFromHell/OriginSteamOverlayLauncher/

It should work just fine regardless of controller since GloSC talks to Steam Input and not the controller itself. Are you sure that GloSC works in other games? And are your GloSC settings for the Forza Horizon 4 shortcuts setup properly? And does an Xbox controller show up in Windows' Game Controllers window? What about if you make a GloSC shortcut that doesn't launch Forza? Just have enable overlay and enable controllers checked. Run that then run Forza manually.

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

@@criticalinput thanks it works perfect now

I believe you need to have the game open when you are trying to select the game in GloSC.

Yes.

You'll have to manually enter the path of the game then. Unfortunately, I have zero experience with this and no longer have any WinX apps on my system to test it with.

Jevi Cordon I Dunno what ViGEm error you are running in to but I would suggest contacting the GloSC dev. He has a Discord server specifically for troubleshooting. The link for that is discord.gg/dEFHVBz

I had this issue. I had to enable unrestricted script policy windows powershell in order to allow for vigem to install it's script. Found this out through trial and error. There is a powershell script in the glosc redist folder that you have to manually input to install vigem. Hope this helps.

I just can´t get it to work... It always tells me: couldn´t detect steams shortcut file. I really don´t know what i´m doing wrong

You have to make one shortcut in Steam before using GloSC. Just click the plus in the bottom left of Steam, Add Non-Steam Game, and add anything (notepad.exe works). Then GloSC should work.

My guess would be that both Steam Input and GloSC (now called GloSI) are working. So you're getting the input from the injected code of Steam Input as well as from the emulated XInput device of ViGEm. I would check to see if the game works fine with just Steam Input first.

Destiny 2 no longer requires this. When it made the jump to Steam it was tweaked to work really well with Steam Input.

@@criticalinput really? If I plug up my steam controller and launch d2 I get....nothing? I cant even do anything at the character selection screen. I must be doing something wrong or forgetting something simple, lol

It's been a long time since I've played Destiny or used Steam Input but as long as your config is set then you should be good. Otherwise I'd make sure all of the settings are properly set for Destiny (Allow Steam Overlay, Allow Steam Input). Sorry I can't be of more assistance.

@@criticalinput *slaps forehead* It was the joystick and not the touchpads...this entire time all inhad to do was move the joystick (I assumed the touchpads would be the joysticks and never checked the button layout). Well, that's embarrassing. 😓

It's happened to the best of us, no worries man. Enjoy the game!

This just means that you've never added a shortcut to Steam before. In the bottom left corner of your Library click Add Game and then Add Non-Steam game. Then add anything from this list, it doesn't matter. This will force Steam to create the shortcuts file that GloSC needs to edit. Now GloSC should work and you can delete whatever shortcut you added initially.

100% safe. There isn't anything going on that Steam could even know about. It's hooking into an application and injecting both XInput and draw commands, no different than any other game. The only difference is that GloSC is sending the XInput to a driver.

Is this any game or just a specific game? There are certain games that completely reject emulated input and GloSC is the best workaround for getting Steam Input to work with those titles. If it's any game, or even manipulating Steam on the host desktop, then you have an issue with the streaming aspect and GloSC won't help with that. You'll need to figure out why your inputs are being lost between your laptop and desktop.

​@@criticalinputThank you for your quick reply..I'm not sure what your stance is on this but the games I'm trying to play are downloaded through non kosher means (if you get what I mean) games added as non-steam games. They work fine when launched in the main desktop through the steam and DS4 support. It's when I launch to stream said games from the laptop that the DS4 paired with the laptop seems to be completely unrecognized. Albeit, some kosher non steam games do work when streamed, it's hit and miss. On another note, I've managed to use a program called "Virtual Here USB" with the steamlink as the server and the desktop as the client. It was a modified steamlink app that allows Virtual Here USB hub to work with 1 device trial version on steam link and desktop, but no luck on the laptop. Virtual Here works well but it's pricey, and in my opinion not worth purchasing. Any ideas even if not related to Glosc, I rather donate to your patreon than pay 2k games, origin, for full versions of old games or buy the virtual here usb license ($50). Thanks again.

@@based1669 If it is hit and miss and the DS4 works while streaming sometimes then GloSC *should* be able to fix the issue. Does you ever have issue with using the DS4 outside of games while streaming -- such as navigating BPM?

@@criticalinput yes it almost always does. I think the problem is the pirated games may mess with steam somehow in order to run the game. Either way, I got VIrtualhere USB to work but using the actual usb cable connecting the controller to the laptop, the dongle for bluetooth works for the steam link, but I guess I can take this tradeoff for now.

​@@based1669 I know it isn't the best setup, having to get all of that connected, but at least it works. I wish I had a better answer for ya.

hey friend can you this with gyroscope in forza?

Alright, I'll walk you through step-by-step for Destiny 2. Open GloSC and add a new shortcut. If you are using XInput bindings (not mouse/keyboard) then make sure "Enable virtual controller" is turned on. Other just make sure that "Enable Overlay" and "Launch Game" are turned on. Then point the path to battle.net.exe and put "battlenet://dst2" in the arguments box (no quotes). Click "Save" then "Add all to Steam" and you should be good. Steam will restart and then try launching that shortcut that you just made in Steam. Inside of Destiny 2 make sure to go to your video settings and change the window setting to Borderless FullScreen so that GloSC can seemlessly render the Overlay over the game when you press the Guide Button. Then make your config and you should be good to go.

hi, when i click "Add all to Steam" appears a message that said "couldnt detect steam shortcuts files, make sure you have at least one non steam shortcut for the file to be present" what step i miss?

Sergio David Ballen Gomez huh, I didn't realize that this was a pre-req. Basically, GloSC edits a file that Steam creates but you haven't told Steam to make that file yet so GloSC can't find it. Alright, open Steam and in the bottom left of the Desktop UI (not Big Picture Mode) click add a game. Then click add non-steam shortcut and select any one game/application. Now go back to GloSC and press Add all to Steam.

ok that part worked, i can click add all to steam, the restart the app, now i open destiny 2, the controller lights in blue at the home button and solid green at the bottom, but doesnt work in the game , any button neither the joysticks, only works the home button that send me to steam when in press it

Sergio David Ballen Gomez sounds like one of two things arr happening. Either you enabled "Use Desktop Config" in GloSC or you didn't create a config for the shortcut that GloSC added to Steam.

I don't have any experience with SWTOR but I did some research and I think I know what the problem could be. I'm going to wager that Steam is getting stuck in the launcher (either SWTOR's or Origin) which is why the controls aren't working in the game. To get around this you'll need to use OSOL. You can use the second part of this video (kzfaq.info/get/bejne/rauFeth7p9ynaIU.html) where I explain how to use OSOL for Apex Legends. Otherwise, since it doesn't support XInput then you can make a separate Action Set for SWTOR in your Desktop Config and choose to not run SWTOR though Steam. Just run SWTOR like normal and switch to the second Action Set of your Desktop Config.

Robert Zabulonian I've heard of this issue before but I don't recall ever hearing about what the issue was. However, someone in these comments said that running Steam with Elevated Privileges fixes this. While I don't see this being a long term fix, it might be worth checking out to see if it would fix it. Then I would try just running GloSC with Elevated Privileges and seeing if that fixes it.

CriticalComposer thanks for the quick reply! I tried running both as admin but it didn't happen It's no biggie though! I've got a PS3 controller and I was just hoping this would help me not have to reinstall SCP, but at this point that's easier than trouble shooting this 😅 Thanks though

Whatever works for you. I think Steam Input (and, if necessary, GloSC) is worth troubleshooting but I would make extensive use out of the profiling aspect. If you just want a way to translate your DS3 commands into XInput then I totally agree with you.

CriticalComposer im going to keep using the steam controller for steam games, especially those with handy community configs ofc, but about the same amount of effort to plug in a ds3 for non steam, considering I have a laptop and not a stationary PC

sano m I'm gonna need a lot more info than that. What game? What OS? What shortcut are you running through GloSC? Does the game work normally? Is it Fortnite?

Hi CriticalComposer, Please refer this video link: kzfaq.info/get/bejne/adeAjLymu83QiZ8.html

Kehinde O Agreed, the dev did a great job with the application. AFAIK, it's the only way to play Destiny 2 and UWP games with the Steam Controller. I hope it works for your with your problematic games.

Im actually having alot of issues with this. I can't open up the steam overlay on my desktop. I keep seeing videos of people with touch menus but i have no functionality like that and I can't get it to work for bayonetta. Do i need to download vigem first? now ive tried it with mulitple games, when i click on the steam button after adding the "xbox controller" profile it just opens up the glosc logo but doesn't actually open steam overlay. Then when i go into game it uses the default steam controller config that you use when steam is actually close.

Kehinde Alright, I'm gonna do my best to help ya here. First of all, you don't need to install ViGEm since it gets installed in GloSC's installer. The issue with the overlay not appear sounds like one of two things. Either you didn't check the Enable Overlay option in GloSC or Steam isn't properly hooking into GloSC. The former is an easy fix but the latter could be anything. For starters, you could trying reinstalling GloSC or switching to the Stable branch of Steam. Once you get the overlay working properly then you'll have your radial menus. As for the Xbox Controller profile, I have no idea what is going wrong here. (This is a long shot) Are you deleting the Xbox Controller Instance in GloSC after adding the shortcut to Steam?

I'm not sure if you are aware, but the latest version of GloSC fixed an issue with the overlay not showing. I would definitely try the new version and see if you are still experiencing the same problems.

Feuerstern3001 Did ViGEm install correctly when you installed GloSC? Are the controls properly bound in the game? Is your configuration set up properly for the game?

SO what I gathered from testing is that when I launched GloSC for desktop "only" an virtual controller got connected and when I started Forza trough steam it disconnected but starting not trough steam it stayed. But I still didn't get Analog triggers bit that was because the desktop Instance was set to use desktop config which wasn't set to triggers so I changed it so it would use an extra config but now the virtual controller doesn't get connected

Feuerstern3001 It all sounds a bit odd but it sounds like you got it working on the end, which is good. Though I'm still a bit perplexed as to why it would use your desktop config when a program/game was run through Steam.

No I dont got ir running and I set it to desktop config because when I set it to extra config and I try and edit the config steam wont load the config window

Feuerstern3001 oh! Desktop config won't work because you can't use XInput commands through it. In GloSC, make sure that Enable Overlay and Enable Controllers are checked. Disable Use Desktop Config and then check Launch Game. Then could the UWP button on the right and select Forza. Give the shortcut a name(box at too of window) and save this then hit Add All to Steam. Steam will then reboot. Go to the new shortcut and edit your config to use XInput bindings then launch the shortcut. If you are doing exactly that then something else is messing with the controller. You'll need to figure out what program is hijacking the ViGEm output before it reaches Forza.

Make such that Xbox 360 Controller Support is enabled in Steam. If not then you might get multiple controllers showing up.

@@criticalinput the option is enabled

​@@maxilaccetta8141 I don't know at that point. GloSC's homepage states that multiple controllers could appear if this wasn't enabled but it doesn't have any troubleshooting other than that and I've never personally run into the issue. Normally I would direct you towards the GloSC Discord server but the dev has been gone for a long time now so there really isn't anyone there that could answer you question. Out of curiosity, does FIFA need GloSC? AFAIK almost every game will work just fine without it, with Destiny 2 being the only exception. If FIFA is on Origin (which I think it correct) then you could use OSOL to get Steam Input to natively hook into FIFA rather than using the GloSC workaround.

Which app? GloSC? You just download it from the website. alia5.github.io/GloSC/

Azyrion as it has a Steam version now, I would assume that simply adding blackdesert64.exe to Steam should work just fine. Just make sure that the "use desktop config in launcher" is checked (this can only be found in Big Picture Mode). Otherwise, you could make a GloSC shortcut without the "Launch Game" section checked. Then run GloSC through Steam and run blackdesert64.exe normally, like from the Start menu or a desktop shortcut or something.

adding the blackdesert64.exe to steam (manually and/or with glosc) doesn't work. Steam doesn't seem to recognise it being run. Also blackdesert64.exe cant be run manually it needs to be startet by the blackdesertlauncher.exe as that is where you login to the game. Maybe thats why it doesn't work well? As for your second suggestion it does work fine, just a bummer that I have to launch a different app first everytime but well.

Azyrion ah, I missed that point. Run the launcher through Steam. As long as you check "use desktop config in launcher" (which is usually checked by default) everything should work fine. However, if that doesn't work then putting the launcher in GloSC's Launch Game box should work too. You'll have to navigate the launcher with a mouse + keyboard -- or make an Action Layer for it -- but that should definitely work as a one-step solution.

so you mean creating a shortcut to blackdesertlauncher with glosc or manually through steam?

Azyrion try Steam first (I think that will work), otherwise run the launcher with GloSC.