Proton
Proton copied to clipboard
ValveSoftware
Long pause between clicking "PLAY" and proton log file
Your system information
- Steam client version (build number or date): 1709168962
- Distribution (e.g. Ubuntu): Ubuntu 23.10 (64 bit)
- Opted into Steam client beta?: No
- Have you checked for system updates?: Yes
- Steam Logs: steam-logs.tar.gz
- GPU: Nvidia
Please describe your issue in as much detail as possible:
When I start a proton game, it takes about two minutes to reach a point where I see the game's ui. It even takes a long time for the proton log to appear.
When i start steam from the console and launch a game i see
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
In the logs. When using PROTON_LOG=1 the stream-{{ID}}.log file first appears forty seconds after that.
The "cloud status" display changes quickly, and then it's again about fourty seconds until i see some UI element of the game (anticheat/loading screen, etc). Sometimes a "Processing Vulkan Shaders" window appears but that's not the issue.
This is not specific to one game, some affected ones are: 603960, 553850, 1817190, 244160.
Changing the proton version has no effect on the startup time. Tried changing between experimental and the current 8.x version.
Checked the partition for possible errors in the SSD. Nothing was reported.
Steps for reproducing this issue:
- Open Steam
- Click "PLAY" on any of those games
@plafue could you try proton 7 and see if it has the same delay? First launch is going to be a bit slower due to having to rebuild the prefix.
This happens every time I start a game, not when a new version of proton is released and I start a game with that version for the first same time.
Switched one of the games to 7.0.6 to the same effect.
Taking a look at the processes running after I hit play, it seems like a lot of time is spent on iscriptevaluator.exe evaluatorscript_XXXXXX.vdf. I can't see it launching any other set up / installation processes
Not quite.
I continued my research and found this thread. I then found out that some package installed the noto fonts in my system, which added a very (very!) large number of fonts. By removing them startup time improved by a lot (I don't have specific numbers right now).
It is still very noticeable but not as bad as before.