steam-deck-tools VS GlosSI

I use Steam Deck tools for windows for all my deck buttons and shortcuts https://github.com/ayufan/steam-deck-tools

It's friendlier than it looks! First download the latest Steam Deck Tools release from GitHubsteam deck tools, then install RTSSrtss so the overlay and quick menus work, and optionally follow thisvrr guide to get VRR working. Make sure they're all set to run on startup and you should be good to go. The options all live in the task bar, and you can easily toggle between desktop/controller mode and different fan profiles, refresh rates, etc. It takes some fiddling around to get perfect but it has most, if not all, of the functionality of the native OS

Are you sure you are actually using Windows on the deck? Because except for getting the controller working in 3rd party launchers (which needs this single tool: https://github.com/ayufan/steam-deck-tools) - there were absolutely NO errors / hurdles at all. Everything just works as expected.

I prefer Steam Deck Tools for Windows https://github.com/ayufan/steam-deck-tools this is free, and adds pretty much full Stream Deck functionality to Windows. Steam Deck shortcuts for bringing up the windows keyboard, closing apps, alt tabbing, bringing up an overlay, using the overlay to choose frame rate and scaling options, etc, etc.

Steam Deck Tools I launch Diablo hold start and swaps to controller mode.

Install https://github.com/ayufan/steam-deck-tools This gives you control of fans, power limits, controller/mouse mode, etc. Its an all in 1 tool

And I use Steam Deck Tools for Windows for everything else and it works great https://github.com/ayufan/steam-deck-tools

Try installing glossi on your host system and running it though that https://github.com/Alia5/GlosSI

GlosSI

If it’s a “non-steam” game, like Diablo IV, I use https://github.com/Alia5/GlosSI to act as the non-steam game for the launcher.

Download GlosSI installer from https://github.com/Alia5/GlosSI (when asked to during installation, install ViGEM driver as well)

Check out GloSI and it's Playnite extension, might be easier to assign input per game from Playnite

There are apps that act as middleware between Steam and these 3rd party launchers that can help. I use GlosSI.

You simply can't because there are no Drivers for it and Steam.exe is acting like the driver itself so that even projects like https://github.com/Alia5/GlosSI are piggybacking on Steam.exe's existence. You may try combining that GlosSI + SteamCMD (command line version) for a minimal impact on your system but you can't avoid installing Steam.

Now I assume you are running it through steam to make use of steam input. The workaround to run the launcher independently and still use steam input is to use glossi . Here’s a YouTube video on how to set it up: youtube .