Trine 2 Previews - Xbox 360

Trine 2
  • Publisher: Atlus
  • Genre:
  • Developer: Frozenbyte
  • Release Date:Aug 31, 2011
  • # of Players:1 player
  • ESRB:E10+ - Everyone 10+ (Animated Blood, Fantasy Violence)
  • Platforms:
Game Description: Atlus and Frozenbyte are collaborating on a sequel to their fantasy platformer, Trine. Trine 2 is scheduled to be released in 2011 via downloadable services.
G4TV Rating
  • Avg User Rating
  • Rate This Game

Trine 2 Previews

Displaying 1–1 of 1 previews

Sort by: Filter by:
All Categories
  • Preview

    Trine 2 Hands-On Preview -- A Gorgeous Return to Fantastical Form

    Trine was a wonderfully imaginative fantasy platformer with stunning visuals and satisfying gameplay, and Trine 2 looks to deliver a similarly high quality experience.

    Posted: Mar 21, 2011

  • Trine 2 Launch Trailer

    Posted: December 7, 2011

    496 Views | 01:40

  • The First 15: Trine 2

    Posted: March 21, 2011

    3,229 Views | 15:02

  • Trine 2 "Alluring Adventure" Gameplay Trailer

    Posted: March 21, 2011

    1,032 Views | 01:48

  • Trine 2 Teaser Trailer

    Posted: October 20, 2010

    789 Views | 01:01

  • E3 2010: Trine 2 E3 Trailer

    Posted: June 17, 2010

    4,195 Views | 01:38


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