Starfield (1716740)

[vercingetorx]

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.

[vercingetorx]

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 https://github.com/ValveSoftware/Proton/issues/7064#issuecomment-1701988449

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)

[ghost]

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

[ghost]

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?

[ghost]

@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

[polluxau]

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

So it seems it's something to do with nvidia and vkd3d?

Edit: guess not? Guess you have to be running the latest of everything to get it running properly

[kimgconnor]

So it seems it's something to do with nvidia and vkd3d?

Edit: guess not? Guess you have to be running the latest of everything to get it running properly

that meaning you got it to work on nvidia? if so what things did you have to update?

[benbot]

@pollux56 ☝️

[ghost]

Edit: guess not? Guess you have to be running the latest of everything to get it running properly

My system is completely updated and it's still not launching. Switched from mesa to mesa-git but no such luck at resolution. Still crashing shortly after launching new game.

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

I've used multiple Proton versions, and GE and still haven't had any luck.

[benbot]

@drlamb did you run the game with any launch options?

And are you on any betas of proton experimental?

[kimgconnor]

Edit: guess not? Guess you have to be running the latest of everything to get it running properly

My system is completely updated and it's still not launching. Switched from mesa to mesa-git but no such luck at resolution. Still crashing shortly after launching new game.

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

@Alpha-Obeisance did you try with experimental bleeding edge or proton next?

Edit: nvm thought the message was from the other guy

[drlamb]

@drlamb did you run the game with any launch options?

And are you on any betas of proton experimental?

No launch options + bleeding edge of proton experimental

[kimgconnor]

@drlamb did you run the game with any launch options? And are you on any betas of proton experimental?

No launch options + bleeding edge of proton experimental

thats the same as me (except i do have mangohud enabled by default for all game but that prob isnt affecting anything)

[polluxau]

Edit: guess not? Guess you have to be running the latest of everything to get it running properly

My system is completely updated and it's still not launching. Switched from mesa to mesa-git but no such luck at resolution. Still crashing shortly after launching new game.

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

I've used multiple Proton versions, and GE and still haven't had any luck.

I meant in terms of amd hardware, on nvidia it's a different story because of its driver

[stubkan]

NVIDIA 2060 with Ubuntu GOT IT WORKING!!!

Downgrade driver from proprietry 535 to 525, purge all nvidia, install 525, restart. Use proton experimental.

Downside is - It runs slow. Significantly.

Attached Logs for people. Not working - Using 535 - https://pastebin.com/rRJJF4bn Working - Using 525 - https://pastebin.com/qssKgzKR

I assumed it was broken because it was reporting the main GPU was hidden and spamming dx12 not implemented, returning E_NOINTERFACE , but these errors are present in the working 525 log, so idk.

[r4m0n]

At least on the nvidia side, looks like the driver is crashing (on dmesg): NVRM: Xid (PCI:0000:41:00): 109, pid=2645789, name=Starfield.exe, Ch 0000004e, errorString CTX SWITCH TIMEOUT, Info 0x2c03f

I'm on Arch with the latest driver (535.104.05), anyone who got it running with an nvidia card can post their driver version?

[kimgconnor]

someone on protondb apparently got it working on 535.104.05 using a GeForce GTX 1650 and they are using the flatpak version of steam

[143mailliw]

Nobara 38, Proton Experimental (bleeding-edge AFAIK), 7900XT, game runs fine, no problems.

[SammyJames]

seems mostly an nvidia problem.

[stubkan]

The latest nvidia driver off their site is 535.104, and someone has reported that working. Mine was Ubuntu 22.04's latest supported and was 535.86 which does not work. I've switched to 525.125 which works. Comes with significant performance issues though.

I will attempt to install 535 again but force it to 535.104 instead of 535.86 and report back if that works.

[ghost]

I've switched to 525.125 which works. Comes with significant performance issues though.

I've had no luck on 535.104.05

[stubkan]

Anyone tried nvidia 530 drivers? It is apparently the cutting edge new feature branch

EDIT. installed nvidia-drivers-530 which installed 535.104 instead of 535.86, so guess thats what that version does.

Can confirm it doesn't work. Only 525 works then, and its real laggy, so I'm holding off on playing that.

[kimgconnor]

have any of you tried on the flatpak as there was that one report where someone was using 535.104.05 which some of you were on and didnt work for you, but it was working for them so if its flatpak that works, that could be a solution until drivers get updated on all distros

[r4m0n]

someone on protondb apparently got it working on 535.104.05 using a GeForce GTX 1650 and they are using the flatpak version of steam

I see 0 entries listing 535.104.05 marked as working, did you see that somewhere else or misread it?

[benbot]

Confirmed working on 4090 with the 525 drivers.

It is slow as hell tho. 11fps on medium.

[kimgconnor]

someone on protondb apparently got it working on 535.104.05 using a GeForce GTX 1650 and they are using the flatpak version of steam

I see 0 entries listing 535.104.05 marked as working, did you see that somewhere else or misread it?

hmm when i went to find it to link to it i cant find it anymore, might have looked at the specs of one that had flatpak and for whatever reason thought that it was next to one that did work or something like that, my bad

[r4m0n]

someone on protondb apparently got it working on 535.104.05 using a GeForce GTX 1650 and they are using the flatpak version of steam

I see 0 entries listing 535.104.05 marked as working, did you see that somewhere else or misread it?

hmm when i went to find it to link to it i cant find it anymore, might have looked at the specs of one that had flatpak and for whatever reason thought that it was next to one that did work or something like that, my bad

Ok, then 535.* is bad, unless someone manages to bisect a working version. I'm back on 525, which works and is terrible. Unless we figure out which trick Valve pulled on the Steam Deck to get it working, we'll probably depend on nvidia releasing a less-broken 535.

[benbot]

Anyone tried nvidia 530 drivers? It is apparently the cutting edge new feature branch

@stubkan trying with the 530 drivers now. Still seems really really slow though