While we found the Xbox One version of Batman: Arkham Knight to be quite impressive from a technical standpoint, PC players were in for a big surprise when they launched the game this morning. Indeed, it's hard not to be mad at Iron Galaxy, in charge of the PC port, and Warner Bros. for releasing the game in such a bad state. Framerate is all over the place even on a powerful rig (ours for example: i5 4670K @ 4.2 GHz, 8 Go RAM, Windows 8.1, SLI Nvidia Geforce GTX 970 Gigabyte OC) and it's oddly locked at 30 fps by default. Many people have also reported numerous crashes or momentary freezes, but we have been spared so far. The videos you'll find inside were captured from this morning's version of the game, before we edited the ini file to try to play at 60 fps. Since Steam is presently downloading the full game again, some of the problems might have been cause by preload issues. We'll let you know tonight, but for now, it looks a lot like the launch of Mortal Kombat X, another Warner Bros. fiasco on the PC scene.
Note: In the XB1/PC comparison video, there's a little bug with the scale of the graph but the plugin works perfectly and the numbers are good.
@Tiz: John finds out he's Dany's nephew after countless banging sessions. He finds out who his family is, but has sex with his aunt. I'd say that's a bittersweet way to end things (1 Hour ago)
@KORNdog: I'm hearing the word 'bittersweet' being used a lot in conjunction with the ending. Could be a union of all the Kingdoms facing the long night with casualties in the millions. (10 Hours ago)