EDIT: This has been fixed, it all mostly chalked up to possibly a driver / kernel bug. Why things managed to work so well for so long, who can say? Anyway all you need to do is upgrade your Linux kernel to 6.5.x, and your Mesa driver to the latest Mesa git.
Hey all,
I’ve been playing Starfield for the last two weeks, mostly been having a great time with it! I’m using the latest kisak mesa drivers and ProtonGE, and it’s been a smooth and stable experience for the most part.
However…within the last two days, I’ve started having a major issue. Any time I land on a planet and exit my ship, the loading screen hangs, and I get kicked back to my OS’es login screen (Ubuntu Studio 23.04). The audio continues to play, not in a staggered way, but as if the game was still running. And yet, my desktop has no idea about the executable being active.
I dunno if a patch came out within the last day or so that fundamentally changed something, or maybe my hardware’s just finally started melting after weeks of playing. Performance is degraded out of nowhere.
What’s curious is that, every time I reload my save, the game runs fine from within my ship. But, if I try to travel to another planet, or exit out of my landing bay, everything I’ve just described happens all over again. This seems to happen regardless of whether the game is windowed, borderless, medium graphics settings, low graphics settings.
I decided to check whether my hardware was just straight-up melting. It’s not. My other Proton titles that are relatively heavy (Returnal, Resident Evil 4, The Callisto Protocol) all run smoothly at higher graphics settings.
Some specs info:
Also, software:
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
Alright, bit of an update: after investigating my hardware, doing a fresh OS install, and trying just about everything that everybody’s suggested to me so far, I have logs. Definitely amdgpu related, but not 100% sure what is going on yet. This was on Wayland, searches for similar error messages suggest a possible driver bug, maybe issues with particular kernel versions? Still investigating.