Windows XP
Published
At first I couldn't get it to work. It kept freezing on startup. I restarted the computer and then used PROTON_USE_WINED3D=1 %command% as a launch parameter. It almost worked after that. It would output to the monitor but not the VR goggles. I then removed that launch parameter and it magically started working after that. It actually even runs better now than on Windows. On Windows, I couldn't get the rotate view controls to work but on here, that actually works.
"Failed to initialize DirectX 12" 1080ti doesn't work with this game until otherwise proven
replaced nvidia DLSS file with the latest one (it didn't make a difference which one I used)
I have a 1080ti. This is the oldest graphics card anyone as of this writing has documented trying to play the game with on here. It doesn't work. All I ever get is an error dialog saying "Failed to initialize DirectX 12. Graphics drivers may require an update, or graphics adapter may not be supported".
I tried Proton Exeperimental, Proton 7.0-6, Glorious Eggroll 7-49, I tried the DLSS trick, I tried every combination of launch parameters anyone has ever reported trying, I tried nvidia driver 515 and nvidia driver 525. I tried running it without waiting for vuklan shaders to finish. I tried running it and waiting for vulkan shaders to finish.
The game is completely unplayable. It crashes far too often. You'd never be able to fly to a different airport and land before a crash.
the map view doesn't show all the terrain. You can fix this by putting it in windowed mode then fidgeting around with the window size until it starts working correctly
lots of stuttering, 10-second long freezes and when starting a new flight, it runs at 0.1fps for a few minutes before starting to deliver a normal framerate. Once it gets going, it runs at a good framerate when it's not stuttering or doing a multi-second freeze.
crashes way too often to be playable. Sometimes it will indefinitely freeze instead of crash. I tried with proton 6.3-8, proton 7.0-3 and proton experimental. %command% -FastLaunch got me the best results.
technically playable, origin is mostly borked right now. Would not recommend
the origin launcher is currently borked. It just shows up as a blank screen. I could only read it by dragging stuff and hoping that what I was dragging was an image, as those are the only ui elements that appear and they only do so when dragging them outside the window.
After about an hour of trial and error, I painstakingly finally managed to log in, submit a verification code and link my steam account to my ea account. I still couldn't get it to launch the game though. It either kept crashing or needed some additional information and there were no images I could use to let me better guess what it wanted.
I almost submitted a borked report but managed to actually launch the game by clicking in random places, judging my cpu usage if where I clicked did something or not. It took a while but I actually got the game to run.
The game runs great but I don't believe I could sucessfully do that again.
sometimes I get popups saying "oh snap, it crashed" when I close or exit it but I haven't ever seen it crash in-game.
the origin issue is a major problem. I doubt you could reasonably play this game unless that ever gets fixed or you have a system configuration that doesn't trigger this bug.
also, it has to process vulkan shaders for 30 minutes every time you start the game. It doesn't matter if you let it complete processing he vulkan shaders or not in previous launches
mods won't work. It doesn't matter which mod you install, installing even 1 mod using the mod manager we are forced to use results in the game getting stuck on the loading screen when trying to start or load a new game. It gets stuck at 14% cpu and 3.4gb of used ram.
Using default steam settings, mods don't work. All the tinkering I tried did not result in finding a way to get mods working.
on both my ubuntu computers, microphone works great out of the box. It must be noted that if gnome crashes, microphone audio will stop working, even if you restart gnome. Once gnome crashes, the only way to restore microphone functionality is to restart the game. I did not test any other desktop environments.
multiplayer works great. Slight stuttering on nvidia 510 drivers, perfectly silky smooth fluid performance on 515.
I used proton 7.0-3. There isn't a box for that on here which is why this is classified as a tinker report.
sometimes the microphone doesn't work. I found that using the pulseaudio gui to click "set as fallback" on the preferred audio input device makes it work but sometimes I can't tell if my teammates can't hear me or if they don't have voicechat. If I had irl friends that play this game, i'd be able to find out for sure but I kind of don't.
sometimes it takes forever to process vulcan shaders but aborting the process doesn't seem to reduce game performance
Microphone doesn't work for me unless I click "set as fallback" for the desired input device in the pulseaudio gui settings. Has to be pulseaudio. Changes made in gnome or cinnamon "sound" settings panel are not respected by steam or SoT, at least for me.
I have been able to play multiplayer as well as accept in-game invites from friends on both steam and xbox live. I don't know how to send invites to friends who are playing on xbox live since you need the xbox live companion app to do so. If you download the xbox live companion app on your phone, you get a "invite to party" button but I haven't tested to see if it actually works.
Sometimes the microphone can be unreliable. Sometimes switching windows to open pulseaudio and click "set as fallback" on the desired input devices fixes microphone problems but there have been times where I had to restart the game for my microphone to start working.
works well for me
In space stations when you get out of your ship and go inside, performance usually tanks until you get away from the docking area and unload all the ships and exterior stuff.
The type of lag when this happens feels exactly like playing Uboat in Linux without using PROTON_NO_ESYNC=1. However disabling esync doesn't fix the lag. This is an Unreal Engine game and Uboat is a Unity game so if the occasional lag is Linux related rather than "big game made by only 1 guy" related, esync isn't the fix.
doesn't work with nvidia drivers. freeze at black screen when starting a new game
VKD3D_SHADER_MODEL=6_6 %command%
The only way to get this game to start on linux with a Nvidia gpu is to use the parameters I provided. See thread here: https://forums.developer.nvidia.com/t/starfield-does-not-launch-on-most-nvidia-gpus-on-linux-and-not-at-all-on-pascal-gpus/265483
Note that I'm using Arch and Nvidia driver 535. People have reported that using Nvidia driver 525 will allow the game to work at the cost of performance and frequent crashes. In Arch, it is very difficult to downgrade nvidia driver versions and probably not possible without doing irreversible damage to your installation (I hate having to reinstall OSes more than I hate not being able to play my game) so I'm not going to try it. I do have a gaming laptop with Ubuntu I will try it on later though.
crashes way too often to be playable. Even removing mods doesn't stop the crash and i'm on latest mesa drivers for my distro.
bash -c 'exec "${@/Starfield.exe/sfse_loader.exe}"' -- %command%
crashes every 30minutes-1hour
6 months ago this never crashed for me. Now it's unplayable. Might be a Fedora issue, last time I had this running without crashes was on a void linux system.
bash -c 'exec "${@/Starfield.exe/sfse_loader.exe}"' -- %command%
I speculate that my crashes are a Fedora/SELinux specific issue because my system hangs for around 2-3 seconds each time the game crashes which is exactly what happens when running buggy g++ programs that only crash on Fedora but not on other systems.
I switched to proton 8 and it crashes a little less often. I also found out through experimentation that most crashes happen right after saving your game and they especially happen more frequently if you save right after loading into a new environment. I'd say my improvements get the crashes down to once every 1-2 hours now which is an improvement. Maybe don't choose a SELinux distro if playing Starfield.
Note that I'm playing the beta update. Performance was terrible on nvidia driver 470. I got 14 fps at the main menu. I updated to 510.54 and now I get 144 fps on the main menu. I changed nothing else. The difference is astounding.
Not working since b127 - performance was unplayable before the update broke proton compatibility anyway
It used to run but it seems to be broken since the last update. It crashes several seconds after trying to start it.
Even when it was working several months ago, the game performance slows down to a crawl once you get into a battle with other ships loaded. Some times you could fix and make it run well for another 5-10 minutes by saving the game and reloading it again but most of the time that doesn't work.
Even before it got broken by the latest update, I would consider this mostly unplayable due to the performance issues. The other people on here acting like the performance issues aren't that bad either didn't play it for more than 10 minutes or found some amazing fix and aren't posting it.
install vcrun2013 and dotnet framework 4.6.2
use protontricks and type "protontricks 494840 --gui". Install vcrun2013 and then dotnet framework 4.6.2. Takes forever. Doing it in non-gui mode fails and will just get stuck in an infinite loop forever (I waited 2 hours and non-gui mode wouldn't do it). You also HAVE to be using proton 5.0-9. 5.13-1 and 4.11-13 does not work regardless of if you install that stuff in protontricks.
sometimes the navigation officer and captain's torso mesh won't load but that's surprisingly all i've found
You need to put "PROTON_NO_ESYNC=1 %command%" in your launch options if you want to get more than 2 fps. Without using that launch parameter, it's blatantly unplayable. After disabling esync, it runs really well and maybe only slightly slower than on windows. I can still run it on max graphics settings this way.
The game doesn't always start. You may have to stop it and start as many as 3 times to get it to start. Once you actually get into the game, it's stable and won't crash.
works great with occasional stuttering. Note that I used proton experimental and not 6.3-6 (there wasn't an option for that on here)
be sure to disabled esync with “PROTON_NO_ESYNC=1 %command%” or the performance will be extremely bad.
it's maybe a little slower than windows but still playable
whatever the devs have done to it in the past year has tanked performance into the ground. Even disabling esync doesnt help anymore.
PROTON_NO_ESYNC=1 %command%
extremely sluggish
crashes once in the ~30 minutes I was testing it
