Starfield (1716740)

[xioren]

Compatibility Report

• Name of the game with compatibility issues: Starfield
• Steam AppID of the game: 1716740

System Information

• GPU: rtx 4090
• Video driver version: 535.98
• Kernel version: 6.4.0-1-amd64
• Link to full system information report as Gist: will have to update later
• Proton version: 8.0-3 and experimental

I confirm:

• [x ] that I haven't found an existing compatibility report for this game.
• [ x] that I have checked whether there are updates for my system available.

todo

Symptoms

The game starts up and seems okay but when starting a new game the game freezes during first load. Experimental freezes and 8.0 crashes.

[xioren]

Also if i add PROTON_USE_WINED3D=1 to launch options the game wont boot and gives an error about video card not meeting minimum spec.

[Katherine1]

I'm having a different problem. When I start the game, it'll reach the building shaders screen and make it partway through. At a decent way in, the game will crash to desktop and refuse to start until I delete the shader cache. Attached is the log.
steam-1716740.log

[benbot]

I'm having a different problem. When I start the game, it'll reach the building shaders screen and make it partway through. At a decent way in, the game will crash to desktop and refuse to start until I delete the shader cache. Attached is the log.

steam-1716740.log

I got past this by removing all my launch options and changing my proton version (which I assume clears the shader cache)

[SammyJames]

I'm also hitting this, logs appear to indicate an issue with a semaphore in vkd3d.

[ExpandingMan]

In particular I see this first

70498.977:0128:01dc:err:vkd3d-proton:vkd3d_view_map_create_view: Intense view map pressure! Got 1024 views in hash map 000000018dcd8dc8.
70498.977:0128:01dc:err:vkd3d-proton:vkd3d_view_map_create_view: Intense view map pressure! Got 1024 views in hash map 000000018dcd9048.

but then, e.g.

70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
70503.294:0128:0224:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.

(RTX 4090)

[benbot]

Replying to #7064 (comment)

Same hardware and same issue for me

[benbot]

I'm also hitting this, logs appear to indicate an issue with a semaphore in vkd3d.

How do you figure?
Just curious. I haven't looked under the vkd3d hood yet.

[baileyallison]

also running into the same issue

manjaro
5.15.128-1
ryzen 9 3900x
3080ti (535.104.05)

[Alpha-Obeisance]

Just adding that I too am facing

4320.209:0124:01e4:warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE.
4324.573:0124:0208:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.

Arch Linux
6.1.50-1-lts
Ryzen 9 5950x 32 @4.1
RTX3080 12GB (535.104.05)
128GB RAM

Only Proton Experimental, Proton 8.0-3, and GE-Proton8-13 launch the game to main menu before crashing upon launching new game.

[descawed]

The vr -4's here appear to mean VK_ERROR_DEVICE_LOST is being returned from calls to vkQueueSubmit2 and vkWaitForFences, among others. I know nothing about Vulkan and D3D, but is the "view map pressure" causing the device to be lost somehow? As ExpandingMan mentioned, that's the last thing in the log before things start failing, although there's a delay of several seconds between the last "view map pressure" message and the first "vr -4".

[benbot]

@descawed https://github.com/HansKristian-Work/vkd3d-proton/blob/master/libs/vkd3d/resource.c#L1211
You're probably not far off, going by this comment

[Alpha-Obeisance]

Someone on steam stated they got it to work with Proton Hotfix. Upon launching under Hotfix it yielded the same result with an error I'd not seen before. Unsure if it's relevant.

5366.455:0128:020c:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to wait for fence, vr -4 5366.455:0128:020c:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4. 5366.455:0128:020c:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.

[Katherine1]

I'm having a different problem. When I start the game, it'll reach the building shaders screen and make it partway through. At a decent way in, the game will crash to desktop and refuse to start until I delete the shader cache. Attached is the log.
steam-1716740.log

I got past this by removing all my launch options and changing my proton version (which I assume clears the shader cache)

Thanks. That worked. Now I just get stuck on a black screen when starting a new game. I can generate and attach logs if someone else hasn't already.

[SammyJames]

I'm also hitting this, logs appear to indicate an issue with a semaphore in vkd3d.

How do you figure? Just curious. I haven't looked under the vkd3d hood yet.

I eventually hit this log line

211167.632:0134:0218:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.

[benbot]

Is anyone on an AMD card and have it not working?

[kimgconnor]

Is anyone on an AMD card and have it not working?

im on a radeon 6600 and game doesnt crash on launch or when starting a new game but at some point before i enter the tunnel. i also have shader pre caching off if that affects it since its related to shaders. am on experiemental

[Raineer]

Is anyone on an AMD card and have it not working?

Yep, 5950X + 6950XT, hanging shortly after E for New Game. Same report as OP, tried on both 8.0.3 and experimental.

[fontivan]

Getting basically the same as everyone else but I also tried loading up a cloud save generated on windows, that also crashes during the load screen. Looks like similar d3d12 errors but possibly some different trace dumps before the crash
proton-experimental-x11-cloud-save.log
proton-experimental-x11-new-game.log

[kimgconnor]

managed to make it a bit farther than was able to before with experimental on the bleeding edge branch. on the loading screen when you first start the game i also saw a progress bar about something to do with shaders that i didnt see before so maybe they changed something to fix it, but am not far enough to say for certain that i just havent gotten lucky to make it this far yet so will continue playing to see

[SammyJames]

Looks like we segfault on the game side:

* thread #45, name = 'CreationRendere', stop reason = signal SIGSEGV: invalid address (fault address: 0x10)
  * frame #0: 0x00000001caf0c506
    frame #1: 0x0000000000090200

[stubkan]

Have Ubuntu 22.04 and RTX 2060. Game freezes after clicking start new game and needs to be killed.

My investigations so far from reading proton logs and trying other DX12 games...

https://pastebin.com/rRJJF4bn - proton log starting the game with no command vars

When it initializes both main and chipset GPUs it finds both but for some reason decides to "DXGI: Hiding actual GPU" and after this it begins to spam dx12 function errors endlessly , ie

warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE

So it seems to me, the nvidia GPU is considered invalid and hidden for some reason. Other DX12 games tested work fine (deep rock galactic) All drivers updated and latest. (proprietry nvidia 535.86) tried proton experimental, proton-ge 8.13

[benbot]

managed to make it a bit farther than was able to before with experimental on the bleeding edge branch. on the loading screen when you first start the game i also saw a progress bar about something to do with shaders that i didnt see before so maybe they changed something to fix it, but am not far enough to say for certain that i just havent gotten lucky to make it this far yet so will continue playing to see

@kimgconnor
This didn't work for me. It still crashed just after starting a new game.

[kimgconnor]

managed to make it a bit farther than was able to before with experimental on the bleeding edge branch. on the loading screen when you first start the game i also saw a progress bar about something to do with shaders that i didnt see before so maybe they changed something to fix it, but am not far enough to say for certain that i just havent gotten lucky to make it this far yet so will continue playing to see

@kimgconnor This didn't work for me. It still crashed just after starting a new game.

@benbot
do you have shader precaching on? and did you see the progress bar related to shaders ingame while it was loading before the main menu?

[Alpha-Obeisance]

@benbot do you have shader precaching on? and did you see the progress bar related to shaders ingame while it was loading before the main menu?

I"ve tried this with both shader pre-caching on and off but result is the same either way. Someone said they got it to work with Proton Hotfix but this has yielded the same results in my case.

[benbot]

@kimgconnor
Yes I do
And yes I saw and completed the shader progress bar.

[kimgconnor]

@benbot do you have shader precaching on? and did you see the progress bar related to shaders ingame while it was loading before the main menu?

I"ve tried this with both shader pre-caching on and off but result is the same either way. Someone said they got it to work with Proton Hotfix but this has yielded the same results in my case.

@Alpha-Obeisance
i unfortunately dont have the knowledge to help much more, but i can still be here incase a working version helps any. also do you have nvidia or amd gpu incase it happens to be seperate issues for them, cause if both me and the guy who had it working with hotfix are amd (which if you know if they are can you lmk) and if you are nvidia since benbot is also on nvidia it could be a sign of seperate issues (or i could just be wrong about all of this due to my lack of knowledge)?

[drlamb]

Game is rock solid stable for me thus far. Fedora 38 + rawhide kernel (6.5) + mesa-git (23.3.0-devel) + Proton Experimental

Max settings at 1440P has yielded 70-130 FPS (no FSR) in my 1.5 hours of playtime.
5800X3D
7900XTX

[LucasiTR]

I didn't say anywhere to install drivers from a browser. Actually it's the first time I hear it's possible. If you are on Arch or a similar distro, just use nvidia-all, it's very simple.

I'm on Linux Mint and I've already tried this. For whatever reason it doesn't work. "makepkg command not found"

[giantplaceholder]

I didn't say anywhere to install drivers from a browser. Actually it's the first time I hear it's possible. If you are on Arch or a similar distro, just use nvidia-all, it's very simple.

I'm on Linux Mint and I've already tried this. For whatever reason it doesn't work. "makepkg command not found"

You shouldn't have used nvidia-all with Debian, Mint or Ubuntu, as it's intended to be used ONLY with Arch or Manjaro.

Please refer to this document -- it's outdated, but it should give you enough pointers, seeing as manual installation procedure hasn't really changed in the past 10 years or so.

Read it thoroughly and don't just jump on the first command you'll see. Disregard any OS versions you see there, and just follow the general flow.

[LucasiTR]

Replying to #7064 (comment)

Use vulkan dev drivers

https://developer.nvidia.com/downloads/vulkan-beta-5354316-linux

This is what happens:

[giantplaceholder]

Replying to #7064 (comment)

Well of course, you're trying to open it in a text editor.

It needs to be launched from the terminal -- it's a self-extracting archive, basically.

[LucasiTR]

Replying to #7064 (comment)

How do I do that? That's what happens when I click to open it from a browser.

[giantplaceholder]

Replying to #7064 (comment)

How do I do that? That's what happens when I click to open it from a browser.

Please refer to the instructions I've posted above, see #7064 (comment). Or better yet, ask any Linux-savvy friend to help you out in person.

I have a feeling that you might not understand the basics of what you are doing. If you're continue to run around doing things blindly, you may end up with a broken system.

[LucasiTR]

Replying to #7064 (comment)

Regardless of how things turn out. Thank you. To everyone who is reading this.

[JCDentonCore]

Replying to #7064 (comment)

sudo sh installername.run

[mozo78]

sudo sh installername.run

But first it has to be made executable - Right click->Properties->Permissions. It's a Linux Mint, and it's PITA for novice to install newer drivers.

[giantplaceholder]

sudo sh installername.run

But first it has to be made executable - Right click->Properties->Permissions. It's a Linux Mint, and it's PITA for novice to install newer drivers.

It's not PITA, but something that requires to actually read documentation.

[mozo78]

It's not PITA, but something that requires to actually read documentation.

It's far easier on Arch with nvidia-all. Arch based distros are more easier and more convenient than .deb-based.

[KickAssDave]

sudo sh installername.run

But first it has to be made executable - Right click->Properties->Permissions. It's a Linux Mint, and it's PITA for novice to install newer drivers.

It's not PITA, but something that requires to actually read documentation.

Please. EVEN now, after many months and months and months of getting to grips with Linux (Arch mostly) and understanding the fundamentals.. I still REGULARLY find it a PITA to do otherwise relatively simple tasks. Unless you work on, grew up on or just use Linux for a hobby, you will be used to Windows where you just download, double click, hit install and wait for drivers/software/games/etc.

Now with that out of the way.

I am running Starfield just fine on latest Nvidia beta driver 545.x.x (Garuda/Arch Linux).

I tested the Vulkan driver and it is indeed faster, however at the cost of stability in some other games I use, so it's not really viable for me.

Performance is definitely noticeably worse with any working driver, however, than when I'm on Windows.

[giantplaceholder]

Unless you work on, grew up on or just use Linux for a hobby, you will be used to Windows where you just download, double click, hit install and wait for drivers/software/games/etc.

Just because things are different doesn't mean that they are easier or more difficult. And please, stop with the off-topic here.

[LucasiTR]

Replying to #7064 (comment)

Well I tried this and for what ever reason, it doesn't work on my system. The "build-essential" is "not found" and I can't unpack the driver download with Archive Manager. Hence I can't get it to open or run in the terminal. That's why I've been silent because I've hit a roadblock and don't know where to go from here. Should I just wipe and install Manjaro or LM again. It's taking all of my strength not to go back to Windows because some people are saying that the game runs twice as fast on Linux then it does on Win 11.

[mozo78]

the game runs twice as fast on Linux then it does on Win 11.

For this game this isn't true at all.

The "build-essential" is "not found"

It's impossible. This package is available for very single .deb distro.

Should I just wipe and install Manjaro

Install something Arch-based or Arch but I can't recommend Manjaro. Anyway, if you're on an Arch-based distro, installing the new driver is a breze in a few steps:
git clone https://github.com/Frogging-Family/nvidia-all.git

cd nvidia-all

makepkg -si

And that's it.

[LucasiTR]

Here's your proof doesn't matter where I am in the process or if its even started. Still says "command not found".

[dsalt]

Here's your proof doesn't matter where I am in the process or if its even started. Still says "command not found".

A package name is not the same thing as a command (or program) name, though in many cases a package will contain a program with the same name.

I could be wrong, but I think that either you're being stupid or you're trolling.

[KickAssDave]

Replying to #7064 (comment)

Cmon, you shouldn't be posting here if you haven't even the foggiest on how apps are installed on Linux. You have to be trolling.

sudo apt install build-essential

Run that. Enter your root/sudo password.

[Blisto91]

Everyone please keep it friendly. No need for these remakes.

@LucasiTR If you are having issues with driver installation I'd recommend seeking out help forums or resources provided by or dedicated to the specific distro you are using. They should hopefully be able to assist you with any such trouble.

[bitcharmer]

I came here to see if there's any relevant updates but all I can see is a flood of posts from a completely clueless user and replies to them.
Can we have those hidden please so the whole thread becomes readable again?

[1basti1]

I'm on steam deck with the newest stable.

Starfield got an update today and now it's crashing my whole steam deck pretty often.
I'm near the end and when I go through an anomaly (in the revelation quest) my deck is always crashing. It restarts with "verifying installation".
Last time I tried I was Infront of this anomaly and wanted to open the menu and it crashed even there.

I played ~20min before and that was fine.

I have 90h on this game and only on deck. The update break something.

Unfortunately now I can't finish this game, because my PC isn't good enough.

[1basti1]

steam-1716740.log

Sorry, never submitted something...

I run it with proton experimental (which is automatically choosen)

This crash always happens, it even crashes when I close the menu (sometimes even when I open it) but I don't know if that's only in the area of the game.

As I said, I played 90h and only on steam deck. And had maybe 3 game crashes, but now the whole deck crashes.

[1basti1]

thats from the journal. Probably no proton issue, but steamos/steam deck issue?

[1basti1]

Ok, sorry. My fault. It seems like a custom ini setting was causing this.

[Blisto91]

@1basti1 Are you able to share it? Might be interesting to take a look closer at anyway. And if you are unsure if it only happens in a specific area then save game too.

[1basti1]

@1basti1 Are you able to share it? Might be interesting to take a look closer at anyway. And if you are unsure if it only happens in a specific area then save game too.

Probably not only that area. I was just confused, because the game worked for 20 mins then I did go into a building and then it all started happening.

I used a custom ini (downloaded it from nexus mods) to get better performance. The line that had to be changed was bGroupRenderAllShadows=1 to 0
It's somewhere in the documents folder. I forgot right now where exactly.

[JCDentonCore]

The game was updated and now I am seeing the image out of sync (tearing) when I move the mouse, it did not happen before, I am using experimental proton bleeding edge with debugging symbols, I attach the proton log.

PC specs: Ryzen 5800x, 32 GB ram, RTX 3070, manjaro linux (KDE) with kernel 6.7rc1, nvidia drivers 535.43.16 vulkan dev, steam beta with runtime beta.
Proton log:
steam-1716740.log

Steam runtime log:

steamruntime.log

Update 12/02/2023

No more tearing but a horrible frame time spikes, using latest proton bleeding edge, beta starfield and vulkan dev 235.43.19, VKD3D_CONFIG=skip_driver_workarounds, MANGOHUD=1 PROTON_ENABLE_NVAPI=1 variables

Graphical issues

steam-1716740.log

[NoXPhasma]

With the latest update of Starfield, it now crashes on launch on the first screen for me. It then shows me this error message:

Sysinfo: https://gist.github.com/NoXPhasma/ba738fff6ec203778f7856299fcf3a94
Logfile: steam-1716740.log

UPDATE
Apparently, Starfield now loads amdvlkpro so on my system, which is didn't before, and that makes the game crash. When I use VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command% as launch parameter, the games starts.

I wonder why this suddenly happens?

[mattpotma]

Probably the FSR 3 update they released yesterday

[strohmy]

Same issue with RTX 4060 driver version 535 on experimental and 8.0-8.5.

Kernel 6.5.0-25-generic

Hardware gist here:
https://gist.github.com/strohmy/26978cb22e9ae78aedda718ce064d54c