Total War: Rome 2 Previews - PC

Total War: Rome 2
  • Publisher:
  • Genre:
  • Developer:
  • Release Date:Dec 31, 2013
  • # of Players:1 player
  • ESRB:T - Teen (Alcohol Reference, Language, Suggestive Themes, Violence)
  • Platforms:
Game Description: Total War: Rome 2 will be the sequel to Rome: Total War, which was released in 2004.
G4TV Rating
  • Avg User Rating
  • Rate This Game

Total War: Rome 2 Previews

Displaying 1–2 of 2 previews

Sort by: Filter by:
All Categories
  • Video Preview

    Total War: Rome 2 Gamescom 2012 Preview

    G4tv talks with Lead Designer James Russell to find out how the team is improving Total War: Rome 2 to bring players a more realistic battle experience in war.

    Posted: Sep 4, 2012 | 11,257 Views | 02:47

  • Preview

    Total War: Rome 2 Gamescom 2012 Preview -- The End of Faceless Cannon Fodder

    Come for the large scale historical battles, stay to see how each individual soldier reacts as they stare down incoming enemy forces. This was the lesson we learned in our latest look at Total War: Rome 2 at Gamescom 2012.

    Posted: Aug 24, 2012

  • Total War: Rome 2 "Carthage" First Gameplay Trailer

    Posted: September 26, 2012

    4,135 Views | 00:59

  • Total War: Rome 2 Gamescom 2012 Preview

    Posted: September 4, 2012

    11,257 Views | 02:47

  • Total War: Rome 2 "Live Action" Announcement Trailer

    Posted: July 4, 2012

    4,114 Views | 02:46


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