X

SOCOM: U.S. Navy Seals Fireteam Bravo 3 Screenshots and Images - PSP

Game Description:Hunt down an ex-KGB agent, and prevent him from realizing his diabolical plans to employ weapons of mass destruction in a series of devastating worldwide attacks. As a member of an elite team of U.S. Navy SEALs, players will fight alongside three AI or human teammates in co-op mode, relying heavily on team-based, tactical maneuvering to eliminate threats and prevent catastrophic events from unfolding.
G4TV Rating
4 / 5
  • Avg User Rating
    (2 Ratings)
    4 / 5
  • Rate This Game

SOCOM: U.S. Navy Seals Fireteam Bravo 3 Screenshot & Image Galleries

  • SOCOM: U.S. Navy SEALs Fireteam Bravo 3 Review

    Posted: February 24, 2010

    5,105 Views | 02:07

  • SOCOM: U.S. Navy Seals Fireteam Bravo 3 Iron Coffin Trailer

    Posted: November 25, 2009

    992 Views | 01:14

  • SOCOM: U.S. Navy Seals Fireteam Bravo 3 Gameplay

    Posted: November 16, 2009

    2,351 Views | 00:59

  • SOCOM: U.S. Navy Seals Fireteam Bravo 3 PSP Sizzle

    Posted: November 16, 2009

    537 Views | 00:39

  • SOCOM: U.S. Navy Seals Fireteam Bravo 3 Trailer

    Posted: June 3, 2009

    591 Views | 01:05

 


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 -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

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 -->

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