Once I had a OOM and the msg appeared to tell me that, I didn't press the Ok button and it let me end the flight. Don't know if that is normal, but you can try. If you press the ok button, you will exit. You can give it a try not pressing it, and leaving the message box semihided (I was in window mode)

I got it to and idd i did not press and vola i can finish my flight but i never expected a OOM never had any before.

Let me explain my FSX settings again.

I am a very experienced FSX user, I know what kind of tweaks influence what, how and when. I am running my fsx.CFG tweaked by the Venetubo website. The only tweak I've added under BufferPools is the setting PoolSize=0. This is a tweak I will never fly without because it increases performance by at least 30%. I have been running this fsx.CFG for a long long time, and haven't done an FSX reinstall in ages. 

In FSX, resolution is set to 1080p, aircraft shadows are disabled, scenery is maxed out with water on HIGH2X and ground scenery shadows disabled. Clouw draw distance is set to 80 nm and cloud coverage is set to maximum. All, I repeat ALL AI traffic is disabled at all times.

For the rest in my fsx.CFG, TEXTURE_MAX_LOAD=1024 (never use 4096), LOD_RADIUS=4.5 (default). For the rest, no other tweaks have been made. 

Before I bought the 777, I wanted to make sure my FSX was stable. So I did over 20 flights in the NGX without a SINGLE issue. I did both long and short hauls, into small and big detailed airports, all of them were flown on IVAO. NEVER HAD AN OOM, NEVER HAVE I HAD AN OOM BEFORE IN FSX.

I bought the 777, and immediately on my first flight, I could hear the bells sounding the background when landing into Aerosoft LFPG. 

If my FSX worked so well before, and I am suddenly experiencing an OOM with the PMDG 777, then the problem can't be anything else than PMDG 777 related. It might not be the MAIN cause, but it might be the straw that breaks the camel's back. 

Note: when I did this flight I where I experienced an OOM, I actually used a CLEAN fsx.CFG with HIGHMEMFIX=1 and PoolSize=0 because I wanted to experiment with performance! 
 

I got it to and idd i did not press and vola i can finish my flight but i never expected a OOM never had any before.

 

That is good to hear! I had once and did what I explained only once. At least we can finish the flight!! and online they can see you! Suppose there will be graphical issues... but in my case was at the ILS localizer (with the concordeX) and I could end the flight normally.

 

Would like to hear someone that didn't press the OK button at the very beggining and let continue the flight for some hours... if it was possible...

Well I just did a test using fsuipc's remaining vas offset. It will display remaining vas on the fsx application bar. So I set up at Flytampa KTPA, current time 6:30 am, no weather, no ai, normal autogen, 4.5 lod, no traffic. Loaded up NGX in default panel state. I panned around the cockpit, went to locked spot and panned around the aircraft several times, and then back in the vc. Alt enter to windowed so I can see fsuipc's offset; remaining vas 2036000. So 2.03gb. Did the same exact thing with the 777X; remaining vas 1700000. 1.7gb. So the 777X uses about 300 more mb than the NGX. If you didn't have 300 to spare when running the 737, well then there you go. I will say I've done two flights; the tutorial to FT Dubai and KPAE to FT Tampa, both with similar settings as above test, but adding 40% commercial UT2 traffic, and no issues. FTXG and UTX as well. I used 4x auto cruise on tampa flight. Perhaps there's a memory leak with some people. Maybe your install was corrupted or something; I don't know.

 

Edit: Also the NGX was using the low res options from the performance manager. I was testing with that and forget to change back. So that will bridge the gap even further to the 777X. When the dev tells you it doesn't use much more vas than the NGX, you should believe him.

 

One more thing I wanted to share about disabling scenery you don't use. I have a lot of Orbx aiports. With FTXGlobal in default mode, those airports now remain enabled in the scenery library. Disabling them freed 150 MB!!!!!! And I was halfway across the country in Florida. I also prevented the airport DLL's from running, and that added another 30MB!! So does everyone now understand why you should only enable sceneries you need?

Well I just did a test using fsuipc's remaining vas offset. It will display remaining vas on the fsx application bar. So I set up at Flytampa KTPA, current time 6:30 am, no weather, no ai, normal autogen, 4.5 lod, no traffic. Loaded up NGX in default panel state. I panned around the cockpit, went to locked spot and panned around the aircraft several times, and then back in the vc. Alt enter to windowed so I can see fsuipc's offset; remaining vas 2036000. So 2.03gb. Did the same exact thing with the 777X; remaining vas 1700000. 1.7gb. So the 777X uses about 300 more mb than the NGX. If you didn't have 300 to spare when running the 737, well then there you go. I will say I've done two flights; the tutorial to FT Dubai and KPAE to FT Tampa, both with similar settings as above test, but adding 40% commercial UT2 traffic, and no issues. FTXG and UTX as well. I used 4x auto cruise on tampa flight. Perhaps there's a memory leak with some people. Maybe your install was corrupted or something; I don't know.

 

Edit: Also the NGX was using the low res options from the performance manager. I was testing with that and forget to change back. So that will bridge the gap even further to the 777X. When the dev tells you it doesn't use much more vas than the NGX, you should believe him.

 

One more thing I wanted to share about disabling scenery you don't use. I have a lot of Orbx aiports. With FTXGlobal in default mode, those airports now remain enabled in the scenery library. Disabling them freed 150 MB!!!!!! And I was halfway across the country in Florida. I also prevented the airport DLL's from running, and that added another 30MB!! So does everyone now understand why you should only enable sceneries you need?

I noticed the same thing! It's using at least 300 MB more, while the Introduction claims it was designed not to use more than the NGX, which is not true.

Well I've done some more experimenting with the 777 and FSDT CYVR tonight.

My Texture maxload is 2048, LOD4.5, Highmemfix=1. The only scenery I had enabled was FSDT CYVR, Vancouver +, and all UT Canada sceneries. UT2 traffic was set at 75% for commercial traffic, Opus weather running. I used the Air Canada livery for the 777, natch! GEX textures for North America.

 

Tonight I didn't even get close to OOMing. One change I made was the scenery order priority of Van+ which I moved to highest priority. This helped immensely. I did notice that as soon as I flew out of the vicinity of the airport the VAS load dropped.

 

I also tested the same aircraft with all the Flightbeam trial sceneries, LatinVFR KSAN, and FSDT PHNL. The VAS load was about the same, high but certainly not going to bust the limit.

 

FT's OMDB did come pretty close to the VAS limit. When I stopped the 777 on a taxiway there, I swapped it out for the PMDG 747 and noticed quite a drop in the VAS. So from my observations (certainly not scientific!) the 777 does increase the VAS load in comparison to other aircraft, (I don't have the NGX) but I believe it is manageable. I haven't checked all Ryan's recommendations for tweaks in the Introduction manual but I think I do have some of them already. Will need to check further.

 

Haven't had a proper flight in my 777 yet, have spent too much time checking out performance at complex airports! Off to bed now, but I know what I'll be doing over the weekend!

Cheers,

does anybody knows(tested)if time compression feature can increase VAS maybe? It was the first time when i used it, and the first time when i came close to OOM...Just a posibility... I never used this before so i realy don't know if time compresion can have any effect on VAS

Thanks heaps to Shug and Arjen for providing us with some factual information. 300MB is a sizeable difference.

This is what I had suspected: The 777 does have a higher memory footprint contrary to what was said before. No big deal, but one has to know about it in order to configure this deeply flawed and aged sim.

 

As mentioned in the previous post, something else worth considering is the effect of "Auto Cruise" on memory. In my flight I noticed the simulation rate constantly ramping up and down, even far from waypoints or step climb points. Every time the simulation rate drops to 4 or below FSX will reload all AI traffic. On my flight from EDDL to OMDB this occurred constantly. Maybe that caused some extra memory usage or memory fragmentation (AI textures are supposed to be small after all). Just a thought.

Sounds like you don't have any personal experience with the art and science of overclocking.

 

LOL! Looks are deceiving my friend.

 

Want proof CPUs mis-behave when overclocked? It is used to conduct cryptanalysis. By overclocking the processor you can make it do things it shouldn't. If an overclock was as simple as you say, there wouldn't be any difference over a normal processor when attacking a system this way.

 

I could go on for hours how there are MULTIPLE clock sources within the processor, and that they do not scale linearly with the clock speed you play with, if they change at all, leading to mis-timings within the processor itself, and odd things happening even though the system may appear to be running normally.

 

Sir, I know what I'm talking about when I say overclocking is bad for your health.

 

Best regards,

Robin.

It is used by some cryptographic attacks. By overclocking the processor you can make it do things it shouldn't. If an overclock was as simple as you say, there wouldn't be any difference over a normal processor.

 

Huh? Sorry I have no idea what you just said. And I have a degree in Computer Engineering with a major in Security.

I just finished OMDB-KSFO in the 77L, 14h43min - enroute was fine, but @ SFO all the buildings were gone - this might be a memory problem but it also may be the Addon Manager used by FlightB.

I just finished OMDB-KSFO in the 77L, 14h43min - enroute was fine, but @ SFO all the buildings were gone - this might be a memory problem but it also may be the Addon Manager used by FlightB.

 

Most likely the addon manager.

 

On the OOM, I will need to reduce some settings and give it another go tonight. What's annoying, is the fact that the T7 performs superbly for me in the VC, a lot better than the NGX. I will not jump into any conclusions though until I test a few things for the next few days.

 

This is exactly what the Scenery Library is for! If you have an addon airport in Switzerland, and fly a U.S. route, part of that Swiss addon WILL load into memory, no matter where you're flying.

 

The question is.......why? If you are flying nowhere near Switzerland, why the hell is anything in Switzerland being loaded into memory??

The question is.......why? If you are flying nowhere near Switzerland, why the hell is anything in Switzerland being loaded into memory?? This is something that I simply can't understand with FSX. It doesn't make any sense.

 

Ask the guys who programmed FSX. Probably easier than thinking about an algorithm that loads and unload only what you need.

 

That sounds like me! :lol: