It performs the exact same as the game running under DX9. If you wait and let the shader cache build for long enough, the apparent frame rate increase which is present initially (while the game is stuttering) is gone, it's same thing with DXVK or DXVK-async. It did get rid of the additional stuttering but it turns out it doesn't increase performance to any extent whatsoever. So I tried DXVK-async and did the process all over again. It seems that DXVK doesn't deal well with the geometry or textures in this game because I'm pretty sure the stutters happen according to how much detail is on-screen at the moment, quite curious (and if you move the camera too fast it happens even if there's not a whole lot of detail visible). Normal DXVK has endless stutter - the more frequent stutters at the start do go away but the game simply won't become stutter-free at any point, it will always happen during camera movement. Launched it, waited until the shader cache compilation stutters in the intro and menu went away, then loaded every mission in the game and did the same thing, moving around for a bit. I tried the game with the latest DXVK version (1.9.3), both the standard and async versions. Did you check DXVK? Just copy and paste all x32 libraries near exe. If you have anything against, please speak out further to investigate the issue further (with your specs at best). If you can, please leave alone Ragnos config with culling value. The config forces low details as a downside, but performance was better vs stock low details if memory serves. If it no longer meets these criteria, you can reassess it.
If you can improve it further, please do so. At this time, the multiplayer servers for this game have been discontinued and shutdown. 1 - The CPU affinity fix: The game process already sets itself to every core available as it should, it just doesnt use more than 2 cores in reality due to engine limitations. Tom Clancys Splinter Cell: Blacklist has been listed as one of the Video games good articles under the good article criteria. Talk:Tom Clancys Splinter Cell: Conviction. Previous config (the one above Ragnos) did nothing to me, but Ragnos would stay with the new culling value. Talk:Tom Clancys Splinter Cell: Blacklist. I only didn't test new culling value suggested by someone else here:īut its value was changed already by Ragnos in the config, but it was different. Nothing else really made a difference to me, and I tried a lot of things, including affinity, which in fact, could be deleted because of varying results (if any).
I highly doubt that you really use an ancient CPU, so you can notice any difference using Ragnos config, because it helped me a lot. Then there must be something else wrong with multithreading in this game.
0 kommentar(er)
