HGL
optimistic-gold
Bug in the new update
After the new update, I could not play any games. Every game I have is not working and gives me this error. Here is a log from one of the games. Please help me—I couldn't play anything yesterday.
Using the new Proton like
9.25 only gives me a black screen without this error.
This is driving me crazy.
13 Replies
optimistic-goldOP•4mo ago
foreign-sapphire•4mo ago
I have the same problem. I tried everything, but nothing works.
xenial-black•4mo ago
IMPORTANT: Logs are disabled. Enable verbose logs before reporting an issue.
You can do so from the game's settings.optimistic-goldOP•4mo ago
Is this it ?
extended-salmon•4mo ago
you said you are using proton 9.25 but the logs show you are using 9.4
secure-lavender•4mo ago
umu is not enabled. Your prefix is nested the game folder itself. Fix that
"winePrefix": "/mnt/SSDTwo/Gaming/Bloons TD 6",
Installed in: /mnt/SSDTwo/Gaming/Bloons TD 6/BloonsTD6
also, what file system is /mnt/SSDTwo?wise-white•4mo ago
I thought umu was automatically enabled when you chose proton now, or was I misunderstanding what the release notes were telling me?
secure-lavender•4mo ago
it should be enabled, but it isn't here
extended-salmon•4mo ago
it's not enabled for games that were not using umu before to not change how working games were running, it's enabled for new games
optimistic-goldOP•4mo ago
9.4 give that error when I change to 9.25 it only give me black screen
I solved the problem by deleting the heroic folder in the .config folder
I dont know why it worked but it worked
what is "umu"?
Deleting the Heroic folder from the config folder is not a great solution. If you know a better way, please share it here.
this is my second ssd I mounted in the /mnt
secure-lavender•4mo ago
yes, I get that. what file system is the drive?
Steam Runtime for outside of Steam. there's a disable button in the game settings now, toggle that on and off again so that umu is enabled.
optimistic-goldOP•4mo ago
the file system is
btrfsforeign-sapphire•4mo ago
LOL, you took the 'Damn, I Messed Up, We Gotta Go Bald' approach. I had the same problem and fixed it by downloading the old version 2.15.2 from GitHub.