X

Warhammer 40,000: Dawn of War -- Dark Crusade Videos and Trailers - PC

Warhammer 40,000: Dawn of War -- Dark Crusade
  • Publisher: THQ
  • Genre:Strategy
  • Developer: Relic
  • Release Date:Oct 9, 2006
  • # of Players:1 player
  • ESRB:M - Mature (Blood and Gore, Violence)
  • Platforms:
Game Description:The second expansion to Dawn of War includes all-new, explosive Dawn of War single-player action play, new multiplayer content, and two new playable races including the technologically devastating Tau. In addition to the two new playable races, Dark Crusade will feature an all-new single player campaign centering on the conquest of a "meta-map," with each territory captured giving tangible rewards to the occupying force. Also featured is a greatly expanded multiplayer component and a completely unique economy model for the Necrons. Warhammer 40K: Dark Crusade is also a stand-alone expansion -- it adds bonus content to Dawn of War and Winter Assault, but it can also be played on its own without needing a copy of the original game.
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    3 / 5
  • Rate This Game

Warhammer 40,000: Dawn of War -- Dark Crusade Videos

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