Unless you are actually using 4096 textures, that setting in the cfg file will do squat. But like I said, this is so subjective that it's not even worth debating over. Some people like to max out their settings, while others don't. If one is in the eye candy camp, 1.5gb will not cut it.

 

Sent from my Galaxy Nexus using Tapatalk 2

 

Hi Efrain I've actually considered getting a GTX680 but when it comes down to it I Just find it hard to justify...being in NZ I would spend over $1000 for it and I don't think it would help my OOM problem. I don't use 4096 textures as I'm quite happy with 1024 res and I've lowered my AA settings to just normal AA (i.e. no SGS). Also with the UsePools=0 tweak I'm not seeing any artifacting or other visual anomalies that would indicate the card being overstressed. Also wouldn't running out of VRAM usually result in a direct CTD? The error I got was the typical VAS error that goes something like "your computer has run out of available memory and will now close etc etc".

 

Thank you all for your understanding. Hopefully some scenery developers will start taking DX10 mode seriously as it's the only way I can see FSX moving forward at the high end with the extra VAS headroom it allows.

<br />Under dx9 it has plenty to do with it as the video ram that is needed (not all of it) gets mapped into the FSX.exe vas space.<br />

 

A 2 or 4gb card isn't going to help cure the 4gb VAS limit. My point was that running those addons in that already very hard area with the settings that he mentioned is what causes the OOM. It's a "glass ceiling" and a new videocard isn't going to fix it.

A 4GB GTX 680 doesn't help with OOM errors. I just got one flying around Orbx's Brisbane with the NGX..

A 2 or 4gb card isn't going to help cure the 4gb VAS limit. My point was that running those addons in that already very hard area with the settings that he mentioned is what causes the OOM. It's a "glass ceiling" and a new videocard isn't going to fix it.

 

He's right Folks, we are starting to move from people being Hardware (FPS) limited to now being software (X32bit app) limited, and at this point no amount of hardware or money is going to change that. I hope the OOM error's will make people move faster to XP10 then once that happens the Dev's will too!

Also wouldn't running out of VRAM usually result in a direct CTD? The error I got was the typical VAS error that goes something like "your computer has run out of available memory and will now close etc etc".

Thank you all for your understanding. Hopefully some scenery developers will start taking DX10 mode seriously as it's the only way I can see FSX moving forward at the high end with the extra VAS headroom it allows.

 

OOM's with a 64 bit OS are rare but they do happen. I do not think it has anything whatsoever with your settings. Your FSX settings look okay with the system you are running it on. I have a lessor system and today, I flew from KLAX to KSFO with RW weather, with ProATC-X running, in DX10 mode, with XPAX running, Shade, and with the PMDG737NGX. KLAX is from FSDT and KSFO is from FlightBeam. I have my FPS limited to 46 and the frames stayed steady at 45.9 throughout the flight. I did see a drastic reduction of FPS in the PMDG cockpit occasionally but, with the wingview, it was 45.9. In the cockpit, FPS stay between 22 and 30 FPS. I have never seen an OOM. My FSX.cfg is without tweaks but it does have the highmemfix installed. My settings are not high but my textures are crisp and clear. LOD is at the default of 4.5 but Texture_Max_Load is 4096. FSX was made for Vista and not with very high settings. I don't think it likes max settings. The super computers today can handle FSX much better with modest slider settings. We are trying to tweak a product 7 plus years old and it's getting harder.

 

But I digress. A possibility for your OOM's is an improper system memory configuration. Did you change the Virtual Memory (page file) settings to one of your own? If so, try System Managed Size as I think FSX, an old program, likes that better. The installed RAM may not be properly installed. Are the memory frequency, timings, and voltages correct? To make sure, check the CPU-Z and it should show your Frequency and Timings on the Memory tab. Now look over at the SPD tab and verify those timings are the same as one of the settings in the columns (the various memory settings allowed are also shown in the Tools tab of your BIOS). If not, you did to fix that. Your system and FSX will run great for a while with bad settings but, eventually you'll begin to see CTD's. I read somewhere that ASUS boards are not very good at configuring memory in the BIOS. ASUS usually puts the settings at Auto and sometimes they are right on and sometimes not. I personally had problems when I first put my system together and let the ASUS BIOS overclock my system. They said everything was working well and my system was overclocked (as I recall to 4.2GHz). A couple of weeks later a crash. I ran memory diagnostics, the Intel Burn Test, and Prime95. All were successful with no crashes. Ran FSX. Crash. So I changed the Auto settings for my memory to X.M.P. profile (the best profile you can use for YOUR memory). I set the proper frequency and then set the proper timings, and set my DRAM voltage to 1.65 (which you can do only with the X.M.P. profile). No more crashes.

 

You are overclocked and, if the CPU Voltage is set too high or too low, your system will crash. So these are the areas I would be looking at especially since you have a 64 bit OS and the OOM's just shouldn't be happening. Don't think you have perfect BIOS settings for your overclock. Yes, your system will operate for a while with bad settings and you'll pass some benchmark testing but when FSX is running and looking for a texture, a gauge, AI, whatever and uses more memory and CPU power, those "perfect" settings will bring your system and FSX down. I have my CPU voltage set at 4.0 and I'm only overclocked to 4.4. Once I lowered the voltage to 3.5 and my system and FSX got really upset with that so I went back to 4.0.

 

You have a very nice system and it should run FSX great. Members with lessor system specs are running FSX w/o problems. Hope you get it figured out what's causing your problem(s). Good luck!

 

Best regards,

Jim

I have FTX England installed and autogen maxxed with scenery density back one notch. . MyTrafficX 5.4 at 25%.

 

:rolleyes:

 

:rolleyes:

 

:rolleyes:

 

:rolleyes:

 

 

A 2 or 4gb card isn't going to help cure the 4gb VAS limit. My point was that running those addons in that already very hard area with the settings that he mentioned is what causes the OOM. It's a "glass ceiling" and a new videocard isn't going to fix it.

Got it. I misunderstood what you were getting at.

 

A gpu with lots if ram will be more likely to have an OOM error than one with less. For example on my old 1gb 460 I had few OOM errors. Now with a 3GB 660 I get them more often.

 

 

:rolleyes:

 

:rolleyes:

 

:rolleyes:

 

:rolleyes:

 

Yes Scarlett we know you have pretty eyes =).

 

Tell me about it. I was flying yesterday from FT OMDB to UK2000 EGLL, 7.5 hrs flight in total, in a nice HD painted PMDG 747, ORBX was activated, LOD was 6.5 though, and I was monitoring my VAS... was around 3.3GB, then 3.5GB when I approached Europe, up to 3.8GB when I crossed Germany, 3.9GB on descent over France, and when I descended up to 12,000ft, I was confronted with an OOM. Due to observing, I was saving my flight regularly (or I could just use FSUIPC Autosave), and I was able to recover, but was never able to land with LOD 6.5. Then I lowered the LOD to 4.5, and pray tell, I landed.

 

The time has come where we can't just barge in whatever we want into FSX. Community requires HD, so developers give us HD, each addon for it's own is going to work, but all them together, well, you can have to monitor your VAS and react as needed.

 

LM are working on the 64bit code, and it will still take some time, but I bet when this comes out, whenever it is, it will be a kind of a Holy Grail everyone will move to like bees onto honey.

 

Absolutely agree - we've just hit a dead-end street with FSX as far as potential HD expansion is concerned. At least in DX9 mode. But even if DX10 became more widely adopted by devs it too would hit the same ceiling eventually. I pray that P3D 64bit code will grace our PCs sometime this year. Good to see I'm not the only one having these issues. I'm just going to bite the bullet and pull back my autogen settings. There really isn't much else to be done as I've reduced my AI as far as I'm willing and it's hard to give up anything else much.

 

You have a very nice system and it should run FSX great. Members with lessor system specs are running FSX w/o problems. Hope you get it figured out what's causing your problem(s). Good luck!

 

Best regards,

Jim

 

Thanks Jim. Not sure if it will help much but I've pulled back my OC to more modest settings. My RAM has been set to run exactly to spec so I've manually set all the timings, speeds and voltages as per the intended design for my hardware. Also I've allocated 6GB for my pagefile manually (not system managed) so that covers that base. I've pulled my CPU OC back to 4.6 and reduced the voltage slightly. Ran Prime95 with it's max power usage/heat generation temps for 20 mins and was perfectly stable. The hottest one core got was 91. Not ideal but I figure nothing I run is likely to push it that far anyhow.

 

One thing I have noticed though is that temperatures are uneven across all six cores to the point where there can be a difference of 10 degrees Centigrade between two of them. Makes me think I botched something when applying my thermal paste and heatsink (maybe uneven spread or possibly the block not on firmly in some areas). I've purchased some MX-2 and will buy some rubbing alcohol this weekend to clean the existing stuff off and try again using the method described in a video I found on Youtube.

 

Thanks everyone for your comments and understanding of my frustration. I want to enjoy flight simming, I really do...but FSX is just making it harder and harder to do that in my case.

OOM's with a 64 bit OS are rare

 

I don't agree. If you run enough detailed addons at high enough detail settings, they are a regular occurrence.

A 64 bit FSX is the only solution to the OOM problem but like NASA told the Moon Program, forgetaboutit, it ain't going to happen.

It's true what is being said about P3D but remember it has not been loaded down like FSX. Just give it time and it will happen.

 

Now that XP10-64 bit maybe the P2D group will consider re-coding P3D into a 64 bit system. If they don't I have no doubt that P3D will go the same route as the XT computer.

Still useable as long as you don't try to run modern software on it.

 

If I wasn't too lazy to learn a new system and didn't have the huge software investment made in FSX I would be flying XP10-64 now. It allows developers to do things they only dreamed about using the FSX platform. For me the switch over button would be FTX/ORBX, REX and OPUS to start releasing packages for XP10-64.

 

Because I love bush flying, memory eating, highly detailed scenery and weather is a is what I want and need.

Looking for that 1000 ft strip cut from the trees in the bottom of a canyon with a gusting 20 knot crosswind to pickup a couple of hunters and their 600 pounds of Moose meat gets my juices flowing much stronger than "Bus Driving" across country with Nav Aids and ATC telling you what to do next.

 

I Hate OOM, really I do.

 

~~ Dale ~~

 

LM are working on the 64bit code, and it will still take some time, but I bet when this comes out, whenever it is, it will be a kind of a Holy Grail everyone will move to like bees onto honey.

 

At the point they release it with 64bit code is the day I move everything to that and never look back at fsx. For now I must keep my LOD at 4.5.

 

Sent from my Samsung Galaxy Note 2

 

 

Autogen max = auto OOM.

I got hit with an OOM the other day on my newly built system for the first time, so now I get what all the hysterics are about. Quite annoying. Was flying Orbx PNW coming in on final at KSEA and then bam!!! settings w/ LOD 6.5, TML 2048, heavy REX clouds etc etc., sliders generally at max. I haven't thought of checking VAS.

 

I also use a a heavy amount of AI, with Orbx AI and UT2. Kinda disappointed that I built myself a banging system, only to be limited by old code. lol. Can't win.

Autogen max = auto OOM.

 

+1

Autogen max = auto OOM.

 

Which is what everyone seems to do, as well as turn their traffic up to 100%, and then come crying to us with their OOM problems.

 

:rolleyes: :rolleyes: :rolleyes: :rolleyes: