X

ShellShock 2: Blood Trails Screenshots and Images - PC

ShellShock 2: Blood Trails
Game Description:War is hell, and the ShellShock franchise delivers gamers to the deepest circles of this hell with the series' second brutal and twisted psychological first person shooter experience. At the height of the Vietnam War, a covert ops cargo plane carrying a top-secret consignment known only as 'Whiteknight' is lost over the deepest, uncharted jungles. Special Ops soldiers are immediately dispatched to the scene to retrieve the top secret shipment and one-by-one they disappear without a trace ... until one month later, one of them suddenly walks out of the jungle. Crazed and deranged, something in the jungle had ripped out his humanity, poisoning his soul. Something in the darkness had driven him mad ... and followed him out. Taking the first-person war game and turning it on its head, Shellshock 2: Blood Trails places you in a war where fear takes on a whole new meaning.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game
  • ShellShock 2: Blood Trails Trailer

    Posted: September 30, 2008

    3,817 Views | 01:21 | 1 Comment

 


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>