X

Serious Sam HD: The Second Encounter Videos and Trailers - PC

Serious Sam HD: The Second Encounter
  • Publisher: Majesco
  • Genre:Shooter
  • Developer: Croteam
  • Release Date:Apr 28, 2010
  • # of Players:1 player
  • ESRB:M - Mature (Blood and Gore, Violence)
  • Platforms:
Game Description:Traveling through the crumbling Mayan ruins of South America, towering ziggurats of ancient Mesopotamia and the savage realm of medieval Europe, Second Encounter players will fend off never-ending waves of Lord Mental’s Army. These warriors include old friends like the Beheaded Kamikaze, Syrian Werebull and Kleer Skeleton, along with five new types of baddies and three new bosses for Sam to “play with.” Luckily, our hero has a HUGE arsenal of 14 ‘bring-the-pain’ weapons at his disposal, including three new toys: the Sniper Rifle, Flamethrower and Chainsaw. For those fans who don’t want to go at it alone, the game’s co-op mode lets up to four players ratchet up the mayhem across 12 maps that include a brand spanking new Deathmatch mode along with Cooperative, Capture the Flag and Survival. Featuring BIG guns, TONS of enemies, loads of achievements and more than 100 delightful secrets to discover, Serious Sam HD: The Second Encounter will remind players why they got into playing games in the first place: to blow stuff up.
G4TV Rating
N/A
  • Avg User Rating
    (2 Ratings)
    3 / 5
  • Rate This Game

Serious Sam HD: The Second Encounter Videos

Displaying 1–3 of 3 videos

 


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>