Confused on Steam Play and Proton? Be sure to check out our guide.
We do often include affiliate links to earn us some pennies. See more here.

Feral Interactive have teamed up with Crystal Dynamics and Square Enix once again to bring a top title to Linux, this time we have Rise of the Tomb Raider.

Disclosure: My key was provided by Feral Interactive ahead of release.

It’s no secret that the Linux port of the previous Tomb Raider had some performance problems, some of which were improved with a patch after release. I’m pleased to say that with Rise of the Tomb Raider, Feral Interactive have done an incredible job overall.

Even though the Linux release is coming in a good while after the Windows release, we do get the 20 Year Celebration edition which includes all the DLC. So we have the complete edition right away along with all the polish that was put into it since release.

Benchmarks

First up, let's see how well it runs with the settings on the absolute maximum, with the different AA options that are possible. Do note, that the game itself warns you that SSAA is very heavy and will reduce performance a lot. Also, Pure Hair is turned on by default for all options above the Low preset. The different presets, even the highest preset actually leaves a few options lower than the maximum, so I manually put them up for these tests. Another note about this: the Very High textures option in use for these first tests, does require a GPU on Linux to have 6GB VRAM (I've seen it practically hit the limit):

As you can see, FXAA and SMAA actually give quite reasonable performance, especially considering all other settings are cranked up to their absolute highest. Even SSAA x2 didn't do too badly with it hitting just over 60FPS average overall. To be clear though, the above results and settings are something very few people will be able to use.

Here's some additional benchmarks for settings people are actually likely to use, from the Very High preset to the Lowest, all with FXAA turned on apart from Lowest which I manually turned off (trying to simulate what people might do):


Note: In the Linux version, the Very High preset leaves textures on High, whereas on Windows it sets it to Very High.

As a bonus, here's a comparison with Windows 10. Do note, that the Windows version has two additional modes of Ambient Occlusion not included in the Linux build, so these tests are simply done with it set to "On" in both versions to compare properly. Also, to keep it to the point we're only using the "Overall Score" given here:

As expected, there's a performance gap, although it's actually less than I expected. Given that these are some insanely high settings with everything manually put up higher than the presets go, the Linux version holds up reasonably well overall. Especially considering the high VRAM use in the Linux version with my 6GB 980ti at it's limits.

Here's how the Linux version holds up on more reasonable graphical settings:

Not bad, not bad at all.

Thoughts

We could run benchmarks until we're red in the face, however, what the benchmarks actually show is quite limited of course and is nothing in comparison to a first-hand playthrough. I started off playing it on the "High" preset, but honestly, I set it to "Very High" quite quickly since it was so damn smooth and it remained smooth even then. I did keep textures down to the default of High, due to the VRAM use. I have to say, I'm personally extremely happy about how smoothly Rise of the Tomb Raider has been running on Linux.

If you thought the first Tomb Raider was action-packed, you’re in for a whole new world of crazy here. Rise of the Tomb Raider certainly isn’t gentle with thrusting you into daunting situations right off the bat. It's also quite the emotional roller-coaster of a game, one that at times blurs the lines between game and movie in the way it's presented.

Not only are you thrown in at the deep end with Rise, you’re also shown how incredibly good-looking this game is right away. Seriously, it's easily one of the best looking games available on Linux right now, some truly gorgeous scenes can be found throughout the game. I've found myself often just stopping to have a look around.

Those pictures are on the standard “High” preset with no other adjustments, yet it looks absolutely gorgeous. It's not just the graphical fidelity, but the actual style to the game is fantastic too, all the little details have made me really appreciate it.

In the first game, Lara was forced into survival against her will. Things are a bit different this time around, as Lara has gained confidence and a sense of self and is literally seeking out the danger of her own free will. You’re on the hunt for some sort of artifact to grant eternal life, Lara is sure it exists and decides to follow her father’s path. Not the most original of story basics, but it’s exciting to actually play through given what Crystal Dynamics have done with it.

The voice actor for Lara, Camilla Luddington, reprises her role for Rise of the Tomb Raider and does just as incredible a job as before. She's really believable, you really feel the intensity of everything thanks to her excellent work here.

While Rise has ample amounts of serious action, requiring some fine aim and reflexes, there's also a healthy dose of puzzles and challenges to overcome as well. As you progress, you will find certain relics that requires Lara to have a certain level of understanding in specific languages.

This makes the exploration side of it a little more fun and varied too and at times, this will give you a reason to fast-travel back to another area, once you learn enough to translate something previously left behind. This brings me to another point, there's so many camps spread across the quite large map, that actually switching between locations is incredibly easy.

Great, but what about actual Tombs to raid? Well there's optional tombs in there too, like the first one you find which is essentially a huge wooden ship buried in the ice:

While they're optional, they're certainly worth doing for the extras that they give you.

To me, it feels like they took all the good bits from the first game and expanded upon them giving you more options everywhere. There's more skills to learn for example, with the previous game having around 24 split across three classes, with Rise given you a whopping 50 skills! It's not just that there's more of them, they're much more interesting to actually unlock too. Some quite menacing in fact, like the ability to put a trap on an enemy corpse.

In addition to all the exploration, the scavenging, translating, region challenges and tomb raiding there's also completely optional missions you can do. Given out by various people you can find spread throughout the game. It's quite a nice way to take a break from the main story, while still giving you some extras to help you along your way, it makes the game a lot more varied that's for sure.

I think one of the great things about Rise of the Tomb Raider, is that it gives that open-world feeling with you being able to travel between areas and do things you miss, while not being overwhelming. It's a good mix of styles bundled together, to allow you to really push through when you want to, and take a break doing some of the smaller (but still fun) aspects of the game whenever you want.

There's a lot I haven't touched on here, partly because I don't want to spoil literally everything and also because it's such a big and varied game, if you spend a little time with it and don't rush through. Sometimes it's the little things, like talking to a character and a rabbit suddenly hops into view, looks right at the screen and then hops away…

As a reminder, to get the most performance out of the Linux version, you will likely want your CPU in Performance mode. You can do this using Feral's GameMode tool, by using this GNOME Shell extension or by doing it manually in terminal:

echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

Replace "performance" with whatever mode you wish to revert it back

The Final Verdict

I haven’t been this engrossed in a game since—well—ever? I’m not being hyperbolic here either, it has such a fantastic mix of gameplay elements all wrapped up in lush detailed graphics. From the moment I first loaded it I just couldn’t put it down. Feral did a really sweet job on the port as well.

I don't want to get ahead of myself here, but given what a great job they did, this gives me high hopes for Shadow of the Tomb Raider (the next title) to be on Linux and run well.

You can find Rise of the Tomb Raider on Humble StoreFeral Store and Steam. Fantastic to have another AAA title on Linux.

We will have a livestream of it tonight and tomorrow with Sin taking the helm, keep an eye on our Twitch channel!

Article taken from GamingOnLinux.com.
50 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. You can also follow my personal adventures on Bluesky.
See more from me
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
221 comments
Page: «10/12»
  Go to:

Comandante Ñoñardo Apr 28, 2018
So far it performs excellent on my PC, ~70 fps in the start location and Syria. But I have some problems, probably because I have Nvidia driver 390, not recommended 396. When I install 396, after rebooting I see this:
![](https://getfile.dokpub.com/yandex/get/https://yadi.sk/i/o8bM99t53UcvHJ)

I'll try to install it again next week after upgrading Ubuntu to 18.04.
Well, I have 18.04 now, and 396 driver still doesn't work. I wish I bought RX 480 instead of that Nvidia crap.

Also: https://www.pcgamer.com/nvidias-latest-gpu-driver-is-causing-installation-headaches-for-some-gtx-1060-owners/

Just curiousity:
What is the text of the nvidia_icd.json?
ageres Apr 28, 2018
You mean /usr/share/vulkan/icd.d/nvidia_icd.json?
Jan Apr 28, 2018
Performance is pretty good, but it’s the most unstable Feral game I’ve ever played on Linux or Mac. In Ubuntu 17.10 with the recommended NVIDIA beta drivers it freezes constantly, especially in the Soviet facility. One of the optional tombs is impossible to complete due to freezing/lock-up of the whole screen. I’m on a fresh install, Skylake Core i7, 32GB RAM and a GTX 1080.
D34VA_ Apr 28, 2018
Performance is pretty good, but it’s the most unstable Feral game I’ve ever played on Linux or Mac. In Ubuntu 17.10 with the recommended NVIDIA beta drivers it freezes constantly, especially in the Soviet facility. One of the optional tombs is impossible to complete due to freezing/lock-up of the whole screen. I’m on a fresh install, Skylake Core i7, 32GB RAM and a GTX 1080.

Turn off the Steam overlay and/or make sure to launch in desktop mode and not Big Picture.
m2mg2 Apr 28, 2018
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.
Comandante Ñoñardo Apr 28, 2018
You mean /usr/share/vulkan/icd.d/nvidia_icd.json?
yes..
ageres Apr 29, 2018
You mean /usr/share/vulkan/icd.d/nvidia_icd.json?
yes..
{
    "file_format_version" : "1.0.0",
    "ICD": {
        "library_path": "libGLX_nvidia.so.0",
        "api_version" : "1.0.65"
    }
}
Comandante Ñoñardo Apr 29, 2018
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-
lucifertdark Apr 29, 2018
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-
I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.


Last edited by lucifertdark on 29 April 2018 at 9:39 am UTC
tuubi Apr 29, 2018
View PC info
  • Supporter Plus
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-
I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.
Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.
jens Apr 29, 2018
  • Supporter
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-
I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.
Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.


Last edited by jens on 29 April 2018 at 11:57 am UTC
DanglingPointer Apr 29, 2018
Too add salt to everyone's injury...
- I've never had a crash in 20 hours of play
- I'm on an UNsupported distro Ubuntu 16.04.4
- I'm on an UNsupported GPU R9-290X
:D

- I do however have Linux Kernel 4.16.5
- Mesa 18.0.1
- 32GB RAM

It just works!
Faattori Apr 29, 2018
Just completed my play through too on unsupported OS and unsupported drivers, without crashes. Sometimes after playing for a while turning with the mouse would turn very stuttery but that is apparently a game bug and not a port issue.
mooln Apr 29, 2018
Has someone had luck with this game on Debian 9?
Ehvis Apr 29, 2018
View PC info
  • Supporter Plus
Had no problem with crashing on Nvidia 390.48 drivers either.

I did see one graphical glitch with shadows or AO though:
![](https://steamuserimages-a.akamaihd.net/ugc/2429006218666687244/1B7F9A5683591445DDE61567B1B82AE82355624B/)

Does this happen on 396 drivers?
tuubi Apr 29, 2018
View PC info
  • Supporter Plus
I did see one graphical glitch with shadows or AO though:
![](https://steamuserimages-a.akamaihd.net/ugc/2429006218666687244/1B7F9A5683591445DDE61567B1B82AE82355624B/)

Does this happen on 396 drivers?
I haven't seen anything like that on either driver. You could try fiddling with your game config?
m2mg2 Apr 29, 2018
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-
I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.
Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

What version of Fedora are you running?
Comandante Ñoñardo Apr 29, 2018
Just completed my play through too on unsupported OS and unsupported drivers, without crashes. Sometimes after playing for a while turning with the mouse would turn very stuttery but that is apparently a game bug and not a port issue.

What version of Ubuntu are you using?

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

No new activity in the Linux depots
jens Apr 29, 2018
  • Supporter
Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-
I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.
Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

What version of Fedora are you running?

Fedora 27 fully updated, thus now kernel 4.16.3-200.fc27.x86_64.
I'm using negativo17 repositories for Nvidia, Steam and some other packages (https://negativo17.org/repositories/). I do not use rpmfusion.


Last edited by jens on 29 April 2018 at 4:59 pm UTC
matou68 Apr 29, 2018
HI

i don't have rise of tomb raider. i have steam with a 1080p desktop resolution
wen i start F1 2017 (vulkan) in 4K resolution (3840*2160) i have the error Game Crash with signal SIGSEGV(11): segmentation fault
wen i start Mad Max (beta vulkan) in 4K resolution (3840*2160) i have the error Vulkan call failed: -4

wenn i put my linux destop to 4K resolution, then start steam with 4K resolution desktop.
F1 2017 and Mad Max start fine at 4K resolution.

GTX1070, kernel 4.16.3 (with 4.16.4 and 4.16.5 kernel panic), 396.18 driver, ubuntu 17.10, cinnamon 3.4.6
you have a problem if the desktop resolution is different to the game resolution
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.