libstrangle VS LatencyFleX

Mangohud (GOverlay), libstrangle, gamescope. Pick your poison.

#!/bin/bash PREFIXES="$HOME/.local/share/wineprefixes" mkdir -p "$PREFIXES" export WINEARCH=win32 export WINEPREFIX="$PREFIXES/World of Horror" #rm -rf "$WINEPREFIX";exit hash xmlstarlet 2>/dev/null || { echo >&2 "Program requires xmlstarlet but it's not installed. Aborting."; exit 1; } hash strangle 2>/dev/null || { echo >&2 "Program requires libstrangle but it's not installed. Aborting."; exit 1; } [[ -f ~/.config/monitors.xml ]] || { echo >&2 "Program requires running in Gnome (to get the resolution in a compatible way with both x11 and wayland). Aborting."; exit 1; } RES_X=$(xmlstarlet sel -t -v '//logicalmonitor[primary="yes"]//width' ~/.config/monitors.xml) RES_Y=$(xmlstarlet sel -t -v '//logicalmonitor[primary="yes"]//height' ~/.config/monitors.xml) #cd to the script dir if executed from outside GAME_PATH=$(dirname "$(readlink -f "$0")") cd "$GAME_PATH/WOH" wine reg add "HKCU\\Software\\Wine\\X11 Driver" /v "GrabFullscreen" /t REG_SZ /d "Y" /f wine reg add "HKCU\\Software\\Wine\\X11 Driver" /v "Decorated" /t REG_SZ /d "N" /f wine reg add "HKCU\\Software\\Wine\\Explorer" /v "Desktop" /t REG_SZ /d "World of Horror" /f wine reg add "HKCU\\Software\\Wine\\Explorer\\Desktops" /v "Default" /t REG_SZ /d "$RES_X"x"$RES_Y" /f hash strangle 2>/dev/null && { echo >&2 "Vsync on."; strangle 30 -v 1 wine worldofhorror.exe; } hash strangle 2>/dev/null || { echo >&2 "Libstrangle (https://gitlab.com/torkel104/libstrangle) is not installed, cpu might run too hot."; wine worldofhorror.exe; }

libstrangle got broken too and it's fully open source.

As written, your suggestion is unhelpful. The name of the project that provides the strangle command is libstrangle. Without that full name (or better yet, a link) it would be darn near impossible to find.

If you're comfortable with terminal use you could also try https://gitlab.com/torkel104/libstrangle

Libstrangle. The options for it, at least for vsync, seem extremely similar to Mangohud's settings in GOverlay, so this may be doing the exact same thing.

https://github.com/milaq/libstrangle with this you can limit the gpu to run an easy 45 fps. The monitors Hertz rate you can set in Linux, depending on what the screen will be capable of.

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.