Battlefield 3 At TGS, What a Difference a Month Makes

The last time I played Battlefield 3 on the PS3, it had some problems. But that was the game’s co-op mode! The game’s singleplayer code is looking a lot healthier. https://kotaku.com/a-tale-of-two-games-of-battlefield-3-5832819 The demo available at the Tokyo Game Show is a level we haven’t played before, a singleplayer mission that involves storming an apartment building at night. The structure of the mission is pretty simple: rummy 365 run down a hill, set up a mortar (sadly, you can’t control it), shoot everyone outside the building then shoot everyone inside the building.(new Image()).src = 'https://capi.connatix.com/tr/si?token=995c4c7d-194f-4077-b0a0-7ad466eb737c&cid=872d12ce-453b-4870-845f-955919887e1b'; cnx.cmd.push(function() { cnx({ playerId: "995c4c7d-194f-4077-b0a0-7ad466eb737c" }).render("79703296e5134c75a2db6e1b64762017"); }); Nearly all the issues the PS3’s co-op mode was suffering from at Gamescom, like poor frame rate and major glitches, were absent here, the mission chugging along nicely despite a ton of effects going off and enemies appearing – and dying – where they should instead of flickering in and out of existence. If you’re expecting this to look like the PC version, or even close to it, you’ll be disappointed. It’s clear the console versions won’t come near the kind of fidelity the PC in 2011 is capable of. But that’s OK, and totally understandable: the PS3 is, after all, 2006 hardware. What I liked about this mission’s visuals, then, is the decision deveopers DICE took with what they were going to compromise. The PS3 version is jaggy, noticably and unavoidably so, but what it loses in clarity it makes up for with the full range of effects. All the smoke, fire and clouds of dirt that rummy 51 bring the game world to life were there and looking great, and at the end of the day if things have to rummy best compromised then that’s the way I’d like it to shake down. Better a jaggy and exploding world than a clear and sterile one! You can contact Luke Plunkett, the author of this post, at [email protected]. You can also find him on Twitter, Facebook, and lurking around our #tips page.