Okay this might sound strange. But i was getting OOM a few days ago , and for some reason MTX Scenery bgl file was causing OOM.When i rename MTX scenery bgl file the OOM stop.

Okay this might sound strange. But i was getting OOM a few days ago , and for some reason MTX Scenery bgl file was causing OOM.When i rename MTX scenery bgl file the OOM stop.

 

It doesn't seem strange at all, by removing your AI traffic you reduced the vas load. It doesn't mean that the MTX bgl was the cause though.

Just did 5 test saved flights from LAM3A inbound LAM FL090 on a LAM transition to RWY27R.

 

Just to test if i had missed something from memory.

 

Daytime at 1200Z ASN date 310116

 

 

RWY27R facing taxing to facing east at A10E (tower on your right side) 

 

With UTX2.1 roads and UTX lights

 

1. test 3.446GB

2. test 3.417GB

 

 

With UTX roads but WITHOUT UTX lights

 

1.test 3.268GB (saving around 180MB)

2.test 3.227GB (saving around 190MB)

 

WITHOUT UTX2.1

 

1.Test 3.043GB (saving around 400MB)

 

 

So a massive different in this location. Cant recall seeing this amount before but for now i will only use roads without lights(daytime) :-)

 

 

Michael Moe

 

 

I did a test number 6 at night from LAM3A just to see if its possible to use UTX lights WITHOUT roads . :wink:  But not possible.

 

With ASN Cloud layers at 5 and enhanced overcast it was at 3.0GB and FPS 25-35fps at RWY 27R EGLL  .

 

Michael Moe

It doesn't seem strange at all, by removing your AI traffic you reduced the vas load. It doesn't mean that the MTX bgl was the cause though.

I think for me it was. Because i kept getting OOM at payware such as FSDT-KLAX - the runway won't show and upon landing OOM. So when i search  in the MTX Scenery Folder i saw KLAX.bgl, as i turn it off i could then see the runway at KLAX and the OOM stop. I didn't reduce the amount of traffic , all i did was rename the KLAX bgl. When i realize it might be MTX that was causing the problem , was when i got the same OOM at KJFK , i fallowed the same steps as i did for  KLAX , by renaming MTX Scenery KJFK.bgl. It also solve the problem.

Generally, having more than one version of an addon airport is going to cause problems. The stock airports in the sim don't count in that regard because addon airports use exclusions to block the display of conflicting items from the stock airport.

 

But if one has a MyT 6 airport and a 3rd version of that same airport, the exclusion approach obviously won't work. The author of MyT 6 recommends renaming his duplicates in order to make the additional 3rd party version display correctly.

 

In most cases, the MyT 6 version only adds additional gates to accommodate enhanced AI traffic. Any payware airport is going to do the same thing.

Generally, having more than one version of an addon airport is going to cause problems. The stock airports in the sim don't count in that regard because addon airports use exclusions to block the display of conflicting items from the stock airport.

 

But if one has a MyT 6 airport and a 3rd version of that same airport, the exclusion approach obviously won't work. The author of MyT 6 recommends renaming his duplicates in order to make the additional 3rd party version display correctly.

 

In most cases, the MyT 6 version only adds additional gates to accommodate enhanced AI traffic. Any payware airport is going to do the same thing.

 

For that reason I have disabled all MTX airport files. Put them in a OFF Folder and just left those files which are needed for traffic.

I think for me it was. Because i kept getting OOM at payware such as FSDT-KLAX - the runway won't show and upon landing OOM. So when i search  in the MTX Scenery Folder i saw KLAX.bgl, as i turn it off i could then see the runway at KLAX and the OOM stop. I didn't reduce the amount of traffic , all i did was rename the KLAX bgl. When i realize it might be MTX that was causing the problem , was when i got the same OOM at KJFK , i fallowed the same steps as i did for  KLAX , by renaming MTX Scenery KJFK.bgl. It also solve the problem.

 That's not finding a cause though at all. As jabloomf1230 mentioned above it seems that that your sim is rather messed up with various airport files all running at once causing issues, not MyTraffic.

 That's not finding a cause though at all. As jabloomf1230 mentioned above it seems that that your sim is rather messed up with various airport files all running at once causing issues, not MyTraffic.

Thank you , i will have to recheck and see. But for some reason the OOM stop. I didn't make any changes to my graphic setting. I just completed  a 10 hour flight and landed at KLAX no OOM. But if something was messed up in my Sim it appears to be fix so far.  I'm not saying MTX is entirely to blame, but for some reason my problem stop.