X

Serious Sam 3: BFE Screenshots and Images - Xbox 360

Serious Sam 3: BFE
  • Publisher: Devolver Digital
  • Genre:
  • Developer: Croteam
  • Release Date:Nov 22, 2011
  • # of Players:1 player
  • ESRB:M - Mature (Strong Language, Blood and Gore, Partial Nudity, Drug Reference, Intense Violence)
  • Platforms:
Game Description: Serious Sam 3: BFE for the PC is a prequel to the original Serious Sam game. This first-person shooter will feature 16-player online co-op, so get ready to get trigger happy with friends.
G4TV Rating
4 / 5
  • Avg User Rating
    (3 Ratings)
    3.7 / 5
  • Rate This Game

Serious Sam 3: BFE Screenshot & Image Galleries

  • Serious Sam 3: BFE "Fork Parker" Trailer

    Posted: November 28, 2011

    7,314 Views | 01:55

  • Serious Sam 3: BFE "Blood And Guts"

    Posted: November 17, 2011

    6,241 Views | 00:56

  • Serious Sam 3: BFE "Melee Attacks" Trailer

    Posted: November 8, 2011

    1,033 Views | 01:11

  • Serious Sam 3: BFE "Helpline" Episode 2 Video

    Posted: September 12, 2011

    744 Views | 01:13

  • Serious Sam 3: BFE "Serious Chaos" Gameplay Trailer

    Posted: August 23, 2011

    1,513 Views | 01:21

 


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>