this post was submitted on 20 Sep 2024
29 points (93.9% liked)

PC Gaming

8573 readers
262 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, within reason.
  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
EXiLExJD@lemmy.ca
UncleBadTouch@lemmy.ca
KairuByte@lemmy.dbzer0.com
29
Wow! Microsoft DirectX Adopting SPIR-V Moving Forward (www.phoronix.com)
submitted 1 month ago by alessandro@lemmy.ca to c/pcgaming@lemmy.ca
3 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] ramjambamalam@lemmy.ca 1 points 1 month ago (1 children)

Interesting, so it allows DirectX to use the same shaders as Vulkan? But isn't the advantage of Vulkan that it has less overhead than DirectX? Does this mean anything for gamers, or does it just make the graphics programmers' jobs easier when they can use the same shaders for either renderer?

[โ€“] fulg@lemmy.world 3 points 1 month ago

Vulkan and DirectX could already share shaders, because the input for both was already HLSL. The difference is the intermediate representation of the compiled shaders that will now be the same in the future (SPIR-V for both).

The real winners here are driver programmers at NVIDIA/AMD/Intel, since they will no longer have to develop support for both DXIL and SPIR-V (which are similar in concept but different in implementation). How much of that will be true in practice remains to be seen, but I am hopeful.

There are tools to analyze, process and transform SPIR-V bytecode already, presumably those will work for DX12 shader model 7 too. It might make performance analysis easier, same with debugging via a tool like RenderDoc that supports SPIR-V but not DXIL.

As for the overhead of DirectX, with DX12 this is largely not true anymore, both are high performance APIs with comparable overhead (i.e. as little as possible).