Pls. search the forum for similar issues before opening the umpteenth identical topic.

 

 

+1, but I don't blame the OP here. He's just doing what everyone else is.

 

This problem (here and elsewhere) has become so bad it's reached the level of being grossly counter productive or even hurting things. It's not just here, otherwise "Let Me Help You With That" - merely a polite way of saying "you could and should have searched for the answer yourself" wouldn't exist.

 

See, the way that search engines work, it won't be too much longer before searches no longer show the older posts that have the answers, even on page 10, 15 or 20 of the search results. There have been several problems for which I've recently searched for the answer that I once read online, and it's not to be found. Just repeated posts of the same issue, which have taken up residence in the index.

 

The other problem this creates is that people who know the answers start bypassing these posts when they see them for the umpteenth time, thus leaving the OP with the well meaning advice from newer users, which may or may not be accurate. I'm not saying that all newer users post inaccurate info, but when good info is mixed in with the bad, who do you believe - especially when advice may mess up one's install?

 

I don't think there is any stopping it at this point. It's a world wide trait, and given so I don't blame the OP here. He's just doing what everyone else is.

 

Some may be too young to remember the "Island of Misfit Toys", but I think of all that sage wisdom in the posts of old being on an island like that.

 

 

Dave

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

.

I have pay 70 euro for the PMDG 777!!!! and every time i have a out of memory, this is frustrating me.  it is only on this plane,

 

What people seem to have a hard time understanding is that it's not one item causing OOMs... it's the addition of everything.

Let's say the VAS limit is 10 (whatever unit, it's juste a theoretical example) :

- 5 used by default FSX only

- 2 by sceneries

- 1 by AI traffic

- 3 by the T7

- 2 by the 737

 

Fly the 737... you're at the limit... let's say it's ok.

Fly the 777... bam ! OOM

 

Is it PMDG 777's fault ? AI's fault ? All of them ? None of them ? Maybe you're using a scenery which is 10 times harder on VAS than the T7 and you don't even know it... yet, you blame the T7 (again, theoretical example, definitely unrealistic... i'm just saying that it's kind of nobody's fault or everyone's fault... it's not the "last installed"'s fault)

 

The T7 may have more impact on VAS than the 737... it doesn't mean the 777 has a problem regarding VAS usage. Is it justified to you ? Completely subjective... sadly, you don't get to choose, that's just the way it... dictated by programming requirements (though, it doesn't mean VAS usage couldn't be reduced, maybe it could be optimized, but we don't know that).

 

You could say it's T7's fault if it had a memory leak... but either everybody would have issues (obvious memory leak) or you probably wouldn't have it for every flight (rare conditional memory leak).

 

So, in the end, it's your job to stay within limits... you want to use the T7 without OOMs ? Decrease quality elsewhere ! Flying the 737 ? Let's re-increase your settings to what you're used to.

Ok i have tested now again with pmdg 737 approach egll no out of memory 

traffic settings from 100% to 45 %.

I am not starting debates about whether this is PMDG's fault or not, but these are the facts:

-  FSX is a 32-bit application meaning it cannot use more than 4GB of Virtual Address Space. It it uses more, you get an OOM

-  You need to adjust your settings properly to be able to run FSX without an OOM.

-  The PMDG 777X uses around 200-300MB more VAS than the PMDG 737NGX.

Currently this plane cannot be used to its full potential in my opinion, which is, flying it into big cities and big airports surrounded by AI. Doing so will often cause an OOM. So you're left with two options: 1, you lower the settings just for this plane, or 2, you avoid big airports and cities which makes this airplane kinda pointless IMO.

All this is currently possible just fine with the PMDG 737NGX. Therefore I think PMDG needs to do their best to lower the detail - or at least include an option - which will bring VAS on par with the NGX.

Ok i have tested now again with pmdg 737 approach egll no out of memory 

traffic settings from 100% to 45 %.

PMDG 737 is not PMDG 777 you need to test it with the aircraft you want to fly. have you actually done anything that we suggested here?

It's not the same product, not the same plane, it doesn't have the same systems, not the same features... So it does not use the same amount of memory. You can't really expect something probably more complex to have the same requirements.

 

For example, the ECL is necessarily having an impact on VAS. How big ? Would it be possible to make an option to completely deactivate it ? Would users be happy with that ? Would it be worthwhile ? What else could be deactivated ? Would it still be a 777 ?

 

Thing is, i don't think PMDG uses memory just for fun and they don't do miracles (huge scenery, tons of AI aircraft, HD textures, multiple plugins [btw, ezca is kind of hungry for what it does in my opinion] and deep T7 simulation)... I'm pretty sure they're doing their best to lower VAS usage... But, at some point you either make a complete simulation or you make compromises (feature wise), something PMDG users are not used to (my opinion - some are still asking for more : stairs truck, taxi camera for the 300ER, HUD, ...).

 

As is (a complete simulation), i can imagine why the 777 uses more memory than the 737.

That's a tricky balance... Features vs VAS

here my suggestion to prevent OOM

 

1. dont change view all the time 

2. make sure your operating system is 64bit not 32bit

3. dont maxed out the ai settings

4. turn off the dx10 preview

5. turn off the light bloom although is an eye candy but sometime it can f*ck up your FSX

6. disable the scenery that your not gonna fly to.

7. don't do the uiautomationcore trick unless you have OOM error all the time

8. limit your simulation rate 2x minimum 8x maximum

9. dont alt tab or alt enter all the time

10. make sure you have the right graphics driver. i suggest you download the 314.07 if your using nvidia

11. don't use pirated add ons

12. dont over tweak your .cfg trust me i only have a few tweaks in my .cfg and my FSX runs very well even though my system is 4 years old

13. limit your right clicking and accessing at the menu while inflight

 

 

Why isnt there a way to change the VAS usage in Windows? Or is it not mathematically possible?

Why isnt there a way to change the VAS usage in Windows? Or is it not mathematically possible?

It is not windows per se. It 32 bit architecture.

FSX is 32 bit and will always be limited to a 4 Gb VAS, no matter in witch OS you run it.

In addition to the 13 suggestions above, keep LOD_RADIUS at 4.5 for the PMDG 777 and tweak AI and autogen to stay within limits. Use FSUIPC to monitor your VAS usage during the flight. I find if I don't switch views too much I stay within limits.

 

Glynn

 

 

4. turn off the dx10 preview

 

 Quite the opposite.  Running in DX10 preview reduces the VAS by a good margin.

 

 

 

FSX is 32 bit and will always be limited to a 4 Gb VAS, no matter in witch OS you run it.

 Not exactly true, only the 64bit versions of Windows allow up to 4gb of VAS, if your OS is 32bit it will allow 2gb and up to 3gb with the proper adjustment.

 Not exactly true, only the 64bit versions of Windows allow up to 4gb of VAS, if your OS is 32bit it will allow 2gb and up to 3gb with the proper adjustment.

That's true. Thanks for the correction.

Why isnt there a way to change the VAS usage in Windows? Or is it not mathematically possible?

"Mathematically"... Not sure it's the right term but... Yes, it sort of is the source of the problem.

 

Each byte of memory has its own adress so it can be read and written. The number of bits determines the number of adresses you can have. Each bit contains either a 0 or a 1 (= 2 possibilities per bit). So, with 32 bits you have 2^32 (= 4 294 967 296) adresses possible. Each adress points to a byte hence 4 294 967 296 bytes (= 4 giga bytes) can be adressed. If you need a 4 294 967 297th byte, you just run out of adresses and you run out of space to store the adress you need > error

 Quite the opposite.  Running in DX10 preview reduces the VAS by a good margin.

 

 

 

 Not exactly true, only the 64bit versions of Windows allow up to 4gb of VAS, if your OS is 32bit it will allow 2gb and up to 3gb with the proper adjustment.

wow really? 

wow really? 

 

Dx10 can reduce VAS by around 200-300MB - its more efficient