Echoz
Published
Performance was flawless at 5120x1440 on max settings.
Previous issues have been solved. I'm able to edit controls more than one at a time without reloading. I have not yet tested if steering wheel FFB works.
Loaded up once but the game was stuck in a tiny square in the top left corner. Second time the same thing happened but the game was also completely frozen
Lots of issues using DXVK, including some random crashing, seemingly constant crashing on second start without deleting its directory in steamapps/compatdata. FPS with DXVK seems to directly depend on the resolution, where it runs well (144+ fps) at 640x480 all the way down to 3 fps on 2560x1440. I was able to run it faster at 2560x1440 once when changing the graphics settings. With PROTON_USE_WINED3D=1 the game runs all right at 2560x1440 with the lowest graphical settings.
With powerful hardware it can be playable
Resolution: 5120x1440
Ultra: ~20 FPS
Low: ~40 FPS
Lowering resolution to 3840x1080:
Ultra: ~35 FPS
Low: ~60 FPS
This was only tested in the starting area (bar).
Proton-7.1-GE-2 GloriousEggroll
Proton-7.1-GE-2
A little stuttering, likely from shader compilation. This only happened using DX12, with DX11 everything was smooth although performance seemed slightly worse when not compiling shaders.
The game locked up once as I switched to my browser before even loading into the game. This has so far been the only time this happened, switching in and out of the game has otherwise worked perfectly since.
Launch options:
PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr %command%
Never tried without these so not sure if they make any difference. Ray tracing was unavailable even with the DXR variable.
In the current state the game works perfectly (save for multiplayer) with the default version of Proton.
6.19-GE-2 GloriousEggroll
The game worked fine in single-player with regular proton 6.13, however multiplayer only worked with the GE fork.
I was running the game on ultra at 5120x1440 with HD textures, which should be no problem given my hardware, and it wasn't either in the beginning. However after playing for some time the frame rate got lower and lower, somewhat depending on context. What usually seemed to trigger this was switching in and out from menus, especially the map, but also loading screens, stores, etc. To temporarily remediate this I could switch the game from fullscreen to borderless and vice versa, but this would only work twice before the game became permanently choppy, sometimes experiencing frame rates lower than 20 FPS during gameplay and 6 FPS during cutscenes. What eventually fixed this was disabling the HD textures. I don't see much of a difference, and I'm now able to play the game for hours rather than 30-45 minutes like I was with them enabled.
I did experience some quirks with Ubisoft Connect/Uplay in the beginning. This seemed to just be the included version's fault, however. I had to delete my prefix to get it to start once, but as soon as it's updated it should work perfectly.
Okay performance at 5120x1440 on ultra settings. Could be drastically improved by lowering resolution or quality.
5120x1440 resolution leaves the HUD somewhat cramped up in what seems to be a third of the monitor width.
Some stuttering, frame rate not that great at 5120x1440 on ultra settings. Totally playable, though.
Setting the game to use DX11 and the right resolution/window mode can be somewhat troublesome initially and require a few restarts that may or may not reset your settings.
Multiplayer not tested on this setup although virtually all of my 889 hours have been in GTA Online on Linux. The game does require an insecure and non-standard networking setup for multiplayer to be stable and work with large sessions when using outbound NAT and a firewall, but I doubt this is specific to Linux/Proton.
It works like native.
Crashes sometimes, but might be due to mods. Saving frequently makes this mostly a non-issue.
The game is old and has its quirks. A lot of interactions in-game are tied to frame rate, so even if you add mods to deal with this you will have to occasionally turn on the frame limiter for certain things to work. For instance in water you will always sink if your frame rate is too high. Rhythm-based minigames seem to base timing on frame count, so if you're running at 300 fps you'll have to be 10x as accurate as you normally would. For the most part the game is enjoyable at a proper frame-rate, though.
Another thing that did not work without mods was my 32:9 aspect ratio.
The mod collection called "San Andreas Definitive Edition" contains a number of mods that will make the experience better on modern hardware without compromising the integrity of the story and overall experience.
Ran perfectly at 5120x1440 with the highest settings.
Full screen seemed to render the game at a lower resolution. Setting the game to 5120x1440 and windowed, then using my WM to put it in full screen made it look perfectly crisp.
In-game input seems flawless, but clicking on the map seemed somewhat inaccurate, making the first few missions that require you to set waypoints on your map a little annoying, but not at all impossible.
The game locked up about an hour into my gameplay. Although I only played a little short of an hour with this setup I've played all of my 58 hours on Linux and completed the game without any major stability problems before.
Not great performance at 5120x1440 on ultra, but likely very playable at lower settings.
ATC audio seems to be missing. Likely because it depends on a Windows language pack in order to do text-to-speech.
Logitech 3D Extreme Pro was recognized as an Xbox controller. This was likely my own fault as my user did not have permissions to read/write to its hidraw device. With r/w permissions to the hidraw device it was properly detected, but the throttle and rudder had to be mapped manually as they did not work with the default configuration.
Only tested on 5120x1440 with max settings, but the frame rate is anywhere from acceptable in areas with few buildings to borderline unplayable in large cities at low altitudes. When flying from JFK towards Manhattan performance gradually got worse, and probably ended up being the worst in Manhattan at around 10 FPS.
I also experienced extreme stuttering at times. Sometimes every 10-15 seconds the game would lock up entirely for seconds at a time. While this was annoying, gameplay was also paused, so it's not necessarily game-breaking, at least not in single-player. This seemed to happen less in third person than first.
During the download the game crashed at least a couple of times. During gameplay everything seemed stable.
The initial download is extremely slow and requires you to be in-game. Not sure how this affects the 2 hours played refund limit, but it's something to keep in mind if you just want to test it.
Download seemed to mostly run at around 50 Mbps on my gigabit connection.
Runs okay at 5120x1440 on max settings.
Mirrors don't work
Some stuttering when loading in and entering new areas. Likely shader compilation. Performance is generally not great, but it's about what you'd expect from an alpha.
I ended up using Proton because the native version didn't work for me. The experience is flawless.
The current issues can make playing the game quite frustrating if you're not doing it with the intention of testing.
Requires WINEDLLOVERRIDES=dxgi=n,b in the launch options in order to run.
Full screen does not return to full screen if you switch out of the game. Workaround (alt+enter twice) is required, with high likelyhood of a crash.
Game seems to crash somewhat at random, but is playable and not a huge problem due to pretty frequent autosaving.
I'm using a custom build of proton from Brendan from CodeWeavers (mrpippy on GitHub): https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644542391
I've covered in more details the issues I've experienced here: https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644836348
Not sure if the game still crackles, but it used to after some time. Probably a good idea to play the game with PULSE_LATENCY_MSEC=60
Some odd shadows, objects not being rendered immediately. Nothing that keeps you from enjoying the game.
To play at resolutions higher than 1080p you need to run the game in windowed full screen. I ran the game with -borderless -w 5120 -h 1440 in the launch options, but I had to apply the resolution through the menu.
Run with WINEDLLOVERRIDES=dxgi=n,b
Overall decent experience out of the box
The game sometimes slows to a crawl, but this usually happens after a good while of playing, so if you can live with having to restart a few times it's no problem.
For the most part it runs like native
Mouse sensitivity was fairly high. Adjusting the settings made no difference, but I'm not sure if they do on Windows either, since there is no setting that specifically mentions "mouse"
Save games just don't work in this game. They only save part of the state so there's a good chance your train will mysteriously malfunction or you'll be stuck waiting for a signal that's never gonna let you through. From what I heard this is the case on Windows, too.
The game did dip under 60 fps sometimes, usually only at large stations. I can't compare to Windows as I haven't tried that, but given how the game looks it's not something I'd expect to be very taxing for my hardware.
There's also some stuttering when loading new areas. Especially when loading into an area for the first time. The stutters are pretty significant, but if you just look around you until it ends after loading in it's not really something you will notice during gameplay.
It has crashed a couple times, but fewer times than I've gotten stuck because of game bugs regarding signals and save games, which is not Linux specific.
Tried different Proton versions, 7, 8, experimental, GE. Tried both DX11 and DX12
Completely unplayable at 5120x1440. About 8 FPS at max settings, 16 at the lowest. Even at 1080p it performed poorly. At 1024x768 it ran at 500 FPS.
Only tested the demo
