Sign in to follow this  
Hao Henry

YSSY-VHHH OOM

Recommended Posts

Hello

 

Yesterday
 
I flew to the VHHH to get to the YSSY-VHHH to use 25R into the near, the memory began to alarm after OOM
 
OMDB-VHHH-OMDB has no problem with the previous day
 
VHHH T2G 1.2 version
 
Global FTX
 
Vector FTX
 
My configuration:
 
4790K 16GDDR GTX980 512SSD 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Do you have the latest version of the 777 installed?

YES 

 

I started VHHH-YSSY for 9 hours without any problems
 
But from the YSSY-VHHH will be the problem of OOM
 
I can't turn off RAAS and Vector FTX.

Share this post


Link to post
Share on other sites

Global FTX

Vector FTX

I see these items appear again and again on threads about OOMs.

Share this post


Link to post
Share on other sites

I see these items appear again and again on threads about OOMs.

These two sets of software take up memory

Share this post


Link to post
Share on other sites

You need to give us more details about the circumstances.  Which simulator you are using, AI settings, weather settings, etc. etc.

Share this post


Link to post
Share on other sites

You need to give us more details about the circumstances.  Which simulator you are using,, weather settings, etc. etc.

Thank you
 
My simulator is Prepar3D 2.5, no use of AI traffic
 
ACTIVE SKY NEXT SP2 
 
REX4
 
The simulator is set to medium ground map 1024*1024 and the resolution is 1920*1080

Share this post


Link to post
Share on other sites

I recently found that reducing max texture resolution to 1024 greatly improves OOM problem (especially in VHHH).

Share this post


Link to post
Share on other sites

True about what Danny F says about res 1024. Turning of autogen also helps you to not get OOM. I have been flying 10-15 hours leg between heavy airports like FlyTempa EKCH, VHHH, NL-2000 EHAM etc. etc. with FTX Vector, Global, Open LC Europe etc without having OOM problems with the 777. Just now I'm over Chad Africa from Rio to Dubai and I started with 2,8 GB in virtual memory in use in Rio and right now it's on 2,6 GB in use. So take a look on your settings. Turning of scenery you don't be landing on also helps.

 

On final approch and you starting to hear OOM pling warning from FSUIPCS, switch to full screen (Alt-Enter) if you are in window mode, This reduce about 200 of virtual memory and can save your landing.

Share this post


Link to post
Share on other sites

FlyTampa Sydney has a LOT of high resolution textures. I had to reduce mine to 1024x1024 so that the airport becomes usable with complex addons. Even in a short flight it will cause issues with the 777 or another similar addon.

 

I understand that airport designers strive for quality, but as long as we're stuck in 32-bit there should be an option to lower the texture size in order to reduce or eliminate the chance for OOM. Maybe a 32/64-bit mode for when/if we get a 64-bit platform :P

Share this post


Link to post
Share on other sites

I believe that, once an airport is loaded, much of the memory used is maintained even though you have flown away from the airport. Then, when you approach your destination, another set of airport scenery is loaded. This may then cause an OOM.

 

My solution has been to:

  1. start my flight at an airport for which I already have a saved file
  2. move the aircraft to the departure airport for my current flight (I now have 2 airports loaded)
  3. save the situation flight at that airport
  4. exit the simulator and then restart and load the saved file (I now have only a single airport loaded
  5. during flight, save the current situation and exit the simulator
  6. restart the simulator with the in-flight save and continue to the destination (with only a single airport loaded as I approach the airport).

I hope this may help.

Share this post


Link to post
Share on other sites

I recently found that reducing max texture resolution to 1024 greatly improves OOM problem (especially in VHHH).

thank You
 
My settings are 1024*1024

True about what Danny F says about res 1024. Turning of autogen also helps you to not get OOM. I have been flying 10-15 hours leg between heavy airports like FlyTempa EKCH, VHHH, NL-2000 EHAM etc. etc. with FTX Vector, Global, Open LC Europe etc without having OOM problems with the 777. Just now I'm over Chad Africa from Rio to Dubai and I started with 2,8 GB in virtual memory in use in Rio and right now it's on 2,6 GB in use. So take a look on your settings. Turning of scenery you don't be landing on also helps.

 

On final approch and you starting to hear OOM pling warning from FSUIPCS, switch to full screen (Alt-Enter) if you are in window mode, This reduce about 200 of virtual memory and can save your landing.

Thank you for your help.
 
I've been using the window mode to fly

FlyTampa Sydney has a LOT of high resolution textures. I had to reduce mine to 1024x1024 so that the airport becomes usable with complex addons. Even in a short flight it will cause issues with the 777 or another similar addon.

 

I understand that airport designers strive for quality, but as long as we're stuck in 32-bit there should be an option to lower the texture size in order to reduce or eliminate the chance for OOM. Maybe a 32/64-bit mode for when/if we get a 64-bit platform :P

Thank you for your help.
 
I think that is also the meaning of my settings have been 1024*1024, and reduce some of the plug
 
I think there is a problem with the VHHH Airport

I believe that, once an airport is loaded, much of the memory used is maintained even though you have flown away from the airport. Then, when you approach your destination, another set of airport scenery is loaded. This may then cause an OOM.

 

My solution has been to:

  1. start my flight at an airport for which I already have a saved file
  2. move the aircraft to the departure airport for my current flight (I now have 2 airports loaded)
  3. save the situation flight at that airport
  4. exit the simulator and then restart and load the saved file (I now have only a single airport loaded
  5. during flight, save the current situation and exit the simulator
  6. restart the simulator with the in-flight save and continue to the destination (with only a single airport loaded as I approach the airport).

I hope this may help.

 

Thank you for your help.
 
I'll try it on your way.
 
Thank you

Share this post


Link to post
Share on other sites

Have a read though my guide in my sig

 

That I can recommend to read either you use P3D or FSX. Very good guide you have made there David ^_^

Share this post


Link to post
Share on other sites

VAS use is an issue that requires the full picture.

 

You have a limited number of bits. When you hit the maximum number of bits, you're out of memory and the program quits. Everything you see in the sim uses memory. For some reason, people seem to concentrate on the aircraft (which is why the OOM threads seemingly end up here). Our aircraft do use more memory than some of the simpler offerings out there, but most VAS use comes from scenery (necessarily so, if you want higher visual realism). Other addons have a highly variable amount of VAS use (again, necessarily so).

 

If you don't have a program crash one day, but you have one on another day, then it's likely it's "caused" by the variable amount used by one of the variable addons. The usual suspect in this case would be a weather addon.

 

We have been pretty candid about the facts surrounding this issue, and have even provided possible remedies to help guide people in cutting VAS use back slightly. Where you're willing to cut back on detail to help cut back on VAS use is entirely personal, as some are more willing to sacrifice weather visuals, whereas others are more apt to cut back on autogen, or airport detail, or shadows, and so on.

 

There is no "fix" for this. There's a conscious evaluation of where you want to cut. It's like a budget: you have a set amount of money. What you do with it is up to you, but you can't use more than you have.

Share this post


Link to post
Share on other sites

That I can recommend to read either you use P3D or FSX. Very good guide you have made there David ^_^

Thank you

 

 

There is no "fix" for this. There's a conscious evaluation of where you want to cut. It's like a budget: you have a set amount of money. What you do with it is up to you, but you can't use more than you have.

 

yep that's a good sum up.

 

But you can make changers to help. Perhaps change my guide to "how to spent your VAS budget"  :smile:

Share this post


Link to post
Share on other sites

I see these items appear again and again on threads about OOMs.

FTX Global is fine and uses the same size textures and stock FSX and GEX. Since it just replaces the default textures with a new set the same size it doesn't cause any difference in VAS usage.

 

FTX Vector on the other hand can take a large toll on VAS usage if all the options are used. UTXv1 or v2 can cause the same high VAS usage if to many options are turned on. I don't have Vector but I do own UTX and it's UI let's you know how much of a performance hit you can expect using certain vector drawn items like residential roads and things of that nature. If I turn on all the UTX option and try to fly I can immediately tell the difference in not only FPS but VAS usage.

 

If you're primarily flying airliners, there are a lot of unnecessary features that can be turned off in UTX and Vector to save VAS and FPS.

 

 

Sean Campbell

Share this post


Link to post
Share on other sites

I believe that, once an airport is loaded, much of the memory used is maintained even though you have flown away from the airport. Then, when you approach your destination, another set of airport scenery is loaded. This may then cause an OOM.

 

My solution has been to:

  • start my flight at an airport for which I already have a saved file
  • move the aircraft to the departure airport for my current flight (I now have 2 airports loaded)
  • save the situation flight at that airport
  • exit the simulator and then restart and load the saved file (I now have only a single airport loaded
  • during flight, save the current situation and exit the simulator
  • restart the simulator with the in-flight save and continue to the destination (with only a single airport loaded as I approach the airport).
I hope this may help.
I think you could save yourself a lot of that preparation. Simply save the flight enroute and then restart FSX and load the flight save. It won't reload your origin airport scenery as it isn't near to the current position.

 

Even better is to use autosave. Then you will always have a recent flight saved in case you get OOM warnings and need to restart. No OOM warnings and you have an uninterrupted flight.

Share this post


Link to post
Share on other sites

Hi Kev,

I already do the autosave every 30 mins with FSUIPC as you suggest. The only thing is that my little brain hadn't thought of just reloading the autosave mid-flight (and potentially losing up to 30 mins of the flight). Good idea!

Cheers, R 

Share this post


Link to post
Share on other sites

It also might be a good ide to delete all the unnecessary files that FSUIPC saves in example \Fsx\PMDG\PMDG777\Panelstate folder. It can be lots of thousands of files based on how often you save your flights. I have standard that I clean of those files everytime I have been finish with a flight.

Share this post


Link to post
Share on other sites

Hi Kev,

I already do the autosave every 30 mins with FSUIPC as you suggest. The only thing is that my little brain hadn't thought of just reloading the autosave mid-flight (and potentially losing up to 30 mins of the flight). Good idea!

Cheers, R 

I have my autosave set for once per minute. Not sure if that's possible with the FSUIPC system, I use a freeware save utility. I need to be able to reconnect quite close to where it crashed or my VA ACARs won't allow the reconnection and the flight is lost.

 

It also might be a good ide to delete all the unnecessary files that FSUIPC saves in example \Fsx\PMDG\PMDG777\Panelstate folder. It can be lots of thousands of files based on how often you save your flights. I have standard that I clean of those files everytime I have been finish with a flight.

Yes you can end up with an awful lot of files. I wrote a batch file to delete them for all my addons (and in the main flight save folder). It's a one click clean up process rather than a lot of manual file deletions.

Share this post


Link to post
Share on other sites

That you can do also. I just drag the mouse over all the files starting with Autosave and hit the shift+delete buttons :P

Share this post


Link to post
Share on other sites

My preference, instead of autosave, is to simply save before TOD. It's become a habit and quite easy to do even if unattended because there is an option for a pause right where you need it.  I often get back over 800 mb of VAS after save/exit/load sequence and it allows me to spend more of my "budget" where I want to.... hey, that Vector N.Calif coastline is awesome even at flight levels.

 

This works 99% of the time.

 

However, Aerosoft PANC to FSDT KLAX does require save/exit/load at both TOC and TOD... all the fault of that beautiful scenery (and Aerosoft's complete abandonment of constraint).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this