this post was submitted on 11 Sep 2023
755 points (98.1% liked)

Games

32373 readers
1927 users here now

Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.

Weekly Threads:

What Are You Playing?

The Weekly Discussion Topic

Rules:

  1. Submissions have to be related to games

  2. No bigotry or harassment, be civil

  3. No excessive self-promotion

  4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts

  5. Mark Spoilers and NSFW

  6. No linking to piracy

More information about the community rules can be found here.

founded 1 year ago
MODERATORS
quinten@lemmy.world
shitpostpolice@lemmy.world
Dremor@lemmy.world
Dremor@jlai.lu
755
Open source community figures out problems with performance in Starfield (www.destructoid.com)
submitted 1 year ago by Mystify0771@lemmy.world to c/games@lemmy.world
228 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] ono@lemmy.ca 41 points 1 year ago* (last edited 1 year ago)

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.