55
DXVK 3.0 Released With DXBC-SPIRV For Shader Compilation, Descriptor Heaps By Default
(www.phoronix.com)
this post was submitted on 25 Jun 2026
55 points (100.0% liked)
PC Gaming
14915 readers
149 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The beauty of the setting is that we can choose a different FPS limit for each game, regardless of which API it uses, even if the game doesn't offer a limiter of its own. 90 is more than enough for a lot of isometric-view games. 180 is helpful in competitive first-person shooters, where every frame is an advantage. 50 or 60 in graphics-intensive turn-based games like Baldur's Gate 3* lets the art shine while keeping my GPU cool and my power bill relatively tame.
*BG3 has its own limiter, so in its case, the same can be done without the dxvk setting.
Also, lower frame rates are generally less noticeable on smaller displays (at any given distance). We can take advantage of this to save money and extend hardware life when not gaming on an IMAX screen.