X

Star Wars Rogue Squadron III: Rebel Strike Latest News - GC

  • Publisher: LucasArts
  • Genre:Action, Adventure, Shooter
  • Developer: Factor 5
  • Release Date:Oct 21, 2003
  • # of Players:2 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:The highly anticipated third installment of the Rogue Squadron franchise lands exclusively on GameCube's flight deck! You must learn to pilot a variety of vehicles - including X-Wings, the Millennium Falcon, Imperial Speeders, AT-ST's and more - in order to defeat Darth Vader and his Imperial Forces. In a new twist, you will also climb out of the cockpit and fight on foot as Luke Skywalker or Wedge Antilles. Beautiful, detailed environments like the forests of Endor, frozen Hoth and Bespin's Cloud City all come alive with plenty of real footage from the epic Trilogy. Many multi-player modes and unlockables are included, and all of Rogue Squadron II: Rogue Leader is built in for co-op play.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Star Wars Rogue Squadron III: Rebel Strike News

Displaying 1–1 of 1 articles

  • Mark Hamill Was Never Asked To Voice A Star Wars Video Game

    You'd think it'd be natural for LucasArts to ask Mark Hamill, aka Luke Skywalker, to be part of one of the many Star Wars video games that have been produced over the years. PC Zone recently spoke with the former member of the Force, however, and said it's never happened. Post-Star Wars, Hamill has made a name for himself as a prominent voice...

    Posted January 5, 2010

    Mark Hamill Was Never Asked To Voice A Star Wars Video Game
  • X-List: Top 5 Games We Want in 3D

    Posted: April 5, 2011

    18,440 Views | 01:07

 


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>