Oh baby, here we go. Thanks to Feral Interactive, XCOM 2 has been officially released today for SteamOS & Linux. Disclosure: Copy provided by Feral Interactive
I’m a massive fan of the original UFO: Enemy Unknown (X-COM: UFO Defense) game and the re-make XCOM which was ported over by Feral Interactive, so to have XCOM 2 on day 1 is excellent. I'm going to be honest, this has been one of the most exciting games to come in the history of Linux gaming for me. Sadly, the initial release has not lived up to my expectations.
Note: It’s another Linux port where Intel and AMD are not currently supported. It doesn’t mean it won’t work, it’s just not supported right now.
The good news is the multiplayer is cross platform! As they announced on Twitter:
When #XCOM2 launches tomorrow on Mac & Linux it will feature cross-platform multiplayer across Mac, Linux and Windows! You ready for that?
— Feral Interactive (@feralgames) February 4, 2016
System requirements:
Recommended
OS: Ubuntu 14.04.2 64-bit or Steam OS
Processor: Intel i7 series
RAM: 8GB
Graphics: 2GB NVIDIA 960
Minimum
OS: Ubuntu 14.04.2 64-bit or Steam OS
Processor: Intel i3-3225 3.3 GHz
RAM: 4GB
Graphics: 1GB NVIDIA 650
Port report
Obviously take this with a pinch of salt considering my hardware, Intel i7 and Nvidia 980ti. Nvidia driver version 355.11.
I've only been able to spend a few hours with it today, so a full review will come later.
It's another title to use Feral Interactive's new launcher system and it's quite nice. I love any game that allows me to pick resolution, and what monitor before it launches and tries deciding it all for me and screwing itself up. Although, that's not really an issue for me now I'm on a single monitor, but for people using more than one monitor it's going to help a lot.
The auto detect graphical settings sets everything to the lowest it can, even with my 980ti so I had to fiddle about with all that at the start. That was slightly annoying, but not a major issue as they do have a "preset" option, so I cranked it up to High.
We seem to only have either disabled, or FXAA for anti aliasing options. FXAA looks pretty bad, so I'm not too happy about it. I know Windows has MSAA, so I would have liked that option on Linux even if it hit performance more, it would still look a lot better. See how it looks on High at 1920x1080 below:
You can clearly see jagged edges all over my soldier, not looking good at all.
2560x1440
This has been giving me between 35-55FPS which isn't too bad, but quite a bit lower than I expected for my card.
The first time I fired a weapon the game stuttered so badly it basically skipped the entire firing sequence, and jumped to a dead Advent soldier on the floor. I heard it all happen, but didn't get to see it which was disappointing for sure. It seems to happen each time a new type of weapon is fired, this is a common issue with Unreal Engine games (Storm United and Borderlands 2 both suffer from it). I really do hope Feral manage to nail this issue down, as it's quite concerning as you miss a fair bit of action. I won't spoil it (yet), but there's an incident with a grenade, and it became a three part slideshow.
An issue that the Linux version seems to share with Windows is how long it takes for each turn to start, sometimes there are random pauses before anything happens, as if the game is loading and trying to catch up with itself. I've seen it happen for other reviews videos, so it's not a Linux issue. The game just doesn't seem to be optimised.
Another issue (which is a game issue, and not Linux related) is the camera, and how terrible it is at times, here's a perfect example:
Do you know what's going on? I don't. I mean I know someone died, but I didn't see shit. They really need auto rotation. They needed it in XCOM, and they need it here too.
There is a bit of stutter when you're scrolling around, it's not too bad, but hopefully something that can be worked on.
When you get back to your base, the performance goes down even more. I was getting 30FPS and below while viewing my base.
1920x1080
I decided to tone it down to 1920x1080 resolution to see what the difference was. There was zero difference on the base view, with it still struggling to hit 30FPS on High.
During a mission the FPS at this resolution was a bit more acceptable between 40-70, but it does dip right down to 40 quite often. It's a little more acceptable, but still quite bad.
I would definitely turn off the action camera, it's distracting and slows things down even more. This is also true on Windows, and I hated it in the first XCOM too.
I turned the game down even further to Medium settings, but still keeping it at 1920x1080 (I refuse to game at lower than that on a 980ti). It's now properly acceptable hovering between 70-90+ FPS. If the AA options weren't so terrible, it would be slightly more enjoyable on Medium.
I failed the first proper mission (the one after the tutorial) twice, so it's exactly what I expected. It's good to be back, it's damn good, but wow is the difficulty higher.
Once you have played it for a while, if you quit the game entirely to the desktop and then re-load it, the stuttering is somewhat improved. This is usually down to cache issues (reloading it with stuff already loaded and ready), but I honestly don't care what's causing it and why it can't be done before the actual gameplay. The problem is, it just should be done before you play it as it gives a terrible impression.
If you do come across this issue below, load a saved game from before you entered the mission and it fixed it for me.
There's also the issue of the colour of the game, compare these images to the image at the top of the article. The shadows here are purple and surfaces are bright blue. Feral are aware and say it happens on Windows too, but they are waiting to hear from Firaxis if it's intentional or not. I really don't think it is (as it looks terrible and it's a completely different colour palette), but I will wait and see.
The game also seems to pause when it doesn't have focus, which can be annoying at times.
Ending thoughts: Performance really is a let down, as is the missing MSAA option. The time it takes parts of the turns to complete is frustratingly slow, as you wait for the game to realize something has happened. I will take another proper look at it after some patches, and when I have put more time into it. Honestly, for the moment I really would hold off and wait for some performance patches.
The actual gameplay is good though, the performance is just all over the place.
About the game (Official)
Earth has changed. Twenty years have passed since world leaders offered an unconditional surrender to alien forces. XCOM, the planet’s last line of defense, was left decimated and scattered. Now, in XCOM 2, the aliens rule Earth, building shining cities that promise a brilliant future for humanity on the surface, while concealing a sinister agenda and eliminating all who dissent from their new order.
Only those who live at the edges of the world have a margin of freedom. Here, a force gathers once again to stand up for humanity. Always on the run, and facing impossible odds, the remnant XCOM forces must find a way to ignite a global resistance, and eliminate the alien threat once and for all.
The game can also be purchased with a Steam Controller (with 40% off!) as it has native integration, so hopefully when the performance is sorted I can sit back on my sofa and relax with my Steam Machine.
You can find XCOM 2 on Humble Store and Steam.
Article taken from GamingOnLinux.com.
Quoting: LukeNukemSounds like it's the old OpenGL issue of only compiling shaders when they get used (hence bombing framerates for new weapons)
Compiling, Linking and Loading shaders to the GPU are all active programmer choices ( i.e. you actively make OpenGL API calls ), so they can be completed ahead of time if you manage your own shaders.
If you use an engine, the same can probably be achieved by rendering every item type once to force the shaders to be compiled and activated. This would obviously look naff unless you can render the geometry with full transparency, or turn off frambuffer updates.
Any idea?
Polochamps Feb 5, 2016
rustybroomhandle Feb 5, 2016
Quoting: zebI have a serious rendering bug (and contacted Feral about it) which makes it unusable.
...
Any idea?
Oh I know what's happening here. You are running it on a ZX Spectrum. :D
Quoting: Polochamps^
That's nasty. Did you also try to contact 2k? - http://support.2k.com
Not yet, I will wait for Feral answer first, after all they are the Linux specialists.
Quoting: rustybroomhandleOh I know what's happening here. You are running it on a ZX Spectrum. :D
That explains all!The strange thing is that I read some comments that it was working on Arch using the same drivers (361.18), so I do not know what is going on there.
Last edited by zeb on 5 February 2016 at 12:38 pm UTC
Quoting: tuubiQuoting: PolochampsYes I did. Still if the game does not perform well on any combination of hardware or software, there's no reason to blame anyone but the developer. If you feel the need to blame someone that is.Quoting: tuubiQuoting: PolochampsBut in this case, if you look at the graphical demands of the game and the performance output on the higher end cards, one may think otherwise that this isn't just about bugs but driver issue as well.Blaming drivers for performance problems across operating systems and graphics hardware vendors is disingenuous at best.
You read the article?
From a developer viewpoint GPU drivers are black boxes, and the Unreal Engine is another black box that uses the first black box. In such circumstances, trying to force the black boxes into the optimal behaviour is quite difficult, particularly given the variety of hardware in use, which leads to different issues on different configurations.
That's not to say developers have no responsibility, and couldn't do more before release. At the very least, ironing bugs out through an opt-in private beta program of pre-order customers would seem a sensible step.
This game is just poorly optimized even on windows as you can see. Don't blame feral for this.
The base scenes? There's no other way to put it: they're herky-jerky. To the point it's almost disorienting. This herky-jerkiness WILL carry over into the missions, making the game a teetotal headache to play.
BUT, quitting the game, firing it up again, then loading directly into the mission does always fix the issue. The framerate isn't exactly what I'd call silky super awesome greasy smooth (glxosd is floating around 30 FPS with most everything set as high as it'll go, barring a few features here and there I've been experimenting with), but it's perfectly playable.
Now I've spent about 5-10 minutes in the Windows rev , and while the framerate isn't TOO much better (haven't Fraps'ed it yet), that herky-jerkiness is nowhere to be seen. On top of that, there's a subtle red glow on top of everything in the Linux rev I initially took for granted that isn't anywhere to be seen in Windows. It's kinda hard to see, but here are a couple of screenshots showing what I'm talking about...
Base
Second Mission
It's real subtle, but pay attention to the landing gears in the first shot, and the edge of the fog of war in the 2nd. It's like a shader or some other graphical effect isn't firing off quite right.
Alright, I'm gonna hop back over to Windows and start taking some more screenshots.
I should also add that this is the first game I've played in Linux that's actually given me any trouble...
...besides XCOM 1. Oooohh...
Last edited by Renzatic Gear on 5 February 2016 at 5:00 pm UTC
Patreon
PayPal
See more from me