You can sign up to get a daily email of our articles, see the Mailing List page!
Support us on Patreon to keep GamingOnLinux alive. This ensures we have no timed articles and no paywalls. Just good, fresh content! Alternatively, you can support us on Paypal and Liberapay!
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.

OpenGL 1.0 OpenGL Beta Vulkan Mad Max Stable vs Beta - Outer GravesAntergos Linux, 1080p, i7 5960x, 980ti Very High Vulkan 126OpenGL 1.0 110OpenGL Beta 49 12611049 0265278104130 Average FPS

OpenGL 1.0 OpenGL Beta Vulkan Mad Max Stable vs Beta - The Big NothingAntergos Linux, 1080p, i7 5960x, 980ti Very High Vulkan 145OpenGL 1.0 129OpenGL Beta 68 14512968 0295887116145 Average FPS


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.
17 Likes, Who?
Comments
Page: «3/3
  Go to:

Ehvis 31 March 2017 at 11:37 pm UTC
View PC info
  • Supporter
I've tested the old version against the new Vulkan in a couple (non benchmark) camps that gave me very low frames before. The bad one increased from 22 to 35, which is a big difference. Note that this is at very high settings and on 3440x1440. That changes the game from stuttery to perfectly playable. I just wish that NVidia would get G-SYNC working on Vulkan.

I have noticed a couple of graphical artefacts though. At one point the canteen flashed before filling it up. Another one was that I saw some flashing white lines that looked like they could have been ground mesh edges. Haven't been able to screenshot them, so I may have to try and screen capture a video.
natewardawg 1 April 2017 at 12:23 am UTC
tripy
natewardawgIf I remember, I will post my stats when I get it running on my other machine. I may do it at 1920x1080 though.

Thanks. Much appreciated.

Edit: wups.. It was wishful thinking, but I've got a GTX 960, not 970.
Damn, time to get some Z I guess too.

Here it is... I actually did the benchmark at both 720p and 1080p with normal quality.

Specs:
i7-6700K
GTX 960
32 GB RAM

720p:
avg: 80.905754 min: 57.537403 max: 87.573341

1080p:
avg: 81.353348 min: 64.316956 max: 86.662621

Yep, almost exactly the same... so this scene is definitely CPU bound. So, I'm pretty sure upgrading your system with a Ryzen chip would cause this scene to outperform my system even with the same GPU. I'm going to do some more tests for the other two quality levels, at some point


Last edited by natewardawg at 1 April 2017 at 12:42 am UTC. Edited 6 times.
natewardawg 1 April 2017 at 12:48 am UTC
Gaming On Windows 10!!! Too funny Liam!
Swiftpaw 1 April 2017 at 6:16 am UTC
Thanks for calling attention to this and running new benchmarks. Vulkan is great, and the improvements are great, no question about any of that. But, facts are facts, and sadly the original takeaway based on a regressed/bugged benchmark wasn't right. D3D ports will probably never be quite as good, but if Feral's ports can squeeze out better performance with VLK as these benchmarks show, we end up with better ports, and that's awesome! I hope we start getting more native-Vulkan-focused games and fewer ports, but ports will be a thing for a long while, so this is great to have in the meantime.


Last edited by Swiftpaw at 1 April 2017 at 6:17 am UTC. Edited 2 times.
liamdawe 1 April 2017 at 9:10 pm UTC
SwiftpawThanks 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.
Anza 2 April 2017 at 6:13 pm UTC
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
rustybroomhandle 2 April 2017 at 10:57 pm UTC
Anza
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.
edo 4 April 2017 at 1:43 am UTC
so not close to Dx11
Swiftpaw 4 April 2017 at 4:14 am UTC
edoso not close to Dx11

Well on high settings, VLK is about 40% behind DX in this port. On low it's more like 50%.

https://www.reddit.com/r/linux_gaming/comments/62ilrk/
  Go to:
While you're here, please consider supporting GamingOnLinux on Patreon or Liberapay. We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

We also accept Paypal donations and subscriptions! If you already are, thank you!

Due to spam you need to Register and Login to comment.


Or login with...

Livestreams & Videos
Official Livestreams
  • Borderlands: The Pre-Sequel continued again
  • Date:
Community Livestreams
  • RPGoodness: "Dragon Age Origins" (via Wine)
  • Date:
See more!
Popular this week
View by Category
Contact
Latest Forum Posts
Facebook