Also see here: https://github.com/ValveSoftware/Proton/issues/7064

It is happening on AMD cards too

if you are crashing after selecting new or continue at main menu try this command

Steam
Launch options:
VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command%

Lutris
Configure -> System Options -> Command Prefix
VKD3D_CONFIG=force_compute_root_parameters_push_ubo

VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command%

This did not fix things for me on steam flatpak with nvidia-open drivers.

@HansKristian-Work I had this issue with Diablo 4. 535 was buggy, crashed and all around slow when it worked, 525 was running great. I didn't manage to find a similar issue, so I thought It's my system to blame. Clearly there is something.

On another note, VKD3D_CONFIG=force_compute_root_parameters_push_ubo doesn't work for me. Nvidia closed 535. I'll check 525.

NV 535 stable is clearly bugged here. 525.47.35 at least seems to work though ...

Performance on NV currently is known to be extremely poor due to being completely CPU bound. This is caused by lack of us enabling NV_device_generated_compute on NV due to a driver bug. #1639 for details. When the beta driver updates, it should start running much better.

On Mesa desktop, please ensure that:

* You're running kernels 5.15.121+, 6.1.40+ or 6.4.5+ to fix a kernel regression that affected Starfield. Without it, GPU will hang randomly.

* You're running mesa from git to get VK_NV_device_generated_commands_compute for optimal performance.

* Proton Experimental

Hello, thank you for your work, I hope you're well.

How is 6.3.9 regarding this? As you may know, we have big issue on AMD with MEMCLOCK being locked to minimum and it appears it's still not fixed by 6.5.x.

How is 6.3.9 regarding this?

afaik, 6.3 kernels don't have a backported fix.

Unfortunate but thanks.

No issues running on nvidia 525, albeit terrible performance, same setup. I guess it really is 535.

I have an RTX 3070 MaxQ. With 535 drivers, the game doesn't launch. With 530 or 525, the game launches, and I can start a new game, but it has atrocious performance and half the assets don't load - humans are missing limbs, walls are missing, etc.

Performance on NV currently is known to be extremely poor due to being completely CPU bound. This is caused by lack of us enabling NV_device_generated_compute on NV due to a driver bug. https://github.com/HansKristian-Work/vkd3d-proton/pull/1639 for details. When the beta driver updates, it should start running much better.

FWIW when I use an older driver version (seems like 535.98 or earlier) the game runs at about 11 fps on my 4090 with 99% gpu load and only 4% cpu load.

On a side note, 535 also broke Horizon Zero Dawn for me.

On a side note, 535 also broke Horizon Zero Dawn for me.

Have also seen reports of it breaking Cyberpunk 2077. 535 seems to have not gone totally to plan.

Have also seen reports of it breaking Cyberpunk 2077. 535 seems to have not gone totally to plan.

Can't speak to HZD, but on 535 Elden Ring stopped working for me, Cyberpunk seems to play nice though.

Have also seen reports of it breaking Cyberpunk 2077. 535 seems to have not gone totally to plan.

Can't speak to HZD, but on 535 Elden Ring stopped working for me, Cyberpunk seems to play nice though.

Elden Ring runs fine on 535-104-5 w/ GE-Proton8-13 for me on 6.5 kernel.

Elden Ring runs fine on 535-104-5 w/ GE-Proton8-13 for me on 6.5 kernel.

Well that's hopeful, I'm running 6.4.12 but was wanting to try grabbing mainline kernel and testing after this comment here. Might be a bit before I get a chance to check it out but maybe others can confirm/deny?

NV 535 stable is clearly bugged here. 525.47.35 at least seems to work though ...

Performance on NV currently is known to be extremely poor due to being completely CPU bound. This is caused by lack of us enabling NV_device_generated_compute on NV due to a driver bug. #1639 for details. When the beta driver updates, it should start running much better.

• Using new Nvidia beta driver 535.43.09 released today
• Proton Experimental
• VKD3D_CONFIG=skip_driver_workarounds PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 %command%

I'm able to get in the game without crashing, but everything is blurry and performance is at 18fps (4090).

Proton log has this:

vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Cannot load existing on-disk cache due to driver version mismatch.
fixme:vkd3d-proton:d3d12_device_caps_init_feature_options1: TotalLaneCount = 12288, may be inaccurate.
warn:vkd3d-proton:d3d12_device_create: Feature level 0xc200 is not supported.

And then it spams thousands of lines with:

warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Ignoring stencilTestEnable due to lack of stencil aspect.
warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE.

It's better if you post a full Proton log.

It's better if you post a full Proton log.

steam-1716740.log

Just to report that using:

• current Proton Experimental on
• Mesa 23.1.5,
• Arch Linux 6.3.9,
• Starfield 1.7.23
• AMD 7900 XTX

The game loaded and I could play the intro without any trouble.

EDIT: I'm seeing those

{}CRASH (ACCESS VIOLATION (inaccessible read at 0x000000000000002C):)
Now that I'm progressing more. Guess I'm going to have to wait and see how 6.5.x is going to come up.

The game still hangs on my system even with Nvidia dev 535.43.09. :(

vc++2022 is tough one, and starfield is not only game from same linage code , Microsoft is making you difficult , i know in a fact since they owned beths studio and entire activision publisher its gonna be more complicated to get vc++2023 code on any dxvk linage code with broken wine libraries that now windows kernel now made changes since beginning 2023 with latest update to get dx12 code into system layer vs user layer that been unsecured for years since vc++2021 the last final version for dx12 library to be in user layer is now into system layer where driver layer share with now

i don't know what linus planning or how get this around it in his kernels , but to me, its not looking good for valve and dxvk creators ...this might be end of proton completely , i afraid to say this but it lasted when it started since he created dx9k,dxvk, vkd3d...not sure amd have something to do with it, it really hurt intel now with this game and entire linux user space that uses vulkan to run native windows games ...we need to put more pressure to get devs to make linux native ports now cause your idea is not gonna work anymore with microsoft latest OS kernels...it just change , oh well, i still have windows 11 on other drive and don't see point using linux right now, it feels tedious for me now, i just getting old and tired to use linux..i just don't want anyone tried break their heads for this , i just give up

i don't know what linus planning or how get this around it in his kernels , but to me, its not looking good for valve and dxvk creators ...this might be end of proton completely , i afraid to say this but it lasted when it started since he created dx9k,dxvk, vkd3d...not sure amd have something to do with it, it really hurt intel now with this game and entire linux user space that uses vulkan to run native windows games ...we need to put more pressure to get devs to make linux native ports now cause your idea is not gonna work anymore with microsoft latest OS kernels...it just change , oh well, i still have windows 11 on other drive and don't see point using linux right now, it feels tedious for me now, i just getting old and tired to use linux..i just don't want anyone tried break their heads for this , i just give up

IMO this place is not a place for a rant like this, take it up to reddit please

Back to topic at hand...

Just tried nvidia vulkan dev 535.43.09 today, seems like the game can pass shader compilation but still hard locks when loading new save or starting new game. I think nvidia 535 is indeed still buggy and for those on nvidia GPUs right now the only way to play on linux is to use 525 series driver (but with performance issue).

Some logs:

531.970:012c:01c0:warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE.
532.518:012c:01c0:warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01f8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to wait for fence, vr -4
536.753:012c:01e8:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
536.753:012c:01e8:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to wait for fence, vr -4
536.753:012c:01e8:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.
536.753:012c:01e8:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.

@delfianto Same issue where it hangs when trying to begin a new save. Can someone that's gotten it to work post an already-created save? Maybe we can get it to load.

@delfianto Same issue where it hangs when trying to begin a new save. Can someone that's gotten it to work post an already-created save? Maybe we can get it to load.

Btw same issue when loading pre-existing save. I played few hours using nvidia 525 driver, tried upgrading to latest vulkan dev and game hard lock when loading my last save.

@delfianto Unfortunate, thanks for trying, answers that question!

NV 535 stable is clearly bugged here. 525.47.35 at least seems to work though ...

Performance on NV currently is known to be extremely poor due to being completely CPU bound. This is caused by lack of us enabling NV_device_generated_compute on NV due to a driver bug. #1639 for details. When the beta driver updates, it should start running much better.

On Mesa desktop, please ensure that:

• You're running kernels 5.15.121+, 6.1.40+ or 6.4.5+ to fix a kernel regression that affected Starfield. Without it, GPU will hang randomly.

fwiw I'm running amd rx5700 and I'm still getting random hangs on 6.4.12, so it looks like there's an amdgpu bug on 6.4.12?

I eventually hit

err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.

and I see this in my dmesg logs at the same time which I'm guessing is causing this vkd3d log:

[ 4674.927560] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2095545, emitted seq=2095547
[ 4674.927853] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Starfield.exe pid 216576 thread vkd3d_queue pid 216817
[ 4674.928126] amdgpu 0000:26:00.0: amdgpu: GPU reset begin!
[ 4675.122942] amdgpu 0000:26:00.0: amdgpu: BACO reset
[ 4678.266664] amdgpu 0000:26:00.0: amdgpu: GPU reset succeeded, trying to resume

For whatever reason VKD3D_SHADER_MODEL=6_6 gets me past the new game crash on load using 535 with a 4090 but it doesn't get me far because it crashes during the next few seconds of the intro playing.

That should be a coincidence as 6_6 will already be advertised if the game doesn't complain about requirements

6900 xt, Nobara 38, Mesa git 23.3, kernel 6.4.10, GE Proton 8-13 here.
Game would crash each time New Game is clicked unless as @mc711 mentioned VKD3D_CONFIG=force_compute_root_parameters_push_ubo is set. Then game would run but still it would randomly crash a lot with intense view map pressure error. Using latest vkd3d with "View pressure message fix" fixed these crashes as well (3~4 hours of play without any crashes so far)..
Thank you!

Using latest vkd3d with "View pressure message fix" fixed these crashes as well (3~4 hours of play without any crashes so far)..

So that's the fix for this issue?

No. The Nvidia crashes are a driver issue.

It's not a "fix". It just removes log spam.

VKD3D_CONFIG=force_compute_root_parameters_push_ubo is also completely irrelevant, and does not even exist anymore. It's been supersedes after NV_dgcc was merged. It would be a fix if using a pretty old vkd3d-proton build though.

I see. I guess we need to wait and pray for it to be fixed in the next NVIDIA driver? Or is it something that can be fixed on the proton's side?

It seems this game is harder to run on Lutris than Steam. Many steam (AMD GPU) users didn't need to do anything and had no crashes either according to ProtonDB reports. Maybe Lutris is buggy here. Nevertheless "View pressure message fix" indeed fixed my crashes!! (or maybe a random graphics settings was the culprit that somehow I have missed!)
also my vkd3d version is 2.10 according to logs...

EDIT: I found a AMD GE Proton 8-13 ProtonDB report with similar experience as me (new game crash + random crashes that solved themselves somehow). Most likely my crashes fixing when using "View pressure message fix" could be a coincidence and under "somehow fixed itself" category too and unrelated to the vkd3d changes... I'm sorry for making a confusion!

I had to restart the game 2 times because it crashed while loading the main menu and when I wanted to start a new game. I don't know why tho but after that I was able to play. I experienced one game crash in the character creation menu. I restarted the game, loaded the save and everything went fine from there. After playing for 2.5 hours from there I experienced no further crashes so far.
Besides the initial crashes (which I couldn't reproduce as I played further) everything else seems to be running fine and out of the box.

Using latest vkd3d with "View pressure message fix" fixed these crashes as well (3~4 hours of play without any crashes so far)..

So that's the fix for this issue?

It's not a "fix". It just removes log spam.

VKD3D_CONFIG=force_compute_root_parameters_push_ubo is also completely irrelevant, and does not even exist anymore. It's been supersedes after NV_dgcc was merged. It would be a fix if using a pretty old vkd3d-proton build though.

where did you update this setting ?
i added the key value in lutris / dll but the game is still crashing

VKD3D_CONFIG=force_compute_root_parameters_push_ubo is also completely irrelevant, and does not even exist anymore. It's been supersedes after NV_dgcc was merged. It would be a fix if using a pretty old vkd3d-proton build though.

Doesn't seem irrelevant at all to me. On vkd3d 2.9 if i omit this option i get the following error when starting a game (new or existing) :

State template is required for compute, but VKD3D_CONFIG_FLAG_FORCE_COMPUTE_ROOT_PARAMETERS_PUSH_UBO is not enabled.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

It is the latest listed on the Releases page, though. How would one go about installing a more recent version ?

I fix my issue (crash after starting a new game) by updating the vkd3d version on lutris here :

this fix is working, i can start a new game on lutris :
https://www.reddit.com/r/Starfield/comments/169pg6t/fix_continued_how_to_fix_crash_after_selecting/

vkd3d 2.9 have a problem. you can update it manually here :
https://github.com/HansKristian-Work/vkd3d-proton/actions/workflows/artifacts.yml

click on the last workflow and update your vkd3d manually. To download it, you need to connect to your github account

Confirmed working with @nbdy-coder 's solution. I used latest master instead of the specific artefact in the reddit post but it's worked so far for me, no crashes or anything.

thx @HansKristian-Work you are a Legend

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

It is the latest listed on the Releases page, though. How would one go about installing a more recent version ?

click on "Actions" tab, click on latest workflow runs and find one that has "build-artifact" in it and download and install it.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

So this is why Lutris users have so many problems as opposed to Steam.. Steam experimental automatically upgrades vkd3d to latest git version yet Lutris users have to do this manually... their "ancient" 2.9 was leading to crashes.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

It is the latest listed on the Releases page, though. How would one go about installing a more recent version ?

click on "Actions" tab, click on latest workflow runs and find one that has "build-artifact" in it and download and install it.

Yes ! Turns out i had botched that step so i thought 2.9 was the new version.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

So this is why Lutris users have so many problems as opposed to Steam.. Steam experimental automatically upgrades vkd3d to latest git version yet Lutris users have to do this manually... their "ancient" 2.9 was leading to crashes.

That is correct. It's a bit unintuitive to upgrade vkd3d on lutris (first select manual in the select, then replace manual with the path to the artefact) but it seems to solve the issue durably. I only had a few missing textures since i did that.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

It is the latest listed on the Releases page, though. How would one go about installing a more recent version ?

click on "Actions" tab, click on latest workflow runs and find one that has "build-artifact" in it and download and install it.

Yes ! Turns out i had botched that step so i thought 2.9 was the new version.

t would be a fix if using a pretty old vkd3d-proton build though.

You missed this part, 2.9 is ancient by now.

So this is why Lutris users have so many problems as opposed to Steam.. Steam experimental automatically upgrades vkd3d to latest git version yet Lutris users have to do this manually... their "ancient" 2.9 was leading to crashes.

That is correct. It's a bit unintuitive to upgrade vkd3d on lutris (first select manual in the select, then replace manual with the path to the artefact) but it seems to solve the issue durably. I only had a few missing textures since i did that.

Is there a solution for Lutris to automatically update its artifacts?

Or do we have to manually update them every time?

That's the price to pay for playing for free lmao.

A bit off topic, but I'm having a seemingly impossible time of getting anything at all to run on lutris, as had often been the case in the past. I thought I'd try bottles but that still doesn't make it quite as easy to update vkd3d version... perhaps it's just better to wait for a GE patch...

@nbdy-coder i'm not sure if vkd3d versions are distributed with Proton versions (which can be downloaded & installed from the Runners settings), or directly shipped with Lutris itself (which means we'd have to wait for a full new release of Lutris to potentially get a more recent vkd3d)

I am able to run new game with Nvidia dev 535.43.09 and https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/6076519760 but screen is blurry and game is unplayable.

From the above comments from @Dam-Buty and @pppbb , I gather that perhaps one (more minor) issue is with vkd3d, but that a full fix requires drivers other than 535 for the game to be playable, is that a fair assessment?

I fix my issue (crash after starting a new game) by updating the vkd3d version on lutris here :

this fix is working, i can start a new game on lutris : https://www.reddit.com/r/Starfield/comments/169pg6t/fix_continued_how_to_fix_crash_after_selecting/

vkd3d 2.9 have a problem. you can update it manually here : https://github.com/HansKristian-Work/vkd3d-proton/actions/workflows/artifacts.yml

click on the last workflow and update your vkd3d manually. To download it, you need to connect to your github account

how did you update you vkd3d manually, in lutris when oi select "manual" it doesnt show anything for me to paste the path to the downloaded artifact in, using the steam deck, lutris is from the flathub

If you are using lutris - https://github.com/lutris/docs/blob/master/HowToDXVK.md

If you are using proton the vkd3d fixes are already in it, since it comes with its own vkd3d packages.

You should also make sure your kernel was updated in the last 2 weeks so the hooks the vkd3d use are in it. Check this list https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

If you are using lutris - https://github.com/lutris/docs/blob/master/HowToDXVK.md

If you are using proton the vkd3d fixes are already in it, since it comes with its own vkd3d packages.

You should also make sure your kernel was updated in the last 2 weeks so the hooks the vkd3d use are in it. Check this list https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

i literally went to /home/deck/.var/app/net.lutris.Lutris/data/lutris/runtime/vkd3d/
found the v2.9 folder, made a folder named it v2.10 and pasted the downloaded artifact, went back to lutris and in vkd3d i just wrote v2.10, seems to be working with how janky i did it

and pasted the downloaded artifact....

I am thoroughly lost on this. I added the filed to the same folder as you, but it still wont load. Im running with Lutris on Pop!_OS so that may be the issue.

@danktankk @fqmes

Yes it's pretty unintuitive and it took me a while but in fact you are supposed to replace "Manual" with the path to the unzipped artefact. Once you start the game, Lutris will do the work of symlinking the DLLs in the correct places. See screenie :

@fqmes i didn't know this technique was a thing, nice find ! the only risk is that it may break in some way once 2.10 is added proper into next Lutris update.

@ExpandingMan This fix is confirmed to work for AMD users, and is wholly unrelated to the Nvidia driver shenanigans. Wish there was a way to split a Github issue cause it's a bit unwieldy to follow the 2 conversations up front.

@ExpandingMan This fix is confirmed to work for AMD users, and is wholly unrelated to the Nvidia driver shenanigans. Wish there was a way to split a Github issue cause it's a bit unwieldy to follow the 2 conversations up front.

ah, makes sense that this didnt work for me then. guess ill have to hurry up and wait for a new driver :(. Doubtful it will be any time soon.

Anyone seeing weird artifacts with FSR2 on Proton Experimental + Mesa Git?

Yes rdna3 GPU's suffer from it. Very likely a mesa problem which i will try to make an issue about tomorrow

I'm able to play on a 4090 using nvidia driver 530.41.03(built with nvidia-all), kernel 6.4.12, & lutris GE-Proton8-14. Needed to set the VKD3D_CONFIG=force_compute_root_parameters_push_ubo env var in lutris system options.

Started with ultra settings but dropped some to medium/high & get ~45-60fps at 1440p.

Can confirm it works with nvidia driver 530.41.03(built with nvidia-all), kernel 6.5.0-1, GE-Proton8-14 Steam and startup option VKD3D_CONFIG=force_compute_root_parameters_push_ubo.

No crashes so far, new game and character creation work.

The downside is the abysmal performance with 20-30 FPS on medium settings at 1440p with RTX 2070S.

I have pushed an updated version of VKD3D to Lutris, based on the latest code. I haven't experienced any crashes since then on a 5700XT.

I haven't managed to get the game running on Nvidia since Nobara ships with the 535 driver and there is no simple way to downgrade.

Any advice for when I get the crazy flickering indoors?

kernel: 6.4.6-3
mesa-git
Proton Experimental
AMD RX 6700 XT

Post a proton log and screenshot or video

It's a known issue already, just wondering if anyone had further luck with it

Known as in game bug? Or as in vkd3d-proton or driver issue

I'm not sure if this is related to vkd3d-proton, but it seems that currently starfield doesn't work for RX 5xx and vega series card owners, the game starts up fine but half the models are simply missing.

So far every mention and every thread that I found on github, steam discussions and reddit mention that it's either rx 570/580/590 or vega cards. There's many reports like that in proton's starfield issue, some logs indicate that maybe this is a vkd3d-proton issue:
https://github.com/ValveSoftware/Proton/issues/7064#issuecomment-1709174112
https://github.com/ValveSoftware/Proton/issues/7064#issuecomment-1703031217
https://github.com/ValveSoftware/Proton/issues/7064#issuecomment-1703524568

None of known workarounds work, switching to vkd3d-proton latest commit, upgrading to mesa-git or linux 6.5, etc.

As said this is still very likely a driver problem (asked devs too) so a mesa issue needs to be made.