Thursday, November 15, 2012

Mechwarrior Online - Yet another update

So MWO is out in open beta now. I've commented about it several times, and have raised many concerns as to its future. Unfortunately, I was right. Very right.

It's a F2P game that is very shallow in nature, repetitive in its grind, and completely unsuitable for release in its current stage. Netcode sucks, performance sucks, the awful motion blur, film grain, HDR, and bloom are obnoxious, content is lacking, game mode is boring, mech prices are WAY too expensive, matchmaking is nonexistent, the grind is painful even for the cheapest mech, and they still pushed it out the door into open beta anyway. The developers knew too, but they had deadlines to meet, which is a shame. They settled on releasing a minimum viable product (their words), and thus, I do not understand how they expect to receive anything more than a minimum viable score. What a terrible business plan.

They cited a bunch of other similar F2P games (namely World of Tanks) to justify their pricing and launch quality, but like I said before... F2P isn't a cureall, and a game released years ago shouldn't be used as the measuring stick for today.

Sadly, I really wanted to be wrong on this one, and for MWO to succeed. But I don't think it will. The biggest chance for MWO to get noticed was at launch, and they blew their chance. Even if they do fix up the game, it'll be too late, as Mechwarrior has always been a small community without the same level of magnetism. Even though it has only been the first 2 weeks of launch, the numbers are disheartening. The devs, PGI, have smartly pulled out the online players counter that was present in every iteration of beta. Worse, they're using a terrible engine (CryEngine 3) which suffers from persistent netcode problems and poor handling of fast moving vehicles (CryEngine 1+2 also had this problem, so MWLL was affected). Its engine also has shockingly poor performance despite being tailored to adhere to console specifications.

Well, I tried my best back in beta to warn the devs of this problem. I even spoke to them personally. They did stall beta few times to increase it's standard of quality, but this isn't enough. At least I enjoyed my time in the beta with it. You know, back when these flaws were 'acceptable'.

"It's just a beta, it'll be fixed on release." Yea, right.

No comments: