DICE was at Gamescom in Germany showing off an assortment of new Battlefield 3 details through their booth and a short keynote speech. The vast majority of the keynote consisted of the two speakers playing Battlefield 3 co-op on the console. Aside from the live co-op demo there was a trailer from a more classic Battlefield map inhabited with 64 players and fighter aircraft. Check it out below, preferably in high resolution and fullscreen. You can then check out the unofficial BF3Blog for the complete weapon list with claymores and mortar launchers.
So Call of Duty was leaving a bar and the pub server asked, “Gotta jet?”
It was also recently revealed that Battlefield 3 would be locked to 30 frames per second on the consoles which drew fire from Activision who runs their game at 60 FPS. Their claim was that the added framerate is required to have a more responsive experience. Unfortunately as our previous article reporting on Mozilla’s stance on responsiveness shows: it is not as simple as 33.3ms versus 16.7ms latencies. Even under the assumption that the framerate is at its maximum you cannot tell the exact duration between input and TV draw without the use of a high-speed camera looking at both player-controller and monitor. Many frames could go by without even looking at the input loop and all the other dependent code on parallel out-of-sync threads that finally alter the state of the threads that draws what you should see. Be careful what you read folks; while yes, higher framerate gives the higher potential for lower latency between press and draw it is not necessarily the case. All of that said we will be on the PC which has its own set of methodologies for how to handle multi-process (there are still latencies inherent with any multiprocess game, but with different limits) and thus this is entirely irrelevant to us, but still a good learning experience regardless.