Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yes, but 9 out of 10 of those issues are user errors or configiration problems.
As mikeytwc kindly said, this version was recompiled, namely using VC2013 versus VC2005 of the original.
For reasons beyond me, the game doesn't appear to install Visual C++ 13 Runtimes (it may be that I have Visual Studio amd that's why I didn't see it but every other Steam game usually tries) Needless to say, all VC++ Runtimes Redistributables are available from Microsoft's site. You should get 2005, 2008, 2010, and 13 (there may be a 2012 but don't quote me on that).
Also, some addons are currently incompatible.
Finally, don't try to run this game with with am Intel or AMD integrated graphics. Don't let the age of this game fool you, it will put a load on your computer. Especially with some scenery addons that will eat your RAM for breakfast.
Really? Thought they fixed the issues and this was no longer needed. Have run this for years in the standard version - solved a lot of problems. Have not had the CTD or other faults except for the "day the multiplayer died" which was apparently a Steam issue.
working fine for me (w8.1) - only one small niggle, the joystick disconnects if you alt tab and yuou have to restart the game to fix it.
Not sure what happended to the post but 'niggle' doesn't sound bad to me as long as you ennunciate well.
I have heard that folks try various things - unplug / replug in the controller; set the USB port properties to not allow the port to 'go to sleep' (the power settings for the individual port); run your controlls through FSUIPC (licensed version required) - maybe I have not had an issue with Win 8 becuase I have run my controls through FSUIPC for a long time now. Wouldn't go back to the FSX-directed control setup. Too many good things with FSUIPC. I have a Saitek yoke and had the phantom keystroke problem - solved with FSUIPC, and can use the Mode switch to change the function of the other buttons to multiply my functionality by three.