This controller config assumes that the default Quake keybinds are in place. If you have additional keybinds that's fine, but the keys for the default controls are assumed to be doing the default actions. If you need the controller to use non-default keys for its various actions, then you'll have to change the controller config (which we won't talk about here).
Usually you can clear all existing Quake keybinds and restore the defaults by using "Reset to defaults" (or some similarly-named option) in the in-game options menu. Although note that this will also reset your mouse sensitivity, game volume, and screen gamma settings.
Some modern Quake engines may change the defaults however. I haven't tried to check them all; I do know that Quakespasm for example still supports the original keybinds (with some additional ones) in its defaults, but Mark V has defaults that change some things compared to the originals.
A reliable way to get the necessary default keybinds is to download the default keybinds config, put it in the "id1" folder of your Quake installation, and then do "exec sc.cfg" from the Quake console.
Note about missionpack 1: The "MP1 WEAPONS" button in the options touch menu changes the Steam Controller inputs to support the missionpack 1 weapon set. This does not create new keybinds in your Quake configuration. It simply assigns some inputs of the Steam Controller to press the 9 and 0 keys. You must have keybinds for the laser (bind 9 "impulse 225") and the hammer (bind 0 "impulse 226") in your Quake configuration. These are in the default keybinds for missionpack 1, so if you do "Reset to defaults" while that missionpack is active, you will get these binds set up. They are also in the "sc.cfg" file.
If you hold in the right grip and press the "X" controller button, that will send an "i" keypress to Quake. Also, if missionpack 1 weapons are not enabled, then right grip + "Y" will send an "o" keypress. These keys don't normally do anything in the default Quake configuration; they're included here as hooks for any additional keybinds you might want to have handy. For example, if you're using the Mark V Quake engine, you might want to bind one of those keys to do "load auto_save_0" to load the most recent Mark V autosave.
If you have mouselook permanently enabled in your Quake configuration, that's good! However, if you don't, there's also a selection in the options touch menu that can be used to toggle mouselook on/off. So even if you're using the original GLQuake you don't necessarily need to do any Quake config modifications to get permanent-on mouselook.
Ideally you'll want to use a Quake setup that has support for XInput gamepads (like the 360 controller). This provides a "left joystick" input that can be used for movement and for menu navigation. I'm not sure how common such support is; I do know that the latest Quakespasm has XInput gamepad support out-of-the-box with no extra configuration, if you use the "quakespasm.exe" executable. DarkPlaces also has XInput support but I don't know the details. I wouldn't be surprised if there are ways to use XInput gamepads with other Quake engines, maybe even in the original GLQuake, but I haven't looked into that yet since Quakespasm works for me.
Anyway, if your Quake engine supports this, it means that you can use slightly simpler "joystick move" variants of this Steam Controller configuration. If your Quake engine does not support this, no worries. There are also non-joystick-move variants that will work for you.
If you're going to be streaming Quake to your TV screen then you probably want the status bar, menus, and console text to be bigger.
When using GLQuake 0.95 (the version that Steam installs), unfortunately you can't do much about the size of the UI beyond just reducing the overall video resolution.
However if you've replaced your Steam Quake executable with some other Quake engine, or if you've added another Quake engine to Steam as a "non-Steam game" to launch, then you can change the size of UI elements independently from the video resolution. The actual adjustment to make depends on the Quake engine you're using. If you're using a Quake engine among those in the drop-down menu below, you can use that widget to see the relevant setting(s) to use for that engine.
Add -conwidth and -conheight options to Steam's "launch options" when launching GLQuake. Values smaller than your video resolution will result in larger console text and menus/statusbar. Assuming you have a 16:9 aspect ratio TV (e.g. 1920x1080 resolution), try: -conwidth 480 -conheight 270, or maybe -conwidth 320 -conheight 180
Change the "Scale" setting in the Quakespasm options in-game menu.
Experiment with settings for "Autoscale" in the Mark V options/preferences in-game menu.
Change the "Console Size" setting in the DirectQ user interface options in-game menu. (This setting can only be changed if you are using a resolution above 640x480.)
You can set the vid_conwidth and vid_conheight console variables for DarkPlaces. Values smaller than your video resolution will result in larger console text and menus/statusbar. Assuming you have a 16:9 aspect ratio TV (e.g. 1920x1080 resolution), try vid_conwidth 480 and vid_conheight 270, or maybe vid_conwidth 320 and vid_conheight 180.
Change the "2D Mode" settings in the FTE video options in-game menu.
Change the "Console Size" settings in the Qrack video options in-game menu.
Disable "Automatic Scaling" in the Engoo view options in-game menu, then change the "Graphics Scale". (However this does not affect console text size.)
Change the "Status Bar Scale" in the Qbism super8 video options in-game menu. (However this does not affect console text size.)
) except where indicated otherwise
Linux Desktop Integration
Singleplayer Starter Pack
Steam Controller Quake
Gameserver Scripts
quakesounds
QL pk3 Support in 7-Zip
MeshTex GtkRadiant Plugin
Birdseye Map Overviews
QSmack Quake Admin