X

Serious Sam II Videos and Trailers - XBX

  • Publisher: Take Two
  • Genre:Shooter
  • Developer: Croteam
  • Release Date:Oct 11, 2005
  • # of Players:4 players
  • ESRB:M - Mature (Titles rated "Mature (M)" may be suitable for ages 17 and older. They may include more intense violence or language than products rated "Teen" as well as mature sexual themes.)
  • Platforms:
Game Description:Square-jawed gunner, Serious Sam, returns with more intense, over-the-top action in this frantic sequel to the popular first-person shooter. Mow down 45 new enemies as you machine-gun your way through 40 levels in 7 environments, including jungles, tundra, swamps, and futuristic cities. Serious Sam II continues the original's knack for creating original enemy creatures that, while evil, pack laugh-out-loud wacky personalities. Powered by the custom Serious 2 engine, the graphics, environments, and physics are 100 times more intricate than those seen in the original. Climb the backs of rideable animals or hop aboard combat vehicles to wreak even more havoc. The explosive antics continue online.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Serious Sam II Videos

Displaying 1–1 of 1 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>