Mercineri935
Published
Ray Tracing cannot be enabled, neither with standard Proton or ProtonGE
Running any newer version of proton, the game would crash on startup, using Proton 7.0-6 I was able to get into the game without issue.
PULSE_LATENCY_MSEC=90 %command%
Cannot get audio to work properly no matter what runner I use, previous reports stated PULSE_LATENCY_MSEC=90 was able to resolve, but has had no such effect on my game. PULSE_LATENCY_MSEC seems to have no effect on the process at all as raising this value does not cause the audio latency to increase at all. I was able to test in Lutris games and noticed that PULSE_LATENCY_MSEC is respected there in a few games, but not on several steam games including this one.
PULSE_LATENCY_MSEC could resolve the issue- but I cannot know as the game will not be effected by it, despite confirming having that passed to the process. Audio issues make the game rather unpleasant to play at the moment as a result.
PULSE_LATENCY_MSEC=90 %command%
Cannot get audio to work properly no matter what runner I use, previous reports stated PULSE_LATENCY_MSEC=90 was able to resolve, but has had no such effect on my game. PULSE_LATENCY_MSEC seems to have no effect on the process at all as raising this value does not cause the audio latency to increase at all. I was able to test in Lutris games and noticed that PULSE_LATENCY_MSEC is respected there in a few games, but not on several steam games including this one.
SteamDeck=1 %command% -nobattleye
In game depth of field set to high causes a weird outlining effect, reducing to normal resolved
GTA Online is borked as Rockstar explicitly does not permit Linux users to play due to cheating concerns.
For Debian I was unable to connect to the game servers without running the following:
sudo sysctl -w net.ipv4.ping_group_range="0 1000"
Replace 1000 with the group ID listed after running "id -g"
If you want to make it permanent so you do not have to run after every reboot, add " net.ipv4.ping_group_range = 0 1000" to /etc/sysctl.d/99-local.conf and you can do this by running "sudo nano /etc/sysctl.d/99-local.conf"
Note that doing so could have security implications regarding ICMP, so DYOR before making it permanent.
gamescope -f -r 144 -w 3840 -h 2160 --force-grab-cursor -- %command%
Game appears to work without any issues, good performance on my hardware & Nvidia
Game appears to work fine, I use a 144 hz monitor and get relatively smooth frames, could be a bit smoother with gamescope.
Seems to occur when riding horse, need more testing
Gamescope is currently borked, needs more testing. Currently crashes at or just before main menu with gamescope enabled. As a result cannot test gamescope for smoothness or HDR support.
VKD3D_FEATURE_LEVEL=12_2 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 PROTON_NGX_UPDATER=1 VKD3D_CONFIG=dxr11,pipeline_library_app_cache %command%
If you want to use the DLSS mod, use the REFramework here https://github.com/yobson1/REFramework/releases/tag/empress
Make sure you download the upscaler plugin dll (https://www.nexusmods.com/site/mods/502) and the dlss dll and place them in the games directory.
And also use the modified launch options:
VKD3D_FEATURE_LEVEL=12_2 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 PROTON_NGX_UPDATER=1 VKD3D_CONFIG=dxr11,pipeline_library_app_cache WINEDLLOVERRIDES="dinput8.dll=n,b;nvngx_dlss.dll=n,b;PDPerfPlugin.dll=n,b" %command%
DXVK_ASYNC=1 gamescope -f -r 144 -w 3840 -h 2160 --force-grab-cursor -- gamemoderun %command%
Under DX12 using Proton Experimental there were an odd texture glitch or two that were not present on DX11, not noticing much more as I progress.
Heavy FPS drops under DX11 using standard Proton 9.03 and Proton GE 9-21, DX12 was even slower.
Issue is mostly resolved under DX12 using Proton Experimental, higher average FPS
Appears to be unoptimized, but may improve over time
gamescope -f -r 144 -w 3840 -h 2160 --force-grab-cursor -- %command%
Game works out of the box and works well with gamescope using my current launch options
