X

Star Wars: TIE Fighter Latest News - PC

Star Wars: TIE Fighter
Game Description:Space flight simulators began to boom in the late '80s and early '90s, but LucasArts arguably stole the crown with its 1994 space hit, TIE Fighter. A sequel to the well received X-Wing, this follow-up enlisted players into the galactic Empire and assigned them missions to help suppress the mutinous Rebel uprising. Playing the devil's advocate was -- and still is -- a brilliant spin on the Star Wars universe, and TIE Fighter's improved flight mechanics, combat, missions, and lengthy, involved storyline still rank it very highly among the best of the very best games ever created.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Star Wars: TIE Fighter 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
  • Top 100 Video Games of All Time #93 - Star Wars: TIE Fighter

    Posted: June 11, 2012

    10,604 Views | 02:04

 


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>