this post was submitted on 06 May 2024
47 points (98.0% liked)

PC Gaming

8563 readers
598 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] autotldr@lemmings.world 3 points 6 months ago

This is the best summary I could come up with:


Valve developers have done a lot of work over the years to improve AMD GPUs on Linux, and continue to do so with the Steam Deck using AMD and it seems like they're now getting stuck into NVIDIA too.

Specifically for NVK, the open source Vulkan NVIDIA driver in Mesa which has seen a lot of focus recently on bringing up performance.

Posting on X (formerly Twitter) Valve developer Pierre-Loup Griffais mentioned:

The two patches noted from developer Mohamed Ahmed are a Mesa Merge Request for get the Vulkan extensions VK_EXT_image_drm_format_modifier support hooked up.

This is needed to support modifiers in NVK and ensure correctness when dealing with the nouveau GL driver."

Bigger version of the attached image from the post above:


The original article contains 171 words, the summary contains 122 words. Saved 29%. I'm a bot and I'm open source!