Battlefield: Bad Company 2 Previews - PS3

Game Description: The boys of Bad Company are back in this brand-new title that will include another singleplayer campaign along with a revamped and upgraded multiplayer experience for more of a classic Battlefield online experience. The graphics engine has also been given a boost and the destructibility is better than ever.
G4TV Rating
4 / 5
  • Avg User Rating
    (30 Ratings)
    4.4 / 5
  • Rate This Game

Battlefield: Bad Company 2 Previews

Displaying 16–16 of 16 previews

Sort by: Filter by:
All Categories
  • Preview

    'Battlefield: Bad Company 2' Senior Producer Interview: Fully Destructible, Finally!

    'Battlefield: Bad Company 2' Interview

    Posted: May 22, 2009

  • Battlefield: Bad Company 2 Onslaught Mode DLC Launch Trailer

    Posted: June 22, 2010

    8,238 Views | 01:26

  • E3 2010 EA Press Conference: Battlefield Bad Company 2 DLC

    Posted: June 14, 2010

    10,048 Views | 01:26

  • E3 2010: BFBC 2 Vietnam E3 Announcement Trailer

    Posted: June 14, 2010

    3,669 Views | 00:51

  • Electronic Arts E3 2010 Press Conference

    Posted: June 14, 2010

    63,346 Views | 00:00

  • Battlefield: Bad Company 2 Map Pack 3 Trailer

    Posted: June 7, 2010

    4,540 Views | 02:03


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>