I have been able to run games whether it was Steam, GOG, or itch and now I can't get shit to run. I don't have the worst rig. I was playing Fo4, and now suddenly I can't. I switched from a shitty Windows to Garuda. That was working wonderful, until I suddenly couldn't get it to work no matter what Proton version. Then I switched to Ubuntu, same issue. Then Cachy, then back to Ubuntu, and now back at it again with Garuda. Still. The. Same. Fucking. Problem. I have scoured the net for answers and fixes to no avail and I feel like driving into traffic. I cannot get any Proton version to run ANY GAME at this point, not just the more intensive ones. What the fuck do I do? Here are some specs:
- Processor: 8 x Intel Core i7-2600 CPU @ 3.40Ghz
- Mem: 32 GiB RAM
- Graphics Processor: Quadro K620
- Dell Optiplex 990 (7010 housing)
- 245GB SSD, with additional 500GB HDD and 4TB external drive
I have been able to seamlessly play all kinds of games for months, and then it just up and doesn't let me anymore. I haven't done anything to tweak shit out of whack. No matter how many clean installs and following instructions otherwise, this shit feels BROKEN and I'm LOSING IT. Someone help me please.
-Little extra info, I always skip the Vulkan shaders bullshit and it was fine before. Sometimes it'd load with the "Downloading Windows (somethingsomething), but I don't get that anymore, and as soon as I skip the thing crashes before any launchers of sorts can load so I can mess with configuration with the little GUI bullshit before total launch.
- UPDATE:
I have switched to Bazzite and have set my external drive to ext4. Shit seems to work seamlessly now. Thank you all very much.
Okay. Probably easier to focus on one, get that working, and see if the problem is common to the others.
I see Fallout 4 and Steam on there. What specifically happens when you try to launch Fallout 4 out of Steam?
EDIT: At least it looks like that's an older Sandy Bridge CPU. I had a 13th gen and 14th gen Intel CPU do the "destroy themselves internally" thing, which manifested itself as an increasing rate of crashes everywhere until finally it couldn't even boot without all cores but one disabled. Was hoping that this wasn't gonna be someone else getting hit with that.
EDIT2: And I'm assuming that, at least for troubleshooting purposes, this is a clean, unmodded Fallout 4 install, right?
Just for now I am having the issue of not veing able to run Fo4 on Steam anymore when I have otherwise been able to run it with no issue. It just up and wouldn't let me boot it up one day. No matter what I tried. All that happens is that I will pick a Proton version I know it worked with, click Play and then it does the stupid Vulkan shaders bit. I click Skip which would normally be fine, and then it just crashes and says Play again in green. Haven't been able to get it to work.
Totally unmodded, I couldn't get that shit figured out anyway and lost interest. Just wanted to play what I had, which is what I was doing before it decided to torment me.
Just disable this, it's annoying and basically doesn't do much.
Steam Settings -> Downloads -> (at bottom) Enable Shaderpre-caching, turn off.
Okay, so then what you're seeing is no dialog or anything coming up, just the "Play" button going green again after a while?
And you already mentioned setting a Proton version, which was going to be about the next thing I was wondering about
which version is it that you're using?
EDIT: Also, I believe that if you let it complete the Vulkan shader processing, it won't need to do so again until the next time a game updates, so if you're going to be launching a game multiple times in a short period of time for troubleshooting or something, you might want to let it complete the pass once.
EDIT2: If you have the hard drive space and a reasonably fast connection and want to try this, one thing you might try, though it's a bit of a brute force method, is quitting Steam, renaming the
.steamdirectory in your home directory to something likeoldsteam, and then relaunching Steam and reinstalling Fallout 4. I have seen Steam get into a broken state before on at least three occasions over the years that it could not recover from on its own after I had my machine lose power while Steam was updating itself. That may not be necessary, but it'd rule out a number of potential issues.8.0-5
Okay, yeah, that should work with it. I'm pretty sure that I run it with a newer version, but I see people running 8.0 without issue.
Next thing to try, I agree with the folks above, is probably to hit the Steam logs, unless you want to jump all the way to taking the extreme route I mentioned above of moving the Steam directory, starting up Steam, reinstalling the game, and seeing if that does it. If it does, that'd probably narrow it down to issues with Steam settings, the Steam installation, the game installation, and the Proton installation.
I understand that skipping the Vulkan shaders has been ok in the past, but as something has gone wrong/ changed since then, have you tried waiting for the shaders to load at all?
I have waited before and either it ran or it didn't depending on the machine I was using at any given time. Inconsequential generally. But as far as today, no I have not. It seems to take hours when I have let it previously.