Sign in to follow this  
TszChun

Have Anyone Here flown into FlyTampa Toronto CYYZ without OOM?

Recommended Posts

Hello all,

 

I haven't experienced oom for a long while since I dicovered the workaround to significantly reduce the risk of OOM (not to select STAR in preflight stage but before descent, because the VAS may continuously accumulate en-route if the STAR has a certain kind of missed approach precedure), but everything got ruined when I flew my PMDG 777 into CYYZ.

 

I am just curious to know if there is someone who has successfully fly a PMDG 777 into Flytampa Toronto CYYZ. Even though I had a flight from Flightbeam KSFO HD to FSDT KLAX, I didn't experience OOM. My settings are definitely not agressive, but moderate. I have no idea why I still got OOM...

 

I have tested the sceneries by Process Explorer, and noticed that 3.1 to 3.5GB VAS has been used just after I started the flight at gate and pan around the cockpit...I have FTX Global with Vector installed. You may say it consumes VAS so much and should be the cause of the OOM, but I have successfully made flights without OOM with the same settings and addons installed for almost a year. Therefore I think there should be some other reasons...

 

In addition, although I have turned "Transparent Glass and Interiors" option ON, I still can't see through the glass of terminals. Does anyone here having any idea?

 

Here are some crucial parameters in fsx.cfg

LOD_RADIUS=4.5
TEXTURE_MAX_LOAD=4096
IMAGE_COMPLEXITY=4
AUTOGEN_DENSITY=3

Here are my settings in Flytampa Configurator:

3D Grass...OFF
3D Grass (ramp)...OFF
3D People...OFF
Static Vehicles...OFF
Animated Cars...OFF
Animated Apron Traffic...OFF

Transparent Glass and Interiors...ON
(all options in "effect" section)...ON
Animated Traffic Lights...ON

Anson Cheung

Share this post


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

I don't have this airport, but i know it's a bad idea to set TEXTURE MAX LOAD to 4096. Set it to 2048 and try again, you should be fine.

Do you have 4096 in fsx.cfg or you have installed CYYZ 4096 textures? In any case, set both to 2048, but in fsx.cfg is more important to do this :)

 Also, disable all other add-on scenery that you don't need for current flight, especially photo scenery, here is a great tool for that: https://sourceforge.net/projects/fs-sceditor/

Share this post


Link to post
Share on other sites

I don't have this airport, but i know it's a bad idea to set TEXTURE MAX LOAD to 4096. Set it to 2048 and try again, you should be fine. Also, disable all other add-on scenery that you don't need for current flight, especially photo scenery, here is a great tool for that: https://sourceforge.net/projects/fs-sceditor/

 

Thanks for your quick reply.

 

I have researched into different parameters which would be the possible causes of OOM, and TEXTURE_MAX_LOAD is the one. As I know FlyTampa created the scenery by 2048 textures, plus I have used this settings for almost a year without OOM, so I dont think it affects much.

 

Also, I have Flytampa CYYZ only in that area, so it is almost impossible that other addon sceneries causes the OOM.

 

Anyway thanks very much for your answers!

 

Anson

Share this post


Link to post
Share on other sites

Did you install the "Lite" version?  I have a terrible time at this airport, not OOM issues as much as bad frames (NGX). All of my other payware airports, including their KTPA perform great.

Share this post


Link to post
Share on other sites

Also, I have Flytampa CYYZ only in that area, so it is almost impossible that other addon sceneries causes the OOM.

 

All sceneries that are enabled in scenery library will use some VAS, which leads to OOM. It doesn't matter in which area you fly. You can fly in Europe and sceneries from China will use VAS if enabled.

 

You can test it and see which settings are affecting VAS a lot. Get process explorer https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

 

You can also try this fix if you are on windows 7, i don't know about other versions: https://support.microsoft.com/en-us/kb/947246  It helps a bit, but settings are more important

Share this post


Link to post
Share on other sites

I don't get any OOM issue but my textures are limited to 1024. I have never tried with 4096.

Share this post


Link to post
Share on other sites

Did you install the "Lite" version?  I have a terrible time at this airport, not OOM issues as much as bad frames (NGX). All of my other payware airports, including their KTPA perform great.

 

I haven't got the lite texture pack installed just because I want to enjoy the amazing visual effect created by FlyTampa. But still I would install it if there is no other options for me...

 

How much VAS remaining when you landed the airport? Did you get the transparent glass of the terminal shown?

 

All sceneries that are enabled in scenery library will use some VAS, which leads to OOM. It doesn't matter in which area you fly. You can fly in Europe and sceneries from China will use VAS if enabled.

 

You can test it and see which settings are affecting VAS a lot. Get process explorer https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

 

You can also try this fix if you are on windows 7, i don't know about other versions: https://support.microsoft.com/en-us/kb/947246

 

Thanks for your solution.

 

FlyTampa CYYZ is the only airport at which I have experienced OOM. I flew from FSDT KLAX v2 to Flightbeam KSFO HD which are definitely the two complicated sceneries with other online traffics but no OOM. So strange,,,

 

I have tested the sceneries by Process Explorer, and noticed that 3.1 to 3.5GB VAS has been used just after I started the flight at gate and pan around the cockpit...

 

I don't get any OOM issue but my textures are limited to 1024. I have never tried with 4096.

 

May I ask you whether you can get the transparent glass and interiors of the terminals properly shown?

 

Anson

Share this post


Link to post
Share on other sites

I have it and have almost everything turned off.  I also have the lite textures installed and for whatever reason it always comes close to OOM or OOM's.  I actually think it has to do more with Orbx Canada Vector and LC than anything else, maybe try turning down the settings there and see what happens.

Share this post


Link to post
Share on other sites

I have it and have almost everything turned off.  I also have the lite textures installed and for whatever reason it always comes close to OOM or OOM's.  I actually think it has to do more with Orbx Canada Vector and LC than anything else, maybe try turning down the settings there and see what happens.

 

Nice to see somebody successfully landing at the airport.

 

I don't prefer to disable so much options just because I have paid for those nice eye-candy. It is acceptable for me to disable some of them but not all actually :Shame On You:

 

I am just using FTX Global with Vector...

 

Anson

Share this post


Link to post
Share on other sites

 

 


In addition, although I have turned "Transparent Glass and Interiors" option ON, I still can't see through the glass of terminals. Does anyone here having any idea?
If you can't see through the glass, I would turn that option off. It sounds like a real VAS eater.

Share this post


Link to post
Share on other sites

If you can't see through the glass, I would turn that option off. It sounds like a real VAS eater.

 

I would probably install lite texture pack just to reserve VAS for the transparent glass if it really works :Devil:

Share this post


Link to post
Share on other sites

With Vector and LC I got non stop OOMs at Toronto. Without them none yet. Also using Lite textures and they look fine. 

 

Dave

Share this post


Link to post
Share on other sites

With Vector and LC I got non stop OOMs at Toronto. Without them none yet. Also using Lite textures and they look fine. 

 

Dave

 

Thanks for your solution. I am also curious to know if you have turned on Transparent Glass and Interiors. If yes, do you get them properly shown?

Share this post


Link to post
Share on other sites

Might be related:  I have the FlyTampa CYUL Montreal and noticed a 500 MB hit on VAS when I flew by at cruise altitude.  I checked the scenery bgl files and found a 471 MB and an 83 MB photo scenery files, geeze. Changed the extension to .bgl.OFF and double checked in the simulator to see the visual impact and decided it looked better without.  I also have Orbx FTX Canada/Alaska openLC installed so the loss of photo scenery isn't an issue.

Share this post


Link to post
Share on other sites

Might be related:  I have the FlyTampa CYUL Montreal and noticed a 500 MB hit on VAS when I flew by at cruise altitude.  I checked the scenery bgl files and found a 471 MB and an 83 MB photo scenery files, geeze. Changed the extension to .bgl.OFF and double checked in the simulator to see the visual impact and decided it looked better without.  I also have Orbx FTX Canada/Alaska openLC installed so the loss of photo scenery isn't an issue.

 

But I am not sure which files can be deleted for CYYZ in my case...but I believe that night blending options could be a possible workaround...

Share this post


Link to post
Share on other sites

first of all, if i didn't overlook. u didn't mentioned ur simulator.i fly in & out of CYYZ couple of times with maxed setting but not with 4096 textures.lower the texture & if u using fsx i can't help & i don't think anybody here can help u with that.also vector is know to be a beast when it comes to memory.i will suggest u to disable it unless u really,really fond of what it does to add immersion to ur flying experience.
but, for p3d try these as the basics & u will be just fine:
http://www.youtube.com/watch?v=0grEYUv6bJ4

Share this post


Link to post
Share on other sites

Orbx Vector has settings that allow you to remove elements so you can save memory.  If used wisely you will not run out of memory.

Share this post


Link to post
Share on other sites

From what I heard with Vector and LC, FT YYZ + the 777, will be unflyable. Remember that YYZ itself, by default, for some unknown reason even to FT, is a very heavy area. I get about 200-300MB more by flying around Toronto default area then any other default areas (except for maybe Seattle and LA).

Also on DX10 I find that you save a bit on VAS vs DX9.

Share this post


Link to post
Share on other sites

I can get into FT Toronto in the 777 with no problems. Using the Lite textures and also FSX in DX10 (with the Fixer). I do not use any Orbx scenery.

Share this post


Link to post
Share on other sites

Yeah, without OOM, but with horrible FPS! I fly in P3D v3.3.5 and the FPS are the worst I ever had on an airport in P3D so far. 12 - 20. FlyTampa is pretty silent about the whole FPS thing and I tried all things I can imagine without success. 

 

Other FT airports:

 

EKCH Copenhagen (30 - 40 FPS)

LGAV Athens (30 - 40 FPS)

LGKR Corfu (30 - 35 FPS)

.

.

.

 

Even KSFO HD is flyable with 30 FPS for me... 

 

VAS on the other hand seems to be "fair" for this kind of airport with such details.

Share this post


Link to post
Share on other sites

    Since version 1.2, Vector has added several thousand, very accurately shaped lakes, streams, and other water bodies to Ontario/Quebec. It is these additional shorelines that cause many memory problems. Disabling the tertiary roads, small rivers/streams, shimmery bridges, and tunnels, etc, will help during a tubeliner flight. Also, disable orbx library objects, as they eat up a considerable amount of memory and are a major source of shimmering objects.

 

  Good luck,

  Jazz

Share this post


Link to post
Share on other sites

Yeah, without OOM, but with horrible FPS! I fly in P3D v3.3.5 and the FPS are the worst I ever had on an airport in P3D so far. 12 - 20. FlyTampa is pretty silent about the whole FPS thing and I tried all things I can imagine without success. 

 

Other FT airports:

 

EKCH Copenhagen (30 - 40 FPS)

LGAV Athens (30 - 40 FPS)

LGKR Corfu (30 - 35 FPS)

.

.

.

 

Even KSFO HD is flyable with 30 FPS for me... 

 

VAS on the other hand seems to be "fair" for this kind of airport with such details.

It is a very heavy FPS airport. Mostly it is not due to airport but the surrounding area. I have managed to squeeze out 25-30fps by constantly tweaking the cfg file as well as my graphics settings. Mind that, all the stuff like Mesh and and other things I have on Max. My PC is about 3-4 years old.

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