Or just leave everything alone because except for photoscenery none of this does anything really.

Exactly my experience which I also said a couple of posts back

I think some of the FTX/Orbx scenery has photoscenery. I know PNW Seattle is photoscenery anyway. I ran Process Monitor in a flight from Chicago to St Louis some time back and saw that Orbx scenery was being processed even though it was not loaded in the PNW. Turned out to be Orbx .bgl's in the Scenery/World/Scenery folder (Autogen). I never did enable the FTX utility to see if the PNW scenery would load even though I was located in Chicago.

 

Best regards,

Using Simstarter I keep it simple, just  2 profiles, 1 No photo and normal settings and 2 Just photo and the best settings for it..easy

I've got over 300 sceneries, that's a lot of sceneries to untick!

 

 

Lee

Yeah, I know what you mean. I have 326 entries in mine and it was a lot to untick the first time. After I did it once it was done for good. Now I only have to tick and untick a few every time I fly.

 

I have my scenery library arranged strating from west to east, west starting on the west coast of the US and east ending in Australia/Asia. Since its arranged in this order it makes finding stuff easy to tick and untick.

Jim is right, never touch the FTX sceneries manually. You can set simstarter to leave them alone and only manage them via their own control panel.

 

Lee

What problems are caused if FTX scenery is manually enabled and disabled in the Scenery Menu? How would I disable some FTX airfields when FTX Central only seems to let me activate or deactivate regions?

With FTX it is all-or-nothing. Disabling any airfields is going to even do less of nothing than disabling regions.. Hard to think that people believe that they are doing something good here, except in the case of photoscenery.

I found after disabling some complex add on airports such as Flytampa, FSDT, and others I had to uninstall and reinstall the airports. After enabling I would have terminals missing and sometimes blacked out areas. I now only uncheck the photo areas I won't use and leave everything else alone. 

That shouldn't be happening, it makes no sense.

 

Lee

I found after disabling some complex add on airports such as Flytampa, FSDT, and others I had to uninstall and reinstall the airports. After enabling I would have terminals missing and sometimes blacked out areas. I now only uncheck the photo areas I won't use and leave everything else alone.

That's impossible to happen to FlyTampa sceneries just by enabling or disabling, however there is a reason it happens with Flightbeam and FSDT sceneries.

 

It has been documented by Umberto at the FSDT forum that if you disable an FSDT or Flightbeam scenery do a flight then exit FSX. Then upon starting FSX you enable the scenery and start a flight that you will get the missing buildings. What you have to do for FSDT or Flightbeam sceneries after you re-enable them is to quit FSX and then start FSX again. Once you do that the sceneries you re-enable will be active again and the buildings will show as they should.

 

Too bad you spent all that time uninstalling and reinstalling when a simple restart of FSX would have solved it, but at least now you know the procedures.

Or just leave everything alone because except for photoscenery none of this does anything really.

I agree with Jim as photoscenery is really the only VAS killer since it loads everywhere regardless of you position in the sim, which has also been verified. Most airports usually load and unload around 10nm from either entering or exiting their vicinity. The only time disabling a lot of sceneries might help is if they are all in close proximity of each other, like in the NYC area.

 

 

I found after disabling some complex add on airports such as Flytampa, FSDT, and others I had to uninstall and reinstall the airports. After enabling I would have terminals missing and sometimes blacked out areas.

 

Ah so that's why after I landed at KIAD the terminals were missing. I reinstalled and they reappeared. I won't make the mistake of deactivating scenery layers again in a forlorn attempt to increase VAS. As Jim and others have rightly pointed out doing this makes absolutely no difference expect where photo-realistic scenery is involved.

Time for some more experiments. I will only activate and deactivate photoscenery regions during my test flights, and see if there is any difference compared to how I have been doing it before. Just to be clear......I can have all of my FTX EU scenery and airfields, plus every other airport and airfield package enabled in the Scenery Menu, and it will not make any difference whatsoever to VAS (when compared to switching them off)? I have been activating all of the scenery packages that are relevant to each area that I have been flying in.

I can have all of my FTX EU scenery and airfields, plus every other airport and airfield package enabled in the Scenery Menu, and it will not make any difference whatsoever to VAS (when compared to switching them off)?

That has been my experience in the past, VAS usage difference with scenery enabled/disabled has been marginal at best as long as no photo scenery is involved.

The issue I had with the FlyTampa (kbos kmdw kbuf) was large  dark areas would appear near the ends of runways. I had to reinstall to get rid of them. In retrospect this may have been because I had them installed on an external SSD. That external seems to work for photo real but not airports. I put those back on my C drive. These areas where large vertical black areas that reminded me of the ape man scene in 2001 Space Odyssey. Come to think of it, if I stared at them I got this strange urge to grab a club, jump up and down and beat the ground.