The new version comes with improvements and timely corrections to the project, while version 1.1 returns to the development board.
DXVK is a fantastic tool that came to the Linux world, more precisely to the gaming world, where it enabled the play of a few thousand games that could not be played before, with only WINE. It now has more improvements implemented in this version.
With the growing compatibility of more and more games, the evolution of DXVK is also growing and surprising. Who could imagine that until last year (2018), the project was just a hobby and it could help migrate games to Linux in a snap, really amazing.
For this version, 1.0.3, the following enhancements and fixes have been added:
DXVK DLLs now include version information, which some games may use;
– Fixed issue where hashing geometry shaders with stream output metadata returned undefined results. This can cause state cache files to grow indefinitely;
– Fixed issue where undefined data would be passed to driver for specialization constants not used during pipeline compilation. This may have caused unexpected shader cache failures;
– Surface loss now has a much more harmonious handling;
– Game Anno 1800: Fixed serious performance issue, enabled with option d3d11.allowMapFlagNoWait;
Games like Dark Souls Remastered and Grim Dawn: Added an alternative solution to fix rendering issues on Nvidia GPUs;
– Star Citizen: Fixed invalid geometry shader, causing GPU crash and driver crashes;
But what about DXVK 1.1?
So he was even released but after several bugs and crashes were reported, the main developer, Philip Rebohle, decided to take him down to fix these pending issues and release the following note along with version 1.0.3:
The release was taken back because it was crashing the games and the GPU crashing for some users. If you have a build environment set up, test the last master branch with as many games as possible to help find and troubleshoot problems.
If you want to directly download DXVK and manually implement it or check out its source code, just access your GitHub official. This article doesn't end here, keep exchanging an idea there in our forum.
Hope to see you next, a big hug.
_____________________________________________________________________________ See any errors or would you like to add any suggestions to this article? Collaborate, click here.