{"id":44329,"date":"2018-10-16T06:00:01","date_gmt":"2018-10-16T10:00:01","guid":{"rendered":"https:\/\/www.shamusyoung.com\/twentysidedtale\/?p=44329"},"modified":"2018-10-16T09:17:33","modified_gmt":"2018-10-16T13:17:33","slug":"andromeda-part-1-so-what-happened","status":"publish","type":"post","link":"https:\/\/www.shamusyoung.com\/twentysidedtale\/?p=44329","title":{"rendered":"Andromeda Part 1: So What Happened?"},"content":{"rendered":"

I’m sure most of you remember the novel-sized retrospective I did on the original Mass Effect trilogy<\/a> that ran from July 2015 to June 2016. At the end of the series<\/a> we were still looking forward to Mass Effect Andromeda and wondering how that would turn out. Since then the game has been released, received mixed<\/a> reviews<\/a>, became an industry-wide joke due to bugs and glitches<\/a>, was patched up by the developers, and then faded from public memory. It began as a hot mess and ended as a disappointing footnote in the history of BioWare. Now I’m finally getting around to playing it, over two years after my original Mass Effect series ended. <\/p>\n

Frustratingly, this game is neither as good nor as terrible as I’d hoped. This is not a return to the energetic worldbuilding of Mass Effect 1<\/em>, but neither is it an affront to reason like the final act of Mass Effect 3<\/em>At least, not the main story.<\/span>. There are a few good ideas here, mixed in with the bog-standard gameplay, open-world busywork, and cringy dialog. <\/p>\n

While Mass Effect 3 was at times frustrating<\/a> and irritating<\/a>, Andromeda<\/em>‘s great sin is that it’s merely disappointing. There’s not much to get worked up about here. Mass Effect 3<\/em> had the problem where its story unraveled right at the moment where it should have started wrapping up, and it was the conclusion to a story we’d been following for three games over the course of five years. This game tells a stand-alone story. The stakes were lower this time around, and so were our expectations. <\/p>\n

<\/p>\n

What Happened?<\/h3>\n

Some parts of this game can be quite interesting or striking. Those moments are sadly lost in a vast sea of stuff that doesn't quite work.<\/div>
Some parts of this game can be quite interesting or striking. Those moments are sadly lost in a vast sea of stuff that doesn't quite work.<\/div><\/p>\n

If you’re a longstanding fan of BioWare then one question probably hung in your mind as you played through Andromeda: What happened to this game?<\/i> Janky animations, un-BioWare gameplay, linear dialogs, Ubisoft-style open-world stuff, pervasive bugs, oddly scripted cutscenes, and a host of other problems all work to pull your mind away from the game and turn it towards thinking about its development. <\/p>\n

The previous games came from BioWare’s Edmonton studio, while this game was created by the new studio based in Montreal. I deliberately avoided looking at the credits during the writing of this seriesNot totally successful, mind you. Partway through writing this series I stumbled on a few names I recognized. Still, I did what I could to keep “the writer” as abstract as possible.<\/span>, so I didn’t know which (if any) writing staff or creative leads this game might share with the previous entries. As in my previous write-ups, we’re going to pretend that this story is the work of some singular unnamed writer. I find this makes it easier for the analysis to feel detached instead of coming off like an angry hit-piece. <\/p>\n

Obviously I don’t have any special insider knowledge about the development of this game. I’ve never met anyone from BioWare and I’ve never personally worked on a AAA game. I’m stuck on the outside looking in, just like everyone else. Most of the behind-the-scenes information I have comes from the Kotaku article The Story Behind Mass Effect: Andromeda’s Troubled Five-Year Development<\/a>. Sure, there are other sources<\/a> of information out there, but as far as I can tell they all lead back to the original research done by Kotaku.<\/p>\n

While I don’t have any insider information, I do feel like this series would be incomplete if I didn’t offer my own take on how things went wrong. As far as I can tell from reading articles and playing the game myself, the problems with Andromeda can be traced to three key decisions: Changing game engines, trying to make an open-world game, and ramping up the scope of a Mass Effect title to include much more content. All three of these are bad decisions, but they’re bad decisions that all exacerbate each other.<\/p>\n

The first bad decision is that they decided to…<\/p>\n

1. Switch to the Frostbite Engine<\/h3>\n

I know this looks like a good fit for the Frostbite Engine because we're trading gunfire with humanoids from behind cover, but Battlefield and Mass Effect are very different properties with different needs.<\/div>
I know this looks like a good fit for the Frostbite Engine because we're trading gunfire with humanoids from behind cover, but Battlefield and Mass Effect are very different properties with different needs.<\/div><\/p>\n

As the Kotaku article explains, the previous entries in the series used the Unreal engine. But for Andromeda, they switched to using EA’s in-house engine called Frostbite. <\/p>\n

The thing about changing engines is that it requires you to retrain your entire creative staff. If you’ve got three dozen people who are all experts in using Unreal Engine to pump out game content, then switching to a new engine will effectively turn them into a bunch of rookies. They may have to change tools, which is hard on both productivity and morale. If you’re fluent in one 3D modeling program and you’re forced to adopt another, then you’re going to spend weeks struggling with what used to be simple tasks. The team will certainly need to adopt a new workflow. Sure, your artists can get the basics down in a few weeks, but they probably won’t be fluent in the new tools until they’ve shipped a game with them. (This game came from a new studio, so it’s possible they hired Frostbite experts. Still, they no doubt began with a seed team from Edmonton or Austin.)<\/p>\n

The new engine will also oblige you to restart your entire asset library from scratch. Let’s say you’ve just spent the better part of a decade building up a vast collection of talking animations, ship models, weapon models, character models for several different species, models for “furniture”Computer consoles, crates, chairs, doors, and everything you use to fill in the environments.<\/span>,and modular interior room sectionsSounds and texture maps should translate just fine. It’s the 3D models that are a problem.<\/span>. If you were sticking with the same engine you could draw from that collection to fill in your gameworld, and maybe just touch up the oldest ones to make them appropriately “next gen”. Even if you end up remaking a lot of them over the course of development, it’s really nice to have the old content to serve as a placeholder during production or a fallback option if the schedule gets tight. But if you have to wipe the slate clean then you end up starting with a blank canvas. <\/p>\n

Worse, the team was switching to a less mature game engine with fewer features. The Unreal Engine is about twenty years old and is a generalized set of tools to support many different types of games. Frostbite is ten years old and is mostly focused on linear first-person shootersAlthough the FIFA and Need for Speed teams were able to adapt it to their needs.<\/span>. There are assumptions built into the engine that simply don’t allow for non-linear exploration-based content. You’re supposed to run through a level, shoot all the dudes, and then leave for the next level. The engine didn’t originally have allowances for the idea that the player might have a branching dialog with someone in zone ATalk to the quest giver on a space station.<\/span> that will cause changes to the content in zone BOnce you have the quest, the bad guys spawn at their designated location on the planet.<\/span> that can be reactive and persistentOnce I shoot the bad guys, they need to stay dead even if I fly to another planet.<\/span> and which can make further changes to the contents of zone AOnce the dudes are dead, I can come back to the quest giver for the reward and wrap-up conversation.<\/span>. All of that needed to be added.<\/p>\n

This engine switch is a heavy burden to place on a team. All by itself, it would make for a challenge. But on top of that the team decided to…<\/p>\n

2. Create a Procedural Open World<\/h3>\n

BAD: Make a procedural open world that's a boring desert planet. WORSE: Hand-craft a boring desert planet. MUCH WORSE: Make TWO desert planets.<\/div>
BAD: Make a procedural open world that's a boring desert planet. WORSE: Hand-craft a boring desert planet. MUCH WORSE: Make TWO desert planets.<\/div><\/p>\n

If not for the Kotaku article, I wouldn’t have believed this. You certainly can’t tell from playing the game. Apparently the team wanted to run with the idea of being a space pioneer and give you massive procedurally-made worlds to explore.<\/p>\n

While this does indeed sound like a great idea for a videogame, it sounds like a horrible idea for a Mass Effect game, a worse idea for a team dealing with sweeping changes to their development tools, and worse still for a game built using the Frostbite engine. <\/p>\n

Mass Effect is a game about telling science fiction stories using cutscenes and branching dialog trees. In a story-rich game like Mass Effect, the writer needs some control over the order in which you encounter content and the pacing of that delivery. I won’t say it’s impossible<\/i> to do that in the context of a procedural world, but it’s never been done before in the AAA world and there’s no obvious<\/i> way to reconcile these two vastly different ideas. <\/p>\n

This idea ran against the genre of the series and the new engine. It’s an idea that leaves a lot of question marks in the design and requires a lot of R&D to sort out. It’s not something you should be messing with when you’re also changing engines and<\/strong> trying to rebuild your entire content library and<\/strong> trying to break in a new team. <\/p>\n

This feature was obviously abandoned for a more traditional design, but it still ate up a lot of time and development resources. This is bad because they also decided to…<\/p>\n

3. Ramp up the Scope<\/h3>\n

It's not a great boss fight, but maybe you'll appreciate it once you're fighting it for the third or fourth time.<\/div>
It's not a great boss fight, but maybe you'll appreciate it once you're fighting it for the third or fourth time.<\/div><\/p>\n

This is a big game. There’s a lot of content here. Sure, a lot of it doesn’t fit together and none of it is polished, but someone on the team felt like Mass Effect needed to “go big”. Possibly different creative people had different ideas about what content the game should include and what it should be about, and rather than settle on a singular vision they just decided to take two and a half conflicting game designs and blend them all together. Or perhaps the creative leadership just had runaway ambitions. Either way, we wound up with this oversized, unfocused mess.<\/p>\n