X

Dead Or Alive 3 Videos and Trailers - XBX

  • Publisher: Tecmo
  • Genre:Fighting
  • Developer: Team Ninja
  • Release Date:Aug 19, 2003
  • # of Players:4 players
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:Re-released as a Platinum Hits, the popular Dead Or Alive 3 returns to the fray. Though there are no new features, this re-release reminds fighting game fans to revisit all the action and brilliant designs of this now classic XBox title. Revisit Dead or Alive's 13 fighting styles, including Karate and Drunken Fist. This slugfest is set on 16 different multi-tiered fighting stages, with combat that allows reversals, countering, and combos. Movement takes place in full 3D. Characters taunt you with either English or Japanese voices. Ten different modes of play include two-on-two Tag-Battle mode. You can record and play back battles, changing viewing angles for cinematic effect. Unlock hidden characters, costumes and more.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Dead Or Alive 3 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>