Maybe look if there are predefined set of user created controls in Steam Deck. Sometimes users create alternative control schemes optimized for controller setup. Or do your own customization with the Steam Input. That won’t make you better at aiming, but maybe you can address some pain points this way.

At the moment I am not using your project, but I think this has its place even with Flatpak available. Because archiving Flatpaks is not as easy as arachiving AppImages. In example there are programs (emulators) I use Flatpak for, but from time to time I also archive a version of the official AppImage.

And sandboxing comes up as a point everytime people talk why Flatpak is superior to AppImages. So tackling that point is good effort to me.

Edit: Think about renaming the project. It’s not very memorable and also the ai in the name suggests it has something to do with artificial intelligence.

deleted by creator

It’s like coming from gamepad to arcade sticks, when playing fighting games. There is nothing else you can do, other than train and play and git gud. Try the original DOOM, and I mean the first DOOM from the 90s. You don’t have to aim up or down, only left and right and its not precise as todays shooters. Maybe play that on a lower difficulty and see if you can get used to it.

Overwatch 2, which is Free To Play, has a training area and courses for heroes you can try. Take the simple Soldier, which is your average FPS character, and maybe you can get used to the controls. You don’t have to play online, just try it out against bots and do these training courses. Maybe that helps.

If you play such a shooter every day, DOOM, and others, than you will get used to it and build up muscle memory. Actually I find it exciting to learn new stuff like this and am a little bit jealous. ^^ Reminds me back when I came from console to PC and had to learn how to play shooters with mouse and keyboard.

Edit: Your age 30 is fine. Age is always an excuse, but mostly not true. I’m also from the 80s and grew up with 8-bit and 16-bit. Yet I learned how to play with arcade sticks and mouse and keyboard in addition to controllers. I’m 42 now (and proud of it). My biggest advice is, play every sort of game, not only you are comfortable with. And do it every day. git gud is the only way.

deleted by creator

After 12 thousand years.

That’s interesting. But man, the project name is not very memorable.

It is not irrelevant to me and I made it multiple times clear. Its a suggestion by me, regardless of what terminology you use or the team uses. The desktop edit change is a big change which I suggest not to do for a year. Only bug fixes and small changes that enhance and improve usability. The desktop edit change is a huge change for the developers and for the end user, with lot of background changes to make it work correctly, with lot of fixes after it.

Something that complex is not a small change and is not irrelevant for the topic I brought up. I made it multiple times clear now, I don’t know why you are still act like this. It’s not a definition of a term we are trying to agree, I don’t care the term.

I don’t agree with you and explicitly listed it in my first reply as an example of what I consider a big change.

You misunderstand me. They can write new code and be ready when the bug hunting phase is over. The end user only gets bug fixes. Later they can backport any new feature after the phase.

https://wiki.archlinux.org/title/Installation_guide

I guess you meant this as a joke, but for clarification, I meant no big changes such as new desktop edit mode. I wish the team would just focus of bug fixes and enhancements without introducing new elements or changing things up in a big way like this.

deleted by creator

deleted by creator

deleted by creator

I wish the team would just spent an entire year of bug fixing and refining user experience without adding new features or making big changes such as the new desktop edit mode. Don’t get me wrong, this is super exciting too, but for the complex nature of KDE it would be good if they keep a bit of focus after a major release.

It just came to my mind, that WINE not only stands for Wine Is Not an Emulator, but also could be interpreted as: WINdows Emulator.

1. I have to run OBS separately, before gaming or when I ant to record something while I am playing already.
2. Configuration of the settings. While I found good settings, its still complicated for most people. Especially on Wayland (a Linux thing).
3. When I want to capture a game, I have to specifically run the game and select in OBS to capture this window. Or capture entire screen.
4. I still can’t use AV1 for recording, but I think that I managed to set VAAPI recording set to my GPU? I am not 100% sure.
5. The flexibility of recording and organization in the way Steam does it is way superior to any external software and custom configuration of it. With OBS I have to rename files and organize things manually, while these are done automatically for each game in Steam.
6. Besides Steam has background recording too, not just on demand manual recording on button press. Think of Nividias Shadowplay. With OBS I have to start end end recording manually.
7. While we play we can add specific markers to the timeline with hotkeys. OBS doesn’t have that.

OBS is clunky and complicated to me. The Canvas and Output resolutions are separate, which confuses me the hell out of it. I only experimented with some settings so far to record gameplay (after my new PC installation) and need to see how this works out. But if I change settings to record something different, then I have to configure it again to record gameplay. Also to use Hotkeys, I have to allow hotkeys to be used globally in my system (which I don’t want to otherwise). Because of Wayland and how it works.

All in all its must simpler and superior to do this in Steam itself now. For other use cases, I will still keep OBS, its not bad, just not straightforward for daily game recordings. But I can add other software and games to Steam and can use it with Steam Recording too (if the overlay works there).

As others noted, this has background recording functionality and manual on demand recording as well. I have used manual recording software and still have OBS installed for any use case. But having Steam Recording builtin is very convenient.

1. configuration, its much easier to setup than any other solution if you care to get best quality and performance
2. convenience, integrated makes it easy to setup and use, with additional features, plus its such a fiddling to record specific windows when using external software such as OBS or similar if I don’t want to record entire screen in windowed or fullscreen mode, especially on Wayland
3. performance, Steam records the raw game footage from your video card and therefore has the best possible quality and performance one can get out of video recording
4. no overlays, Steam will only capture the game footage without fps indicator or other stats and without overlays or menus from Steam, other software would just record everything visible
5. timeline, resulting video is raw footage and is not encoded into a video file format for output and not useable before output to video (mp4), we can add timestamps with hotkeys while playing to mark specific points in recording, then we can mark start and end points or select certain parts in the timeline to save or export it
6. share, it has multiple sharing functionality besides saving to mp4 video file format

All of this is builtin and works the exact same way regardless of operating system and hardware (independent from cpu and gpu and os). No one needs to study hardware and software in order to configure it in the best possible way. If you used this on Windows, its the same on Linux, no dependency of recording software.

This is a much bigger deal than just recording footage with gnome-screenshot.

Its huge for me, because in Linux I can only record through OBS. And OBS is suboptimal, compared to a builtin solution like this. On Steam Deck I used the plugin too, but had to remove it again, because the plugin system stopped working.