Hi guys,
  For those of you who bought the new Mexico City scenery, is there an option to turn off all of the photo areas around the outside of the Airport perimeter? LatinVFR have this option in there installers (KMIA v2, KSAN). I choose not to use the Photo real stuff because I like how FTX Global fills in around the airport and it looks more uniform if you know what I mean?

Cheers

I just bought it and installed it and there is no option to turn if off.

 

However, you can manually disable the photo real and the autogen that comes with it.

 

The way the airport and the scenery installs is in 3 different folders in your Addon Scenery/MMMX-T2G folder. Followed by the 2 folders.

 

MMMX - which contains the airport bgls and textures

MMMX - city  - which contains the buildings and textures for the city

MMMX - terrain  - which contains all the photo real and custom autogen

 

All three of these folders are added to your scenery.cfg. You could probably try  turning off the MMMX - terrain folder/entry in the scenery.cfg to exclude it.

 

Should you delete the folder and eliminate the entry from the scenery.cfg, remember to use a scenery.cfg editor to renumber the scenery.cfg entry numbers as you will now have a blank and missing entry in the .cfg.

 

I have not tried this and doing so could have consequences or not in the way the airport displays if the included flattens and exclusions depend on the photo real being installed. But it would be easy and painless to test.

 

Right now, I am busy paring down the airport textures to 1024 DXT5 format as it includes numerous 2048 sized textures in 32bit format which are known FPS and VAS killers.

 

It amazes me to this day how some developers publish these sceneries using 32bit 2048+ sized textures then wonder why people complain about OOMS and FPS issues. Thats the reason I always check the texture folder when I install a new airport before I even load FSX and try it out.

 

I've read a few people complain about OOMS here, not many though, but pushing 12 2048 32bit textures will surely add a lot to the over head in the VAS department. Add that to the T7 or complex a/c, lots of autogen, AI, and it can be putting you close to OOM territory.

Ok man, I'm gonna buy it and try out your reply, its just I use the T7 and the NGX only and I get pretty close to the VAS limit and I'm sure turning off a lot of that stuff would help.

Thanks for the reply, very detailed!

 

 

 

Ok man, I'm gonna buy it and try out your reply, its just I use the T7 and the NGX only and I get pretty close to the VAS limit and I'm sure turning off a lot of that stuff would help.

Thanks for the reply, very detailed!

 

You could also turn off the MMMX - city folder which contains the buildings the city if you are not using the photoreal. By leaving that folder enabled while disabling the photoreal might cause some weird building placements with FTXG since those building are aligned to proper locations to fit the photoreal. You might otherwise get some buildings overlapping default city buildings.

 

You said you get pretty close to VAS limits normally, then this airport might put you over the edge considering it is full of 32bit textures and 2048 size. I have spent the last few hours converting the 32bit ones to DXT5 and resizing them to 1024. You can't really tell much difference but the VAS savings is huge. Its a time consuming process though and I can't believe a developer included as many 32bit textures as they did knowing the effect they can have in the sim.

How about shifting the photo bgl's to a newly created scenery folder and adding that one in a separate entry to the scenery library?

 

That way you can activate/deactivate the photoscenery from within FSX, depending on the type of aircraft you fly.

 

 

How about shifting the photo bgl's to a newly created scenery folder and adding that one in a separate entry to the scenery library?
 
That way you can activate/deactivate the photoscenery from within FSX, depending on the type of aircraft you fly.

 

They are already in their own scenery folder as I mentioned in my post above, so you can simply uncheck then in the scenery library.

 

As I mentioned there are three folders added to your scenery.cfg as listed below:

 

MMMX - which contains the airport bgls and textures

MMMX - city  - which contains the buildings and textures for the city

MMMX - terrain  - which contains all the photo real and custom autogen

 

If you want, you can simply uncheck the MMMX - city folder and the MMMX - terrain folder. The "city" folder just holds all the custom city buildings, but if you uncheck only the "terrain" folder which houses the photoreal and leave the "city" folder checked, then you will probably have building placed over whatever GEX or FTXG places there and will look weird when flying over it.

Do you think id save much VAS by just disabling the city, autogen and photo real areas? I wanna fly to mmmx from sfo lax mia and dfw....all if which I have high quality pay ware scenery

Do you think id save much VAS by just disabling the city, autogen and photo real areas? I wanna fly to mmmx from sfo lax mia and dfw....all if which I have high quality pay ware scenery

 

 

Yep, I think so. But why don't you disable the (photo)scenery you're NOT flying over instead? It helps with VAS, as well!

On my rig with the majority of the 32bit textures converted to DXT5, and having resized most of the 2048's to 1024, but with the photoscenery and city enabled, sitting on the gate with UT2 at 70% airline and some other WOAI cargo packages (lot of traffic at this airport at this level), and the T7 loaded and ready to go I am only sitting at ~2.7 of the memory consumed. That still leaves a comfortable 1.1 of VAS available, although I dont think that even with more traffic I could get near 3.8GB of memory consumed, so I still have a pretty safe margin to go.

 

Overall this is a pretty well done package. Still cant believe they included a boat load of 32bit textures. No one does this anymore, not FlyTampa, FSDT, or Flightbeam. I have no idea what they were thinking.