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 

Do you have the latest version of the 777 installed?

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.

Global FTX

Vector FTX

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

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

These two sets of software take up memory

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

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

Have you got FlyTampa Sydney installed?

Have you got FlyTampa Sydney installed?

YES FlyTampa Sydney 1.1

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

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.

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

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.

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

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

Have a read though my guide in my sig