In an effort to make things as clear as possible, I decided to do some additional testing with Mad Max [Steam, Feral Store]. More specifically, in OpenGL for Mad Max at release vs the beta.
This is important, since our previous benchmarks (and every other website and person who ran benchmarks) will be affected by this.
Why was this not tested before? Well, we weren't made aware of any changes to the OpenGL renderer in Mad Max. There should have been no need to do tests like this since the whole idea behind the Beta was to test Vulkan specifically, but hopefully this will help clear things up a bit.
I ran some of my own tests using GLXOSD's benchmarking tool coupled with my speedy SSD on the Very High preset (with no extra game adjustments) and here's what I found. The results, sadly, speak for themselves. Done in two completely different areas to be sure it wasn't a fluke.
As always, benchmarks should always be taken with a grain of salt. It will depend heavily on your system setup. Not just hardware, but the exact distro and libs you have too all affect the numbers.
This was tricky to do, since the Beta version does have other issues with OpenGL, which is in the form of crash bugs. I've had a few crashes I've reported to Feral in the beta version when using OpenGL, so hopefully those can also get fixed. It's also tricky since the original release didn't feature a benchmark mode, so it had to all be done manually.
The good news is that Feral Interactive are aware of it, so they can look to fix it. The other good news, is that Vulkan is still performing better than both versions of the game when using OpenGL.
This regression might also be affecting the Vulkan renderer, so it's possible when fixed both the OpenGL and Vulkan versions could see a boost, although the OpenGL boost would likely only be putting it back to normal levels.
Finally, something to remember: This is exactly what a Beta test is for. Article taken from GamingOnLinux.com.
This is important, since our previous benchmarks (and every other website and person who ran benchmarks) will be affected by this.
Why was this not tested before? Well, we weren't made aware of any changes to the OpenGL renderer in Mad Max. There should have been no need to do tests like this since the whole idea behind the Beta was to test Vulkan specifically, but hopefully this will help clear things up a bit.
I ran some of my own tests using GLXOSD's benchmarking tool coupled with my speedy SSD on the Very High preset (with no extra game adjustments) and here's what I found. The results, sadly, speak for themselves. Done in two completely different areas to be sure it wasn't a fluke.
As always, benchmarks should always be taken with a grain of salt. It will depend heavily on your system setup. Not just hardware, but the exact distro and libs you have too all affect the numbers.
This was tricky to do, since the Beta version does have other issues with OpenGL, which is in the form of crash bugs. I've had a few crashes I've reported to Feral in the beta version when using OpenGL, so hopefully those can also get fixed. It's also tricky since the original release didn't feature a benchmark mode, so it had to all be done manually.
The good news is that Feral Interactive are aware of it, so they can look to fix it. The other good news, is that Vulkan is still performing better than both versions of the game when using OpenGL.
This regression might also be affecting the Vulkan renderer, so it's possible when fixed both the OpenGL and Vulkan versions could see a boost, although the OpenGL boost would likely only be putting it back to normal levels.
Finally, something to remember: This is exactly what a Beta test is for. Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: GuestThanks for calling attention to this and running new benchmarks.No problem, it's good to shed light on things. I'm here to serve my readers, no one else. Making things clear is important.
0 Likes
Quoting: rustybroomhandleI am running Manjaro and have noticed on kernel 4.9 this game stutters terribly, with frame rate wildly fluctuating. I booted up with kernel 4.5 and all of a sudden it's smoother than suppository dipped in Vaseline.
I also noticed that performance got lot worse with 4.9 kernel. After digging little deeper I noticed that threads were moving between cores quite frequently. So far htop has been best tool for debugging this as it shows which core thread uses and even shows threads by default.
I made a script that locks threads to dedicated cores and that helped quite a lot. Vulkan is now pretty smooth nearly all the time.
I uploaded the script to GitHub: https://github.com/anzah1/task-affinity-balancer
2 Likes, Who?
rustybroomhandle Apr 2, 2017
Quoting: AnzaQuoting: rustybroomhandleI am running Manjaro and have noticed on kernel 4.9 this game stutters terribly, with frame rate wildly fluctuating. I booted up with kernel 4.5 and all of a sudden it's smoother than suppository dipped in Vaseline.
I also noticed that performance got lot worse with 4.9 kernel. After digging little deeper I noticed that threads were moving between cores quite frequently. So far htop has been best tool for debugging this as it shows which core thread uses and even shows threads by default.
I made a script that locks threads to dedicated cores and that helped quite a lot. Vulkan is now pretty smooth nearly all the time.
I uploaded the script to GitHub: https://github.com/anzah1/task-affinity-balancer
Cool beans. Will give it a shot.
0 Likes
Patreon
PayPal
See more from me