X

Resident Evil Outbreak: File #2 Videos and Trailers - PS2

  • Publisher: Capcom
  • Genre:Action, Adventure
  • Developer:
  • Release Date:Apr 27, 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:Resident Evil Outbreak File #2 takes us back to the dangerous and infested Raccoon City. Last time a deadly outbreak plagued the land and the people of Raccoon City. Started by a secret biological weapon, the outbreak has turned the people of Raccoon City into man-eating zombies! There's nothing left to do but escape with your life before you become lunch or the government destroys Raccoon City to prevent the outbreak from spreading. It's all the chills and thrills that Resident Evil fans have grown to know and love, with new graphics, a more high-paced storyline, and dynamic gameplay that will have you sweating with joy.
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

Resident Evil Outbreak: File #2 Videos

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