Jump to content

Cris B.

Members
  • Posts

    359
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Cris B.

  1. Hi,

    I just make a check and I think the need time to check also the default directory is not so critical, so in 1.94, AES will also search for the Addons below <FS>Scenery, even when I prefer not to install scenery there.

    That was quick! :shock:

    Thanks again! :)

  2. Hi,

    the problem is, that AES will ignore every Path, where the beginning is <FS>SCENERY.

    I do that, because below you have a long list of FS internal and default Scenery entries, which never includes any AES related files, like ..SCENERYWORLD and so on.

    As AEShelp needs to read and check all this entries every time, I think it makes no sence to check them every run and to hold a installation clean, it is not a good choise to place Addons in a MS default directory path.

    But I will check, how many time we lost to check all this directories too.

    Oliver,

    Thanks for the reply and explaination of how AES works has helped me greatly.

    Again thank you for such a great product and all the work you put into it!

  3. Hi Oliver,

    I am trying to get the airports, that you have shown us, installed and working but I have hit a small snag. For 1.93 you had us move some of the ISD Project scenery from the FS9/scenery folder to the FS9/addon scenery folder so AES could find it. I have noticed in the install instructions of LIME, LIPR, VHHH, and LGAV that each of their designers indicates they should be placed in the FS9/Scenery folder. Now I realize that it does not matter what folder the scenery goes into as long as it is properly registered in the scenery library. But it leads to my question. In what folder will AES 1.94 be looking, to find these scenery? :?:

    bump

  4. Hi Oliver,

    I am trying to get the airports, that you have shown us, installed and working but I have hit a small snag. For 1.93 you had us move some of the ISD Project scenery from the FS9/scenery folder to the FS9/addon scenery folder so AES could find it. I have noticed in the install instructions of LIME, LIPR, VHHH, and LGAV that each of their designers indicates they should be placed in the FS9/Scenery folder. Now I realize that it does not matter what folder the scenery goes into as long as it is properly registered in the scenery library. But it leads to my question. In what folder will AES 1.94 be looking, to find these scenery? :?:

  5. Make a copy of all of your Mytraffic BGLs and place in a temp folder.

    Then rename them by putting the word "traffic" in front of the file name, (this is so the Traffic tool can read them)

    Follow the traffic tool instructions and search for VHHH and change them to VHHX then recompile.

    Change the changed file names back to the original names.

    Make backups of the original BGLs and store in a safe place.

    Then overwrite with your new files.

    Kai Tak is so close to VHHH that FS9 and Mytraffic make the transition without any problems!

    If you want to use FSBuild to make flight plans you will have to change the Airport and Runway text.

    You will find Kai Tak under its original ICAO of VHKG.

  6. This is the best Kai Tak Airport (VHKG), or as it is known in SF9 (VHHX) that I have ever seen for any flight sim. I broke out my old approach charts and started "chasing the the rabbit" again! This is payware quality!

    I'll keep my fingers crossed and hope Oliver will put his special touch on this one!

  7. Hi Dash8,

    I know that UUDD Domodedovo (Moscow) has parking stands that an aircraft has to be pushed into!

    The airport can be found at www.IGfly.com and AES works on it!

  8. I'm trying to complete my scenery in Germany in FS9. I have most if not all of the German airports sold by Aerosoft and several asked if any of the Scenery Germany series was installed. At the time I installed the airports I did not. My question is, if I want to install the Scenery Germany Series now, will I have to do anything out of the ordenary or will the installers take care of everything for me?

    • Upvote 2
  9. Just a thought, take a look in the aircraft.cfg and check the parking spot and parking spots entrys for that airline livery.

    It's possible that a wrong airline assignment may be there.

    i.e.: see bottom in red.

    [fltsim.15]

    title=747-400 KLM

    sim=B747-400

    model=GE

    panel=

    sound=

    Texture=KL

    kb_checklists=PMDG747-400_CHECK

    atc_id_color=0xffffffff

    atc_id=PH-BFL

    atc_airline=KLM

    atc_flight_number=744

    ui_manufacturer=Boeing-PMDG

    ui_type=747-400 GE-CF6 Engines

    ui_variation=KLM

    description=Boeing 747-400 with GE-CF6 engines v 1.0nPrecision Manuals Development Groupnwww.precisionmanuals.com nFor use with BOEING 747 by PMDG nFor Technical Support please visit www.precisionmanuals.com or email support@precisionmanuals.com n

    visual_damage=0

    atc_heavy=1

    atc_parking_types=GATE

    atc_parking_code = 1

    atc_parking_codes=KLM

  10. It is SO ironic that what Mathijs is preaching here, is tolerance...and it's the very thing that Snave violates all the time for others.

    But trust me, everyone here knows the score when it comes to our resident source for entertainment...it is humorous indeed to watch him dig a hole for himself, then try and tunnel out through a completely different path than he arrived!

    Oh, and as far as breaking out the thesaurus, I would instead recommend a dictionary for you Snave...for the word isn't "peurile" but rather "puerile". ;)

    I must concur with you, Ripmaster, Snave can be brash and down right rude at times but as Mathjis states, Snave can make some good points. Most of the time, though, I see Snave as a form of "comic relief".

    I'm sorry if this hurts your feelings Snave but I just call'em as I see'em! :wink:

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use