FSX and the computers of today some thoughts

[Wayne Pierce]

My fellow Pilots;
This is a forum post on the ORBX forum which only a registered user can access, but it addresses a problem in which many of us FSX users have. It really puts any problems we have with FSX and todays' use of FSX in perspective.

Here is a link to the post, but you need to be a logged in member to view, for those whom can read the entire message.
http://www.orbxsystems.com/forum/topic/ ... ll-errors/

If you don't have any FTX scenery packages then it still is a good read as to cause and effect for FSX problems.

I subscribe to the theory below about why FSX give us many problems and have personally done a lot on my system to reduce them. My system works well now with very few problems and gives good results.
I get very good frame rates with the advanced scenery and payware aircraft load over much of the FSX world.

I very seldom, if at all now get CTD's, only those which are FSX aircraft built in CTD's. Incomplete design on them.

My scenery is where I would like to see it as a virtual world.

Not all below is applicable to everybody, some solutions are only if you have the FTX scenery.


From ORBX CEO;
(edited by me)

"Consider this scenario:

You are flying over Orbx PNW, enjoying your flight - when you begin to see large black squares appearing on the terrain, and blurred ground textures. Then some stuttering and a loss of frames. You continue your flight, and the black textures disappear, but re-appear in different places. After 25 minutes of this - BANG! FSX exits suddenly to the desktop and you may even see a dialog box with a "g3d.ll error" or other similar message.

Frustrating stuff! We feel your annoyance, pain and plain anger at how this spoils FSX for you.


WHAT CAUSES THIS?

Way back in 2006 and even 12-18 months ago, CTDs were rare, if they happened at all. But something has changed over the past year and a half and we have noticed an escalation in reports from FS users all over the world, and for many different sceneries, airport, aircraft and other FS addons from many vendors. So the question is - what has changed, and why is this an issue for some users?

We don't profess to know the answer to the above, but we can offer some theories and of course, some solutions below. Firstly, let's wind back to 2007/9 when Orbx released FTX for Australia and then PNW etc. People's hardware and environments were predominately dual-core, Windows XP or Vista, and machines had modest RAM and hard drives. We also did not get any reports of CTDs, g3d.dll errors or a lot of crashes. Remember, FTX's architecture has not fundamentally changed since its first release, but it was commonly recognised (and we never shied away from) that FTX did place a lot more burden on people's hardware simply from the perspective of our much higher density of autogen and also the 3D lighting system.

Fast forward to 2010/11 and we begin to see the emergence of these CTDs. What has changed since 2006/7? Let me present a list of things which have changed for most FS enthusiasts:

- Faster hardware - CPU/GPU/HDD/SSD/RAM

- Increasingly sophisticated FS addons - complex aircraft, environment textures, HD textures, shader mods, moving cameras, higher resolution scenery imagery, 3rd party tools, DLL plugins and even aircraft with completely custom DLL-based physics and cockpit systems

- Two new Microsoft operating system releases - Vista and Windows 7 - and their countless patches and some service packs

- New Windows tuning tools, anti-virus tools, optimizer, defraggers, GUI enhancements, and countless other apps

- "Bloatware" PCs being shipped - that is, vendors like HP, Dell etc pre-installing whole suites of apps which 99% of customers don't use or are unaware of being installed, both passive and active, including Windows services

- The emergence of many "tweaks" for FSX which have only begun to become popular in the last 18 months

Think about this: after three years of coding the engine and countless hours of testing and beta reports, there's a reason ACES locked LOD to 4.5 and textures to 1024 - because the engine clearly showed signs of stress when pushed beyond those vital horizon and texture limits. FSX is not Skyrim where modders can throw 4096 textures, countless mods and upsized files at it; Skyrim's horizon rarely goes beyond 5 miles at best. (Its whole *world* is smaller in square miles than some Orbx airport photoreal areas). FSX is one of the most sophisticated far-distance 3D engines ever made, with a horizon of 70+ miles; but you need to respect that and not push it to do things even the ACES engineers knew would break it.


So now consider that since FSX SP2/Acceleration, there has been zero code changes to the FSX engine, but we now have significant amounts of horsepower pushing that engine, under new operating systems and in many cases with multiple tweaks applied and multiple layers of FS addons - all of which are vying for a slice of the FSX engine which is single-threaded and completely not designed for the layers sitting on top of it today. You have immense CPU power pushing a single-threaded engine at higher and higher clock speeds. Yes, there are benefits, but also stresses induced.

The issue is this: the FSX engine is under more stress than it even has been since it was released. It is being asked to drive higher resolutions at faster refresh rates and with multiple layers of increasingly complex addons, higher resolution textures and DLLs which it frankly, it's struggling to cope with. Today's FS users are hammering FSX very hard, in a nutshell.

So FSX is beginning to protest under this burden, and we see these CTDs manifesting as a result.



SOME SOLUTIONS

Orbx has always listened to our customers. Your feedback, bug reports and (constructive, consultative) critique is what makes our products better. We have recognised that CTDs do happen, and we have spent considerable time, money and research on trying to minimise them. We have released new libraries and recently a patch to our 3D lighting system to take stress off the FSX engine. All the while, we are continuing to implement more rigorous testing of our new products to ensure that less missing GUIDs and other possible causes of stress are no longer a factor in our addons.

This does not mean we accept that Orbx FTX addons are the cause of CTDs, but we do and have publically admitted that there were holes in our products which may have added to the stress being added to the FSX engine. So our ongoing mission is to continue to plug those holes, and we expect other vendors to be doing the same, and learning from their customer reports and feedback as well. We are never too proud or arrogant to assume our products are perfect and bug-free - but at the same time we have from day one continually offered free service packs and patches and continual improvements and new features to our entire product line.

So let me offer some possible solutions to these CTDs, which may or may not eliminate them for you, but in our team's opinion they will go a long way to reducing their occurance.


1. FSUIPC New beta 47.49d - Pete Dowson is an FS legend and was developing stuff long before Orbx was born. So when he speaks, we listen. When he tells us he's fixed something, we should all listen. In this instance a new beta build of his FSUIPC DLL seems to have been sucessful in trapping many CTDs and early reports suggest a much more stable FSX environment under stress loads. We highly recommend Pete's module!

A. If you don't have FSUIPC yet, download the full installer from Pete Dowson's web site.

B. Once you have done the setup or if you already have FSUIPC, download the new beta 47.49d - http://fsuipc.simfli...FSUIPC4749d.zip

Unzip the file and move the enclosed FSUIPC4.dll file to your fsx/modules folder and you are done. There is an ongoing discussion with Peter over at AVSIM about his current beta builds if you want to keep tabs on his debugging efforts - http://forum.avsim.n...ost__p__2175043

If you want to show your appreciation, you can purchase the full registered version.

(some lines deleted here by WLP)

4. Less tweaks to fsx.CFG

This is subjective, so take it as it comes - my personal opinion, and how I use FSX. Simply put, I use a vanilla fsx.CFG and don't add any tweaks at all, other than some simple lines to remove the annoying red texts that appear on-screen. I have used this approach since 2006 and I'll be honest with you - I have never encountered CTDs/g3d.dll errors - ever. This is likely due to keeping my FSX installation as vanilla as possible, not adding complex layers of DLLs and other addons, and also ensure my Windows environment is bloatware-free. So take that advice or leave it - it's not a religious argument, just my recommendation."


If you have read this far, I have reduced what I can on my computer and "tweaked" the FSX.CFG with a bare minimum of items.

Thanks.