You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

Rise of the Tomb Raider tested on AMD RX 580

By - | Views: 48,344

To go along with Liam’s benchmarks of the game on his Nvidia GPU, I decided to also run some tests on my RX 580 to give you a picture of the AMD performance of the Rise of the Tomb Raider port. So, let’s go!

Disclosure: I participated in the closed Linux beta for ROTTR and thus received a key for the game from Feral.

Let’s first go over my gaming rig specs before we jump into the results. My system uses an AMD R7 1700 at 3.7GHz and 16 GB of 2133MHz DDR4 RAM. The GPU I am using is an Asus ROG RX 580 8 GB. On the software side I’m using Antergos with Linux 4.15.15 with Mesa 18.0.1. Feral’s Gamemode was installed and operational for these tests.

Due to time constraints I stuck to running the benchmark through the Lowest, Low, Medium, High and Very High without anti-aliasing at 1080p resolution. Benchmarks were repeated a couple of times on each preset to eliminate as many discrepancies as possible.

So, let’s have a look at the numbers:

On the Lowest preset the game quite simply ran flawlessly, maintaining an average of above 100 FPS during each of the three scenes the benchmark went through. The low minimum framerate during the Syria scene appears to be an oddity of this game that makes the minimum framerates in this benchmark largely meaningless. While monitoring the game, it never actually seemed to drop down to 24 FPS, so my guess is that some individual frames in the benchmark just take abnormally long to render and bring the minimum framerate way down. You can see similar numbers in my other benchmarks of the game but I wouldn’t consider these low minimums meaningful. I decided not to average them out so as to avoid looking like I am tampering with the results.

 

Low preset isn’t a big change from the Lowest in terms of performance. The game still maintains an average framerate of around 100 FPS throughout the benchmark.

 

 

On medium settings the game is finally starting to make the RX 580 work but the averages are still very much on the healthy side of 60 FPS and even according to the somewhat untrustworthy minimums the game is maintaining a stable framerate.

 

 

On High settings the gap to 60 FPS is narrowing but there’s still some wiggle room for anti-aliasing effects and possibly increased resolution here.

 

 

At Very High some of the Scenes are hitting near the desired 60 FPS average and dipping below the 60 FPS at times, although not to a point of unplayability. You could probably still enable some anti-aliasing and get away with it, but if you are unwilling to occasionally dip below the 60 mark you might need to drop some settings to achieve a constant framerate.

 

Overall I’d say this port is working quite wonderfully. Not only are AMD cards on the officially supported list, they would seem to be running quite well too. Do note however that 1st and 2nd generation GCN graphics cards (or older) are not supported, which makes sense considering the experimental state of the Vulkan drivers for those graphics card. According to Feral at a minimum you want an R9 285. So, if your GPU is either that or an R9 380, RX 470/570, RX 480/580 or better you should be good to go.

When it comes to the actual game, I sadly haven’t been able to test it too much. I played about 3-ish hours of the game during the beta and I didn’t run into issues, graphical or stability-wise so I think the game beyond the benchmark is also shipping in good condition. As far as the gameplay and story are concerned, I’ll leave the evaluation of the game to those with more time on their hands.

Article taken from GamingOnLinux.com.
20 Likes
About the author -
author picture
I'm a Linux gamer from Finland. I like reading, long walks on the beach, dying repeatedly in roguelikes and ripping and tearing in FPS games. I also sometimes write code and sometimes that includes hobbyist game development.
See more from me
The comments on this article are closed.
68 comments
Page: «7/7
  Go to:

lucinos Apr 21, 2018
I always assumed it is that Feral is just only interested on steam-only pulishing which is absolutely fine and I do not think these games would be published on other places anyway.

(Something about my opinion on DRM. I hate it but steam is not that bad at all. I could write more, I just mention for example that I prefer a lot more running steam than for example need to run a "genuine" cd.)


Last edited by lucinos on 21 April 2018 at 5:58 pm UTC
F.Ultra Apr 21, 2018
View PC info
  • Supporter
For some reason I cannot make it run fullscreen, even though fullscreen is selected everywhere it opens in window (which makes it cut the bottom and the right side since the window have the same size as the screen plus the size of the bars and so on). Mesa 18.0.1 on RX480 and kernel 4.16
Ehvis Apr 21, 2018
View PC info
  • Supporter Plus
Quoting: lucinosI always assumed it is that Feral is just only interested on steam-only pulishing which is absolutely fine and I do not think these games would be published on other places anyway.

It's highly unlikely that Feral has anything to do with it. Square Enix likely dictates that Feral can only publish in place where they do. They're a triple-A publisher and as such they are highly protective of their IP. And in their eyes, this is the way to protect that.
F.Ultra Apr 22, 2018
View PC info
  • Supporter
Quoting: F.UltraFor some reason I cannot make it run fullscreen, even though fullscreen is selected everywhere it opens in window (which makes it cut the bottom and the right side since the window have the same size as the screen plus the size of the bars and so on). Mesa 18.0.1 on RX480 and kernel 4.16

Interestingly it went a little bit better if I choose windowed in the Feral launcher since that made the window borderless and thus the cut off is much smaller, however if I then ingame change to/from fullscreen then the full bordered window appear again.
m0nt3 Apr 24, 2018
I have had two hardlocks in ~17 hours of play.It seems completely random.


Last edited by m0nt3 on 24 April 2018 at 1:21 pm UTC
drlamb May 1, 2018
Update: 4.17rc2 + Mesa 18.X-git results in 37-40fps. So about +5fps better than mesa 17.3.8. Still have no idea why 18 is required for Vega GPUs.
lucinos May 1, 2018
Quoting: drlambUpdate: 4.17rc2 + Mesa 18.X-git results in 37-40fps. So about +5fps better than mesa 17.3.8. Still have no idea why 18 is required for Vega GPUs.

probably because they only tested that and they only test on ubuntu so they have no idea the "real" minimum requirements which is not just mesa.

I think it is better to simple say mesa 18 as a minimum requirement than saying something more precize but more complicated even if they know it.


Last edited by lucinos on 1 May 2018 at 12:36 pm UTC
Scoopta May 1, 2018
Quoting: drlambUpdate: 4.17rc2 + Mesa 18.X-git results in 37-40fps. So about +5fps better than mesa 17.3.8. Still have no idea why 18 is required for Vega GPUs.
Vega has been having a lot of weird issues. I don't have Vega but I know it still has polygon culling issues in Civ VI. I imagine it requires 18 to not be buggy but this is just a guess on my part.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.