A prominent open-source dev publishes their findings as to what's going on with Starfield's performance, and it's pretty darn strange.
According to Hans-Kristian Arntzen, a prominent open-source developer working on Vkd3d, a DirectX 12 to Vulkan translation layer, Starfield is not interacting properly with graphics card drivers.
Looks like Hans implemented a workaround in vkd3d-proton 2.10, using the open-source AMD vulkan driver on linux (RADV).
Device generated commands for compute
With NV_device_generated_commands_compute we can efficiently implement Starfield’s use of ExecuteIndirect which hammers multi-dispatch COMPUTE + root parameter changes.
Previously, we would rely on a very slow workaround.
NOTE: This feature is currently only enabled on RADV due to driver issues.
I don’t imagine it will take long for this to make its way into a Proton experimental release. Folks with AMD graphics who are comfortable with linux might want to give it a try.
Looks like Hans implemented a workaround in vkd3d-proton 2.10, using the open-source AMD vulkan driver on linux (RADV).
I don’t imagine it will take long for this to make its way into a Proton experimental release. Folks with AMD graphics who are comfortable with linux might want to give it a try.