Sniper: Ghost Warrior 2 Previews - PC

Sniper: Ghost Warrior 2
  • Publisher: City Interactive
  • Genre:
  • Developer: City Interactive
  • Release Date:Jan 15, 2013
  • # of Players:1 player
  • ESRB:M - Mature (Blood, Drug Reference, Intense Violence, Sexual Themes, Strong Language)
  • Platforms:
G4TV Rating
  • Avg User Rating
  • Rate This Game

Sniper: Ghost Warrior 2 Previews

Displaying 1–1 of 1 previews

Sort by: Filter by:
All Categories
  • Preview

    Sniper: Ghost Warrior 2 First Look Preview -- Snipe in the City

    Sniper Ghost Warrior 2 takes you back into the heat of the battle while making every shot count. Taking you out of the jungle and putting you into the city, look for places to hide while trying to take the perfect shot. Hold your breath and squeeze.

    Posted: Mar 22, 2012

  • Sniper: Ghost Warrior 2 "Brutal War Crimes - Bosnia" Trailer

    Posted: December 21, 2012

    6,285 Views | 02:10

  • Sniper: Ghost Warrior 2 "Urban Combat" Trailer

    Posted: May 29, 2012

    1,953 Views | 02:09

  • Sniper: Ghost Warrior 2 "Sarajevo" Gameplay Video

    Posted: March 22, 2012

    5,403 Views | 11:11

  • Sniper: Ghost Warrior 2 "CryEngine 3" Tech Demo Video

    Posted: March 21, 2012

    3,524 Views | 01:09


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

        <customErrors mode="Off"/>

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

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