82
vkd3d 2.0 (gitlab.winehq.org)
submitted 5 months ago by to c/linux_gaming@lemmy.world
4 comments fedilink hide all child comments

all 4 comments

sorted by: hot top controversial new old
[–] 10 points 5 months ago (3 children)

Note that this isn't vkd3d-proton, the d3d12 implementation that Valve's Proton and most gamers are using.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 1 point 5 months ago (2 children)

    Is there much difference? Performance compatibility etc?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 5 months ago

    I don't have hard numbers, but my understanding is that in general, Proton is more receptive to hacks which get stuff working, or working faster, but that aren't proper solutions. WINE has a greater preference toward correctness, so compatibility is a bit worse, as is performance.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 5 months ago

    Bit different philosophy. Wine does everything by the book to ensure maximum compatibility both now and in the future, even if it costs performance. Proton does per game dirty fixes, which requires more maintenence, but game with these fixes work better.

  • permalink
  • fedilink
  • source
  • parent
    • 1 comment in c/steamdeck@sopuli.xyz view that post
    [–] 5 points 5 months ago

    hell yeah, this rocks

  • permalink
  • fedilink
  • source
    •