askiiart
Published
Sometimes has artifacts when inspecting a phone/tablet, or at the beginning of the intro
Occasional stuttering
Can't speak to performance on lower end hardware, or how it performs to Windows, but works perfectly for me.
Works perfectly with Proton 8+, except on Arch where you need Proton 3 which also has high mouse sensitivity
In old versions of Proton, the mouse sensitivity is very high in New Vegas
Sometimes would become extremely slow for a bit or crash after switching from and back to GGST
Somewhat decreased FPS, particularly noticeable on low spec systems ofc
Also just fails to start up sometimes, in that case just close and reopen it.
PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1 %command%
With gamemoderun, it wouldn't launch at all for me. These args were needed for it to launch without immediately freezing on a black screen, and switching to Proton 5.13-6 fixed audio in cutscenes.
The "engine control" axis did not work (Logitech Extreme 3D Pro joystick), USB Xbox One controller worked perfectly.
Works perfectly, except for some controller issues
Windows performance on Quality was roughly equal to Linux performance on Low
Needs a more beefy GPU (RX 580 is decent on low).
Also, not a Proton problem, but in general something to keep in mind is that unless you have a rather powerful GPU, when moving the mouse to move the camera, it slows down significantly for a second.
Very minor graphical issues where it loops, could very well be issues with the game itself though
Works great with GE-Proton9-10.
Note: This game seems to have significantly worse performance when running in a VM, with worse performance overall and significant slowdowns when moving the camera, with both a Linux and Windows guest. Running on the host, though, it works great.
Sometimes had minor artifacts when at the loop, but could be an issue with the game itself. Regardless, very minor
Note that this has significant performance issues, both on Windows and Linux (though worse on Linux), if running in a VM with PCIe passthrough. It's definitely playable, but I'd advise against running it in a VM.
Works great on the host, though. (also, takes up ~1.5 GB of RAM)
Throws "Fatal error!"
When started, after a while it displays a window with the title "The UE5-PirateFS Game has crashed and will close", the text "Fatal error!", and a button saying "OK", then the window closes after a minute or two.
Native, and works great!
Seemingly randomly, when started, Team Fortress 2 will be offset by a blank space the size of window controls at the top. This is fixed by focusing to another screen and focusing back, though it sometimes takes a few tries.
Need to replace libtcmalloc_minimal.so.4 and disable Steam Input, after tinkering it runs perfectly
libtcmalloc_minimal.so.4: Does not launch, gives error about libtcmalloc_minimal.so.4. Can be fixed by replacing libtcmalloc_minimal.so.4 in TF2's bin folder with a system one, either via a symlink or by copying it to the bin folder. It could need either the 32-bit or 64-bit version.
e.g. on Fedora 38 sudo dnf install gperftools-libs.x86_64 or gperftools-libs.i686, then cp /usr/lib/libtcmalloc_and_profiler.so.4 {tf2}/bin/ or cp /usr/lib64/libtcmalloc_and_profiler.so.4 {tf2}/bin/
Additionally, Steam Input needs to be disabled.
64-bit is borked
%command% -nojoy -nosteamcontroller -nohltv -particles 1 -precachefontchars -noquicktime
64-bit doesn't launch. When starting it with ./tf_linux64, it throws error while loading shared libraries: libmimalloc.so: cannot open shared object file: No such file or directory. After installing mimalloc-devel, it gets to AppFramework : Unable to load module engine.so!, which is the expected behavior; it's what it should do given it's not running in Steam Linux Runtime 3.0. However, running it in Steam still causes it to fail to launch and nothing is displayed.
(tested on Fedora)
Works perfect - the only bugginess is tf2 itself
Occasional graphical glitches at boundaries between different areas
