New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GTFO (493520) #3834
Comments
Hello @beardstorm, can you check if the game runs better with mesa 20.0.x or git master from a mesa PPA like oibaf or kisak-mesa and using the RADV/ACO render path? Support for mesa 19.3.x has ended upstream, and issues with RADV/ACO in the older driver version are not particularly interesting because it is not enabled by default and no more fixes will ship for 19.3.x. |
Hello @kisak-valve, thanks for the quick reply. I have followed the instructions here to install kisak-mesa. If that is what is applied by setting launch options to How come the mesa support for 19.3.x has ended? |
Follow-up question. How come RADV/ACO is not mentioned among the Proton runtime configuration options? |
Because 20.0.x is out and 19.3.x has run its course. |
I would just like to add that using the system installation of wine (mine was version PS: Now the game even works with 5.8-GE-2-MF!!! (have not tried 5.11-GE-1-MF) Even though I have lost my own logs from back when the game did not launch, I remember comparing my logs to @beardstorm's and the exception at line 243: System InfoGPU: GeForce GTX 1650/PCIe/SSE2 |
After applying settings the video freezes (it plays background music, effects when you hover over a button, etc.) and it rarely happens when going into video settings. Is this happening to anyone else ? I used Proton 6.3-7 |
So, the game before the 1.0 update used to run at 144fps with everything set a very high for me, since it the update dropped two days ago I'm running at ~30fps... I'm wondering what this could be and how I could debug it; does anyone has any tips on how I could debug the root issue? |
Also, @kisak-valve could this be considered regression as the game's performance is reasonable if not the same with |
Hello @wizardlink, in general, unwanted behavior introduced by a game update can't be investigated as a regression on Proton's side because a Proton dev can't bisect changes in the game's code. That said, please add |
I'm also experiencing performance problems using Proton compared to windows. System Information
|
I get very similar logs to @CytexalMika If I go into a mission it is typically fine, I usually get 60fps and when I use radeontop, I use most GPU utilisation between 50-70% for most things. However, if after that I go into a second mission the fps drops to 30 and the GPU utilisation maxes out to 100%. System InformationDistro:Manjaro Linux Issue occurs in both: Proton version: 6.3-8 and Proton Experimental |
I have similar issues as @ahtoms and @CytexalMika . Before the update performance was fine, after 1.0 it has degraded significantly. Other people I've played with are on Windows and don't report having the same issues. System Info:Disro: Pop!_OS 20.04 LTS (64 bit) |
Sorry for my immense delay to answer you @kisak-valve. Yeah, I understand that, I just can't see another label fitting this better and wanted to understand the process; thanks for the clarification! Report
Also, for anyone else having performance issues: Do use |
As a quick test, can you see if disabling MangoHUD and gamemode has a significant influence on the game's performance with newer Proton? I wouldn't be surprised if there's no effect, the request is just to remove them as extra factors. |
@kisak-valve I am not using MangoHUD but the ingame FPS counter, I have tried it with and without gamemode and I still get these drops. |
Alike @ahtoms, disabling FeralInteractive's gamemode and MangoHud (plus enabling ESYNC again) did not affect in anything noticeable, I can generate a new log if you prefer without the usage of these tools, not sure if it's cleaner for you and the team to analyse. |
@wizardlink I had just tried it with Proton 5.0-10, There was no improvement. Some reports on protondb are starting to corroborate that when reloading from checkpoint/dropping to another mission after trying one before it/or joining midgame, it will trigger a significant FPS drop. https://www.protondb.com/app/493520 I strongly suspect there is some oddities with shaders being sent to the GPU. |
Intriguing, with If you do suspect it's shaders you could clean them and try again, perhaps allowing the background processing of the same could help? Though I'm unsure if that setting just means it can download pre-compiled shaders while the game is running. |
I am also getting this issue in GTFO. It seems to be related to an extremely similar problem I get in Battlefront II: #3971 (comment) |
Having also the same issue. Whenever I change a graphic setting or change the window resolution, game drops to 20FPS, happens when I lose and have to restart the game. If I don't have to restart or change any settings, game is 70/80FPS all maxed out on 1440p. |
Can confirm, seeing exact same issue. Framerate gets halved every time I press ESC for the menu or die/reload level. |
New rundown/update, it's very clear to trigger a slowdown now. You simply just need to start the B3 mission and you'll find that you get between 10-20 FPS. There seems to be something quite intensive being ran on the GPU on this mission that I am uncertain about. |
Well... it appears that if I run the game with the following environment flag |
Hello @ahtoms, please copy your system information from Steam ( |
Hi @kisak-valve, you can refer to the following: https://gist.github.com/ahtoms/f1426d6c10d7a531125bd785b7e12fc9 |
I'm really considering switching to an AMD GPU. I have a 3070 since Jan 2021 and bought it so cheap but I might sell it and just buy an AMD one. I didn't test the new update but sometimes it happens on Windows too. I had my FPS drop from reloading the level after a checkpoint door. |
Freezes on the Steam Deck while loading, or immediately after loading is complete, on most expeditions. Sometimes it crashes back to the OS, but other times it seems to hard lock the deck and it needs to be forcibly power cycled. |
@absolom Are you still able to reproduce this? It seems on Steam Deck Beta on my side. |
Yes, I am still having the same issue. I turned on Steam Deck Beta, validated game cache, and configured it to use Proton Experimental. Same behavior. This is rundown 7.0 still. The "EVAL" sector of the rundown runs perfectly. The "A1" sector I was able to get through playing with friends with one crash and one near crash. The "B1" sector crashes every time during loading (while dropping down into the level). |
I never found a solution for GTFO using 8GB of my VRAM (3070) and dropping FPS like hell whenever I reloaded from a checkpoint but I found that setting the texture size to "half" and limiting my FPS to 70 with DXVK_FRAME_RATE, only takes 4 or 5GB of VRAM and it's super smooth, frametime is a flat line, even comparing the 100FPS I got without setting the frame rate cap and the 70FPS capping (I have a 144hz monitor), 70FPS looks and feel way smoother than 100FPS. |
I've come back to trying GTFO again on my Steam Deck. With the latest version of the game, running on lowest settings, I no longer have the issues that I was encountering with rundown 7.0's B1 sector. Seems to be working well now. |
I get random system freezes and game crashes with all the logs ending in |
Compatibility Report
System Information
I confirm:
Symptoms
The game simply will not start using any of the tried Proton versions. The game will briefly show an Unity crash handler and then close.
Reproduction
Launch the game using the hardware and drivers provided in System information.
Proton log
Workarounds
I managed to get around the launch crash with OpenGL-based wined3d renderer by using launch options
PROTON_USE_WINED3D=1 %command%
. This did however come with severe rendering issues in the main game. 2D interfaces like the menus and the game HUD worked fine. Would you prefer if I opened a separate issue for using wined3d?I managed to get it working properly with the LLVM compiler framework by using launch options
RADV_PERFTEST=llvm
. However, I happened upon this solution at random, and it seems to not be an intended way to use Proton.The text was updated successfully, but these errors were encountered: