Not the problem:

 

An i7-975 cpu running W7 64 bit Ultimate with 12 GB's 1600 MHz system RAM, pushing it out to an EVGA GTX680 Signature GPU.

 

The problem:

 

This is running an antiquated 32 bit internal code program that has not seen any refreshes or updates other than what we are all aware of.

 

We all know that we live inside a 4 GB VAS envelope...and that's that, as they say.

----------------------------------------------------------------------------------------------

 

If you run in DX10 Preview, you only pick up a 300 MB buffer, as there are no double texture lists as happens controlled by DX9 when running. Some run with DX10 for this reason, whether they knew this or not.

 

After a full continuous 5 hours of flying around ORBX's Pacific Northwest with a custom plane, and also Shade, A.I. Smooth, and OPUS weather, with also ACCU-SIM, and COUTL, etc...I experienced with the following settings, no CTD's. No O.O.M.'s no .dll or AppCrash. Nothing but seemless 30 locked FPS and smoothness.  I had to dumb down a couple of settings, and had a fabulous uninterrupted flight.

 

Settings that will cause no O.O.M with a high end system:

LOD 5.5

Max Textures 2048

 

Hardware wise, I had previously always flown FSX with 4096 texture settings and those textures installed. Airplane, and scenery.  I also flew with a LOD of 6.5   This simply even on my take-no-prisoners system is, with this old 32 bit software, unsustainable. You will run until you CTD with an O.O.M. and a long enough time in the air to cause one!!!

 

So, I now no longer look ten miles out from my present position, and frown that the mountains are not as sharp as glass shards as scenery around me 2 miles out to view. The mountains and terrain are with LOD 5.5 in 'soft focus' until I get my a** there!  I can live with that. I also can now live with REX Extreme clouds rendered at 2048 rather than 4096. They don't look as fluffy life-like,but they CERTAINLY don't look bad either!  By just dropping those two that I mentioned, one down a notch, and the other by half....FSX will run til the cows come home. 

 

I played around for the best part of the day Friday with DX10, but with so many compromises, and 'this works, but that doesn't'...I decided to come back to to DX 9 that looks great, works smooth as silk, and now will run until I decide to 'drop to desktop'...lol.  I just had to back off what I mentioned, and not drastically so.  So, if your're still with me on this sentence, try it yourself. Keep everything as you like it. Load up the sim with what you normally do...but just do not go above 2048 for atmospherics and land textures, and finally back off the LOD to 5.5 or keep it at the stock 4.5   You will be fine...and fly until the coffee thermos is finished...(wink!)   Bottom line, with my forementioned system specs and the rest of this post....I have ended 32 bit FSX crash-what-ever's.

 

I have made a decision, with the coming release of Xplane 10:22 and its 64 bit .exe,  I will buy that, and enjoy on my 64 bit enabled CPU and O.S.  I will also buy hand's down, the 'other' FSX variant, when (and if ever) it supports DX11 and they translate it to 64 bit, also when, and if ever. With that in place, will it be a no-brainer to migrate to it. Until then?....no problem running 32 bit, 4GB VAS-restricted, FSX with the above mentioned in place. It still puts out the beauty and grace of flight.

 

Ses 

At the end of the day, FSX is still just a 32-bit program.  A 64-bit version would have been great and would have allowed FSX to utilize more than 4 GB of memory.

I have default LOD and textures limited to 2048 in fsx.cfg, and i didn't get OOM's and CTD's more then 1 Year  

That may be true... 

With "CTD's", does that mean it (might) solve the freaking "A fatal error occurred." nonsense as well?

With "CTD's", does that mean it (might) solve the freaking "A fatal error occurred." nonsense as well?

 

That error can be OOM related, but it's better to check the reason. I recommend you to use this tool: http://www.nirsoft.net/utils/app_crash_view.html  

 

It will tell you "fault module name" for example, or what error is. And if we know the reason - we can fix it

Apparently (if I'm reading it right), g3d.dll is the faulty module. It's been in the report of the last 4 crashes. The one before that is caused by "StackHash_c2c0", then "StackHash_fc24", and then the next 6 errors are g3d.dll again..

If you are having CTD's, please post in the CTD forum.  In the CTD forum there are suggestions for fixing the g3d, StackHash, API, and OOM crashes.  They have worked for many.  Any CTD reports I'll have to split off from here and move the topic to the CTD Forum.

 

Thanks!

 

Jim Young

AVSIM Moderator

Understood! Thanks for moderating this thread; I'd hate to have derailed it.

Some scenarious are very precarious, even with reasonable settings. My machine is an i7 2600k, 8 GB of RAM, a GTX 580, and Windows 7 64 bit. I run LOD radius at 4.5, scenery density maxed, autogen at normal, and water at 1.x high. With the FSLabs Concorde X, even with these settings and no traffic, I can get OOM errors if I fly from UK2000 Heathrow to FSDT's KJFK with UT2 traffic disabled. With the PMDG NGX, I can get OOM errors flying from Flightbeam's KPHX to FSDT's KLAX if I run UT2 traffic around 60% with ProAtcX. LOD radius is very important, but the total usage of addons used, and how demanding they are for VAS is very important in limiting OOM errors.

 

Sent from my GT-N8013 using Tapatalk HD