Broken games aren’t anything new, although it does seem that we have had a glut of them in recent months. Assassin’s Creed Unity looks set to join the post-development woe befalling Halo’s Master Chief Collection and DriveClub. But has it always been this way for games to be released with problems?
In a word, yes. Sadly the game medium and the ease publishing downloadable updates to consoles have seen game publishers rigidly stick to their release dates in order to fill their quarterly reports, at the expense of bad press and consumer dissatisfaction. It feels all too apparent in recent times though. Here are a few reminders of the last 12-18 months of game release failures. [divider]
Those who recall the long wait for a £60 pound persistent online game only to find that they were only persistently trying to connect to EA’s servers will lament this well. It was made even worse for Mac users who had to not only wait an age for their release but for the problems to be solved as well. Was the game broken? Well there were parts of it that were, and certainly still are. A new engine and new AI was being patched quite a lot in the end to stop itself from doing silly things but for the most part (apart from the always online design flaw and small development areas) the game was fine. But the release of the game turned into a complete farce for EA.
Given that the game was “always online” and there was no offline mode, it was the lack of servers that surprisingly foiled EA’s release. The back end infrastructure they had in place couldn’t handle the amount of people who were wanting to play, nor the data it was supposed to store, leading to a long process of issues, apologies and modifications. EA had to give away a free game, Maxis had a tail between their legs and had to release certain things for free that would have made good DLC and they had to implement an offline mode after the mod community showed how easy it was to implement. Never one to be bested by such setbacks, EA did exactly the same thing six months later…
The release of Battlefield 4 actually started a lawsuit against people who appeared to be raising the game’s praise to shareholders erroneously in order to generate satisfactory financial reports. But us gamers don’t care about all that suit nonsense, we care that once again, EA’s servers were not up to the task of online play. Bugs galore as people could run around with no health and kill you, the promise of big destructible landscapes and buildings were hard to find, lots of graphical glitches and all this was only an issue if you could even connect to a server in the first place to play the game.
Personally, I found Battlefield 4 quite uninspiring as a single player game although I enjoyed the online play as by the time I’d got to it, the multitude of patches and fixes had been implemented and the multiplayer game was playable. But around its launch, very public and very damning issues beset it. Exactly who is to blame here is tricky as there seems to be quite the administrative level fallout over this, but EA once again were at the centre of the storm and directly addressing it calling the situation “unacceptable”. Two bad online releases in a year is obviously the button pusher in the EA head offices. Speaking of fallout…
Fallout: New Vegas
Ok, so this game goes further than the 18 months but still, it’s worth putting in here. This game was bugged from release. I know this, which is why it’s on my gaming rack still in its cellophane wrapping. As gamers, we tend to forgive Bethesda’s mistakes in game development because of all the things they get right in their games, but this game makes my little reminisce due to it being the most bugged of them all. Fallout 3 was not without its issues and PS3 Skyrim players will recall the game breaking memory issues and save deletions.
Fallout New Vegas also had the same issues and was prone to a multitude of crashes, textures not loading properly, framerate issues, characters running away, item and character clipping, characters heads doing strange things, incorrect gender character noises, to name but a few. There’s a big old list of all the bugs on the wikia page for the game and you could summise that this is why we’re waiting a long time for another Fallout game, or a proper Elder Scrolls successor. The engine definitely needs a lot of work to be up to the scrutiny of a new generation of consoles and maybe that’s why Bethesda are being quiet about it. But that hasn’t stopped them, oh no…
The Evil Within
Bethesda’s most recent release is a fine game. It looks excellent and has only the minimal of bugs, like the headless character bug pictured. It’s a survival horror treat that is worth the time and the day one patch. If you don’t have the day one patch however, the game is a completely different story. Digital Foundry did some snooping after a couple of reports of bad frame rates, but that was just the start of the horror. The out-of-the-box version of the game is a mess. The resolution of the game is a heavily upscaled resolution that is nowhere near the 1080p or 900p it’s supposed to be for the PS4 and Xbox One respectively and is stretched to fill the screen. It also suffers from massive framerate drops, the likes of which you’ve probably only seen on a heavily overworked Minecraft server.
The patch completely changes this to a playable game. But what gets me is that the developers had time to fix this for the release edition until the game’s release was brought forward a week (presumably to cash in before Alien Isolation came out). The patch, given how much it fixes, is a monumental effort by developer Tango Gameworks. It’s definitely worth checking out the videos that Digital Foundry put up as it really does highlight the issues the retail version of the game has. To release a game in that condition is simply just not cricket…
Ashes Cricket 2013
Yes these links are getting worse. But no worse than the only game in this piece that was actually removed from sale. It even made national news due to its failure. Ashes Cricket 2013 is probably the reason that you won’t see a cricket game for quite a long while. 505 apologised and issued refunds, Steam pulled the game from sale and the console versions didn’t even appear. Why? Because the AI was awful, the character models were missing key things (such as an animation for catching the ball) and the players ambled around in such a manner that Tecmo Bowl looked superior in playability.
Everything about this game was poor although the development was just as sketcky, moving to the Unity engine and then back again, being delayed twice and only released to try and cash in with its titular sporting series in Australia back in November 2013. All in all the story of this game is quite tragic really and just a cacophony of errors that will probably see Cricket languish in video game development hell, much like Rugby has for the most part in the past decade.
The thing is that all games release with bugs and as console gamers, we probably feel a bit precious about it given that we expect for our £50-60 outlay a satisfactory and, above all else, a ready product. And releasing games into a retail environment (that includes all the digital stores too) that are effectively broken or heavily bugged, just to make the demands of agreed times and publisher’s quarterly estimates, is quite abhorrent. That maybe a slightly cynical viewpoint though as PC gamers of all ages will know that games can be and are regularly patched to combat these problems. They always have been and they always will be. But the fact that we’ve had quite a few big name problems within the space of a week is quite damming.
Of course Microsoft have always had this date due to the nature of its anniversary package for Halo and the game in all honesty is intended to be a much needed unit shifter for the Xbox One. In fairness to them, the single player element of the game is fine there are just a lot of teething issues for quite a vast and probably the largest options of a multiplayer experience to date. Assassin’s Creed Unity is suffering from a number of graphical glitches in character models as well as world clipping issues. The game has already irked some due to its drop from 1080p to 900p in what is perceived to be cross platform parity. But the game has quite the demanding and technically difficult task of simultaneously processing 10,000 AI controller non-playable characters so that the experience of the crowd is more real and genuine. It’s no small matter given the processing power needed for that and what the consoles can achieve at present with how new the technology is for developers. DriveClub’s issues just seem to be poor choices that have been made at a management level to the game’s infrastructure and, if we’re honest, just a complete shambles from pre-launch to now, which is a shame for Evolution Studios.
While these bugs are certainly taking away from the game experience, and do invalidate our confidence in a publisher to develop a complete package for our hard earned electronic wealth numbers, do they constitute such a breach of trust between the consumer (us) and the developer/publisher (them) that we should be up in arms, or should we just back off a bit? After all this is all new ground for everyone, right?