FSX is prone to crash under Windows 8 — a lot of people reported that on the Internet, even though there are still many positive feedbacks about the combination. Frankly speaking, I was really a bit nervous about my bold decision of upgrading to the new OS. And I was prepared to encounter all sorts of unexpected FSX problems plus the notorious crash-to-desktop (CTD) issue.
To my surprise, in the first few days after FSX with Acceleration was installed under Windows 8.1 on my new computer, the simulator not only performed smoothly without the need of any tweaks but also ran sturdily. It didn’t crash at all, not even once during those days, UNTIL … Orbx’s FTX Global was added to the system. Then, FSX was prone to crash. The case was confirmed after I restored the FSX back to its initial stage via the Acronis True Image backup I earlier made.
Going back to Windows 7 was not my option since the problem wasn’t caused by the new OS in the first place. Also, FSX under Windows 7 is not CTD-free as well.
After days of trial and error, my FSX can now be played stable again — well, in relatively speaking.
So far I had all Orbx regions (NA, EU, AU, NZ), plus the FTX Global and the FS Global Ultimate meshes (the Americas and Asia and Oceania) installed. As long as I don’t switch locations frequently (probably not more than a couple of times) during a flight session, FSX can be run stably without crashing to desktop. I tried flying the C172 over Orbx’s NA and AU regions a few times for more than an hour without any problem.
Here are the tweaks:
Right click on the fsx.exe icon and modify its Compatibility setting as shown below:
Add the following entry to the content of the fsx.CFG file (C:\Users\<user>\AppData\Roaming\Microsoft\FSX):
Look for TEXTURE_BANDWIDTH_MULT= in the fsx.CFG file, and modify its value to
70 (or 80 or 90)
True, the current solution isn’t perfect, but at least I can run FSX in a sound and stable manner. Just avoid not to switch locations too often during a flight.
As always, your mileage may vary.