linux-cachyos VS LatencyFleX

The Arch derivative CachyOS[1] has ZFS-enabled kernels by default. And their repos can be added to existing Arch installs[2], so I've found this a nice way of working around the non-ideal state of ZFS integration in Arch. (Plus their kernel choices have other interesting features.)

[1]: https://cachyos.org/

[2]: https://github.com/CachyOS/linux-cachyos#cachyos-repositorie...

You can also use the CachyOS repos which have packages compiled with LTO as well.

Yes, here's the GitHub issue: https://github.com/CachyOS/linux-cachyos/issues/82

in regards to that link, it looks like that person was running a cachyos kernel, ive never ran this kernel though but again any one of these kernels should be better than the default kernel.

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.