I am posting this in the FSX forum, because I am not sure what the work around will be.

 

This is the issue at hand;

 

1. click on "Scenery Config Editor" select airport "A".

 

2. click on FSX.exe and select airport "A".

 

3. airport "A" has no AES support.

 

4. click on AEShelp.exe. AES sees airport "A" and asks to "Activate" it.

 

5. activate airport "A" in AES. AES says activation will take on next FSX startup.

 

6. close AES and FSX.

 

7. click on FSX and select airport "A", now have AES support for airport "A".

 

8. finish flying FSX and close program.

 

9. click on "Scenery Config Editor" deselect airport "A".

 

10. in "Scenery Config Editor" select airport "B".

 

See where this is going? opening AES prior to opening FSX will not help. You have to open FSX,  open AES, let AES activate airport "B" and so on and so on. Anyone have a solution for this "Dog and Pony Show"?

 

Why are you clicking on the scenery in FSX? If you are using the airport editor you shouldn't have to go into FSX to change anything.

Why are you clicking on the scenery in FSX? If you are using the airport editor you shouldn't have to go into FSX to change anything.

 

Who said I was clicking on scenery in FSX? I said "select" airport.

You select airport "A"  and "B"in SCE, save. Run FSX, to build scenery cfg, close FSX, run AES config tool click prompts, run fsx and fly. There is no other way, as AES reads the scenery cfg, and your scenery entries are not updated till you run fsx after editing SCE.

I keep a back up of my complete scereny list as scenerydefaultall.cfg

 

Once the airports are active in AES just leave AES at the top of your scenery.cfg no matter what edited cfg you are using.

 

You only need to open aeshelp once to activate a scenery. Just make sure your scenerydefaultall.cfg is your active scenery.cfg when doing so. If AES sees missing scenety entries it will deactivate them.

I keep a back up of my complete scereny list as scenerydefaultall.cfg

 

Once the airports are active in AES just leave AES at the top of your scenery.cfg no matter what edited cfg you are using.

 

You only need to open aeshelp once to activate a scenery. Just make sure your scenerydefaultall.cfg is your active scenery.cfg when doing so. If AES sees missing scenety entries it will deactivate them.

 

What a mess, thanks, I was afraid of that.

 

You select airport "A"  and "B"in SCE, save. Run FSX, to build scenery cfg, close FSX, run AES config tool click prompts, run fsx and fly. There is no other way, as AES reads the scenery cfg, and your scenery entries are not updated till you run fsx after editing SCE.

 

That is what I have been doing and it is tedious. Ever feel like we have become a slave to our hobby?   :Worried:

Have to agree Ric. been doing it for so long now, I do it without knowing I am doing it. Starting fsx just for a quick flight is a bit of a joke. On the plus side, it keeps OOM's in check.

I do not understand what the problem is here (I am not the brightest so I could be missing something).

 

I almost never run AES help unless I am adding new credits or configuring a new aircraft. And, as I said when I do run AES help I make sure my scenerydefaultALL.cfg is loaded before doing so. I rarely run it or see a need to.

 

I leave AES active at the top of my scenery.cfg no matter what route I am flying.

 

So I do not understand why you guys are needing to open AES help before you fly?

 

Been usind SCE and AES for a while now and have zero issues.

 

You might also want to save different sceney.cfg entries for routes you fly. For example scenerykjfkkord.cfg

 

Then when you want to fly that route (KJFK - KORD) you can manually rename it to scenery.cfg and drop it in the FSX folder overwriting your scenery.cfg and start FSX.

 

It is that easy, not to mention you can do the same thing with the backed up scenerydefaultall.cfg too before you run AES help.

 

Or am I missing something here?

Who said I was clicking on scenery in FSX? I said "select" airport.

I read it wrong. Sorry.