LatencyFleX VS wayland-keylogger

Installing LatencyFleX on multiple different games and Proton versions was cumbersome to me. I created an install script to do that for you. Tested on Arch Linux, should work on any distribution, provided LatencyFleX is installed on the system beforehand.

Find liblatencyflex_layer.so, latencyflex_layer.dll, latencyflex_wine.dll from extracted https://github.com/ishitatsuyuki/LatencyFleX files

No and it has a vendor agnostic alternative that works better: \ https://github.com/ishitatsuyuki/LatencyFleX

Strangely, a reflex alternative is available on Linux for AMD cards (third party, open) https://github.com/ishitatsuyuki/LatencyFleX Nvidia and AMD could both implement that as a standard, but NVidia is not keen on standards, and AMD is oblivious.

If you're on linux there's LatencyFleX: https://github.com/ishitatsuyuki/LatencyFleX

https://github.com/ishitatsuyuki/LatencyFleX here you go

And this depends on what actually reflex is and doing - Nvidia love to take a standard api and giving it a brand name and strut around like they invented something new. For example, https://github.com/ishitatsuyuki/LatencyFleX seems to suggest they get similar advantages "just" using the submission timing interfaces already available in the standard graphics APIs, I wouldn't be surprised if reflex is "just" an implementation of that, possibly with an API designed to be a bit easier to integrate in game engines than the gamedev doing it themselves.

As long as you have the most recent driver version and are on Proton Experimental, you shouldn't really have to do anything. You are on a VERY old Proton-GE build, which does not include DXVK 2.0, so that's probably why you're having issues. Maybe look into LatencyFlex, but again, with these bans going around, use at your own risk.

Use LatencyFlex instead. However it might be a bit tricky to get it working. I've not yet had success using it in Overwatch 2.

Intercepting inputs meant for other apps is easy and it's already been done via LD_PRELOAD.

And all of this just for supposedly better "security", that can easily circumvented with trivial attacks.

Not in the same sense that there's a keylogger included with Windows, no. It's that it's easier to do on Xorg as opposed to Wayland. This isn't to say that it's impossible, however.

You can have keylogger on Wayland also without root priviledge. It's trivial: https://github.com/Aishou/wayland-keylogger

> you can still deliver different experiences at runtime — but you’re not likely to have the superuser privileges needed to run a leylogger or read ~/.ssh/id_rsa, etc, at that point.

Keyloggers are trivial to do in userspace Linux via LD_PRELOAD attacks[0], and typically your user account has permission to read ~/.ssh/id_rsa.

[0] https://github.com/Aishou/wayland-keylogger

I have read that bare Linux is totally insecure (https://github.com/Aishou/wayland-keylogger) unless you use some means of sandboxing. That's why I have been reading a lot about firejail, AppArmor, Tomoyo, etc.