After doing a bit of research I am beginning to wonder if those experiencing OOMS are jumping in and out of the cockpit.

 

Ah! That's a valid point! Also, as far as I recall, PMDG recommends using the View Menu to change views instead of the usual key shortcuts.

 

I believe that coming from the PS1 times, what matters to me is really the complexity of the simulation, the accuracy, the overall feel of the aircraft and systems. I seldom change to external views...

 

I also don't care using a good 2d panel.

I do believe system specifications do not effect VAS (other than 32-bit or 64-bit OSes), which causes OOMs. 

As under DX9 Video Ram is shadowed into VAS, maybe user with more than 1 GB RAM graphiccards will suffer earlier from OOM's.

 

 

There isn't much you can do except to uninstall/remove add-ons which are not used, turn down graphical settings. If you're doing a flight from Heathrow to Dubai, there's no need for your Aerosoft add-ons for Brussels, or FSDT etc to be enabled. I do believe they take VAS space up

 

But where ist it all going to end in the future, if developers are designing addons without having the limitations of a 32 bit application in mind.

 

Tomorrow with the next addon, I have to delete my complete texture folder or install this addon on a vanilla FSX.

Sorry, but this can not be the solution.

After doing a bit of research I am beginning to wonder if those experiencing OOMS are jumping in and out of the cockpit.

 

I never change my view but still have OOMS and my PC is £6000.

I never change my view but still have OOMS and my PC is £6000.

Wow, why on earth did you spend so much on that PC?! Did you pay someone to build it?

 

have started reading the DX10 forum, it looks like it will be the way forward, guess I will have to try an ultra long haul with DX9 once I get the 777 and see what happens.

 

 

I'm going to be installing UTX USA soon.

 

Installed. Not much effect on the VAS after an hour of messing about.

On which parts of my PC am I supposed to spend GBP 6.000 in order to overcome the limitation imposed by a 32bit application (FSX, VAS limit 4 GB, no matter how expensive my PC is)?!?

What we need is some sort of utility addon that will unload scenery after we are well past it on long haul flights. This would drop the vas usage on the long haul flights. Of course, developing something like that is probably extremely difficult or not even possible. 

I've got GEX for Europe, Africa and Middle East and North America. I'm going to be installing UTX USA soon. All AI is set to 0, I used to use traffic but that got me an average of 3-5 FPS around busy airports. I thought it would have been more usage over that period of time.

Ok, it must be UTX that causes a high VAS load for me then.

Even wirh zero AI traffic I think I start around 2.0Gb VAS at places I have GEX/UTX.

No way I can start a flight with 1.3Gb VAS only.

(but I will try and see at different places a little bit more)

 

Let us know what you get with UTX USA please!

My second longhaul flight with T7 KLAX-EGLL. Holding over BNN and I already noticed the beep from FSUIPC....minutes later booom OOM! Very amazing after a nearly 10 hours flight. :rolleyes:

Yesterday I got OOM just before touchdown in OMDB after 7 hours.

 

 

My LOD is set to standard: 4.5

I use absolutely no Ai Traffic

only 1024 dxt5 clouds in use

Win 7 64 bit

 

Sorry to say but at this stage this aircraft is useless for me and I hope PMDG will do some rework on this.

It is not the 777 that causes the OOM. Try the same flight in the NGX and refuel in the air a few times. I am pretty sure you will OOM as well.

 

If not THEN we have something to report to PMDG.

 

Do us a favour and post your VAS at the beginning of the flight and maybe at a few intervals.

Like every 2 hours or so.

 

My VAS seems to increase by about 100Mb per hour (but I have to do more testing).

If yours increases way faster then mine, then you might have an addon with a leak and we can try to identify that.

After doing a bit of research I am beginning to wonder if those experiencing OOMS are jumping in and out of the cockpit.

I have looked at that too. When I go outside VAS increases by about 100-150Mb. Then when I go back inside VAS reduces again after a few seconds by the same amount. It does that each time and I have tested at least 30 times on 15 different flights! So no problem with that here.

As under DX9 Video Ram is shadowed into VAS, maybe user with more than 1 GB RAM graphiccards will suffer earlier from OOM's.

 

 

 

But where ist it all going to end in the future, if developers are designing addons without having the limitations of a 32 bit application in mind.

 

Tomorrow with the next addon, I have to delete my complete texture folder or install this addon on a vanilla FSX.

Sorry, but this can not be the solution.

That is an interesting comment about GPU memory being shadowed in VAS!

 

Is that true?

I thought GPU memory only takes up (is mapped in) RAM space, not VAS?

Ok, interesting news!

 

I reinstalled Win7 and FSX from an image.

 

Then I ran windows updates followed by the install of some airports that were not installed in FSX at the time the image was taken.

 

Remember how I said VAS just keeps going up slowly but steadily during aech flight.

 

Well.....now it does not anymore!!

(only did one flight so more tests required)

 

I took off from KJFK with Aerosoft Manhattan X with a VAS of 3.5Gb.

During the flight VAS reduced by 200Mb while flying over USA/Canada. (GEX/UTX)

Across the Atlantic with x16 speed, it reduced more. VAS at landfall Europe was 2.8Gb.

 

Thats 700Mb less then what I started out with!

 

The only thing different in my setup compared to before:

All (I dont have that much anyway) addon scenery installed is now activated in the FSX library (nothing deactivated).

VTBS addon airport not installed yet.

 

 

How about that!?

 

EDIT: to be able to use x16 speed I turned off AItraffic untill on approach to destination Fly Tampa Vienna (LOWW).

I landed with 3.3Gb VAS.

i'm getting frustrated now. I am flying 737ngx from cyul to kfjk and I am going OOM now. I am at 2.6-2.8 before takeoff. I have turned off all traffic. There is a bad snow storm I had to takeoff in , so I wonder if that is what is pushing it soo high. I am also using track ir for the first time, but that wouldn't use vas would it? 

I never have an OOM problem since I reduced LR settings to 4.5 with PMDG-777

 

[TERRAIN]

LOD_RADIUS=4.500000

I never have an OOM problem since I reduced LR settings to 4.5 with PMDG-777

 

[TERRAIN]

LOD_RADIUS=4.500000

 

Ditto.

 

Mine are very few and far between with that setting as well (and setting my CFG to 2048 textures helped greatly as well)

i'm getting frustrated now. I am flying 737ngx from cyul to kfjk and I am going OOM now. I am at 2.6-2.8 before takeoff. I have turned off all traffic. There is a bad snow storm I had to takeoff in , so I wonder if that is what is pushing it soo high. I am also using track ir for the first time, but that wouldn't use vas would it?

 

What payware do you have for KJFK?

 

Ok you start with 2.6-2.8.

 

I just went back through this 3 page thread.

you have only stated that you OOM.

Not once have you mentioned if you tried the many suggestions we have given.

 

Reduce auotgen/complexity slider settings.

deactivate things from the library you dont need.

(this can also help in identifying a possible memory leak)

Like mentioned above...LOD 4.5

Do no use HD cloud textures!

 

Next,

Did you look at regular intervals how VAS develops?

Check VAS before starting your descend also!

 

If you were to do the flight the other way around, so KJFK - CYUL what VAS do you start out with then?

 

Because if your KJFK puts a hige load on VAS then you would probably OOM on any flight going in there.

Like me, with my very high autogen/complexity settings, I start at 3.6Gb or so at KJFK because Manhattan X puts a high load on VAS. (thats fair weather!!)

(I think it is Manhattan that does that, but have not checked actually. I will try by turning it off in the library)

That is 1.0 Gb higher then other airports!

So I figure if I want to fly into KJFK I need to start the descend with max 2.9Gb VAS used or I end up OOMing on approach.

 

 

Like I said before, when it gets real high (3.5Gb), save your flight and restart FSX.

This empties VAS.

I have fsdt kjfk. I don't use manhattan X. I lowered some of my settings, although I have noticed my 737ngx cockpit looks absolutely horrible at night now. Right under the glare shield there are all these lines running through it. I can't seem to find the setting to fix it and its really ugly. 

I have fsdt kjfk. I don't use manhattan X. I lowered some of my settings, although I have noticed my 737ngx cockpit looks absolutely horrible at night now. Right under the glare shield there are all these lines running through it. I can't seem to find the setting to fix it and its really ugly.

 

I edited my post above a little while you responded. read again please.

 

What setting did you change that made your cockpit look horrible?

 

That should not happen and might indicate other problems.

 

Are you sure you OOM?

(you hear a beeping sound before the message "FSX has run out of available memory shows" (or something like that).

 

You are not CDT-ing (Crash to Desktop) are you?