spamb07
Published
DLC Initialization Infinite Loop Bug
The game keeps wanting to restart in order to finalize initialization of DLC. It might work without the DLC, but I gave up at this point.
It seems to work out of the box now. I however did not get far in the game.
When quitting, it doesn't close gracefully, but the save seems ok, so no foul.
It works if you are willing to deal with the nonsense to get into gameplay. Once there it seems stable and looks good
Sometimes random artifacts come up during game-play, alt+tab'ing in and out usually fixes it
Once again, once stable, alt-tabing in and out seems to fix the partial screen issue other users have
Enter through the errors and immediately select gameplay in the start menu allows you to back out to the main menu if needed to load the game.
Looking at the main menu for to long without entering gameplay or letting the error's linger on screen crashes the game at the moment.
I don't think it is straight barked, just annoying. It works once in gameplay though. What I need to do to get this working with default proton components:
1.Choose the resolution that is exclusively less than your monitor resolution (this games seems to only support 4:3)
2.Enter through the errors quickly and choose to enter a new game before a crash (which happens in a couple of seconds of first getting to a new screen
3.Once in-game, alt-tab in and out to get true full screen, clean up artifacts, and fix some of the controls.
4.You can now safely (as far as I tested) get back to the main menu to load your save.
It seems to work fine on a keyboard, but controller tests are mixed.
As others have said, it seems that the controller stops working after the tutorial. I do not know if this is also a bug on windows.
Ran primarily with a controller and had appropriate framerate (150-180, Ultra, 1080p) and responsiveness.
It seems to work out of the box. Any oddness seems to be consistent with the windows version.
It seems to work, however It is a multiplayer game and I was unable to find anybody online when testing.
Suggested to use the "vgaversion-vgaversion" under beta's to get a better experience. I did not get far in the game to check everything tho.
It works, as far as I can tell. This multiplayer only game seems dead and I couldn't properly test it.
Crashes randomly with default settings. Use dosbox instead.
Install dosbox natively and run the conf "dosboxPHANT2_single.conf" in the dosbox folder in the local files. It seems to work a lot better this way.
I was able to complete the game with only minor controller issues with Proton 6.3-6 (default at the time). WAY better than native.
In native, there are issues with full screen. Not with proton.
You have to open options -> Controls -> Default bindings for the controller to be seen every time you start the game and when you start a session (continue, start new, etc). This also leaves the "incorrect" keyboard based prompts as the default uses those. I haven't tested if changing the keys to be controller only would correct the prompts.
Play with Proton over native. Native has windowing and other issues. I don't foresee a better native any time soon (without a remake or something).
Also, I found issues with Proton 6.15-GE2, where error text will always show on the screen, so there is a potential for regression in the future. Watch for that.
I was able to run the game an average of ~170 FPS unlocked, however vsync is suggested for reducing stutter (also seen on windows).
Proton 6.14-GE2
Out of the box with GE, over 144 Hz at max settings. I played the entire game with only minor controller disconnect issues. Native soon tho.
6-15-GE-2 GloriousEggroll
Glorious Eggroll : 6.15-GE-2
If controller disconnects, you have to reboot the game in order for it to see the controller again
Decent Framerate when unlocked at 1080p (100-130 fps)
VSYNC has more hitching than I remember on Windows, but overall minor
Like most other NVIDIA users, I am unable to play the game with the newest drivers on any version of proton.
Reverting to older drivers (525) will let you play the game, but with some broken assets and at unexceptable performance (especially as you get to the city). More current drivers (535) are broken.
It seems Starfield works well on enough on the steamdeck. It might not be able to wow you with FSR'd 800p, but it works well enough.
If you walk away from the game for a bit, the right joystick no longer registers, but you get mouse in menus. A smaller bug is that the two start and select buttons seem to be flipped with the default layouyt.
The steamdeck is a great platform to play Starfield, especially if used as an "in between" system to work through the more mundane tasks between major misssions. However, if you are expecting the full visuals that BGS has been able to accomplish, it might not be an ideal platform.
Works after upgrading kernel mainline to 6.5.1, as another user stated
Seems to be borked as of 5.0/GE5.9
I tried all versions of proton up to 5.0 that comes with steam and 5.9GE and none seem to can get beyond a black window popup and crashing
It works as badly as it does on windows once you fix the missing steam_api64.dll error. I only played until the second section tho.
Proton-6.15-GE-2 GloriousEggroll
Had to copy/link "steam_api64.dll" into "common/THE QUIET MAN" dir from "THE QUIET MAN/Engine/Binaries/ThirdParty/Steamworks/.../steam_api64.dll" . This is the same directory as Browsing local files from the game settings menu.
MF-install seemed to stop working with current proton.
Get's stuck on a black screen as opposed to CTD seen without install. Seems to be a regression.
Works with launch options
Needed to set launch option: "taskset -c 0-3 %command%" due to having more than 4 cores like others have said
The game runs as expected, but it will not save and/or load saves in it's current version.
It runs our of the box, no problems that don't seem to be inherent in the game design.
I have note tested on windows. So oddities like frame rate locked at 62 fps, slow initial load, and weird controls could be new to Linux, but I doubt it looking at reviews.
