X

Grand Theft Auto: Vice City Stories Videos and Trailers - PS2

  • Publisher: Take Two
  • Genre:Action, Adventure
  • Developer: Rockstar Leeds
  • Release Date:Mar 6, 2007
  • # of Players:1 player
  • 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:Stories once told only on PSP now unfold on a bigger screen as GTA's Vice City Stories comes to PS2. You'll experience the same storyline, missions, music, and massive open world as you travel back to Vice City's beginnings. It's 1984 and the still-growing city is gripped by a violent power struggle for control of its lucrative drug trade. You're Vic Vance, former soldier and brother of GTA: Vice City main character Lance Vance. You've just been kicked out onto the young streets of Vice City. To protect those you love, you have no choice but to build an empire in this saga set before the events of GTA: Vice City.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Grand Theft Auto: Vice City Stories Videos

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