Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on User talk:Kms6872

Hi,

Saw you added your previously added DXVK-workaround back to the Stray page after I removed it. Nothing wrong with that of course, but I wanted to discuss more in-dept if we really want to keep it in there. My reasons against it currently are: - The game officially supports Windows 10 and above. Your fix allows it maybe to run on Windows 7 while it is not meant to in an unofficial way, which can always lead to compatibility-issues and other issues as these old OS's don't receive any Windows- or GPU-issues anymore. Do we really want to serve people a possible quite bad experience? There is probably a very good reason why developers don't develop these games for these old unsupported systems anymore. - You mention that it also can solve some issues with Windows 10; your source mentions nothing about that to be honest. So, this mostly seems to be a workaround to get the game running on Windows OS below 10, maybe it should be marked as such if we keep it? - DXVK is in constant development (you "hardcoded" any links to the 1.10.2 version, which isn't very nice honestly), but what says a future build of DXVK couldn't break the game? - DXVK is made originally to run on Linux. It was not made for originally and extensively tested on Windows. Using it on Windows will make you miss out on some features of it. And from my testing with some games stability and performance varies quite a bit. As DXVK was not made to run modern games on Windows, I personally don't feel very comfortable with potentially serving people a massive workaround that might result in severe bugs in-game (remember, this was not extensively tested). - DXVK thus translates the DX11-API calls of this game to Vulkan-API calls. This is in my opinion not just a workaround in this usage-case, as it affects almost all code of the game itself. Do we really feel comfortable providing this "sledgehammer"-solution for this "problem"? - DXVK can be used for almost any game that does not support Windows 7 to make it run on it (with varying success of course). Do we really want people to add this to wiki-pages for every non-Win-7 it works for? It sounds then more like a throw-at-the-wall-and-see-what-sticks-solution..... - The devs of the game just released Hotfix 2, which fixes a boot-related problem that has to do with the GPU-driver. Are you sure your original issue on Windows 10 isn't fixed with it (what was it anyways to begin with? I suspect stutter and lag issues? Sure this doesn't still happen using DXVK after clearing the shader cache?) thus making this workaround superfluous for Windows 10? - My question also: did you test this solution yourself to check if it fully works ok using both Windows 7 and 10/11?

What do you think? :)