Jump to content
The simFlight Network Forums

jagman

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by jagman

  1. Hi Pete I am sending you (by e-mail) the scenery config file after the config editor has (apparently) sorted it out. I ran the RC scenery DB rebuild again on this fileand then had a look at Runways text. right at the end of the file the paths and afcads appear which indicates to me that makerunways has detected the afcads. However there is no detailed airport data......similar to that for the default airports. What this means I have no idea..........over to you. I look forward to hearing from you in due course Regards David
  2. No ...... I'm afraid not Just as a matter of interest.......I noticed in Runways.txt there was no detailed info from the AFCAD of another airport I installed a while back ......LGKR. The AFCAD was in the FS9\addon scenery\LGKR\scenery directory........ I shifted the AFCAD to FS9\addon scenery\scenery as per my (unauthorised,unnofficial !),workaround......fired up FS to check the AFcad was found....... it was I ran the RC Scenery DB rebuild again and checked Runways.txt.......... MakeRunways had scanned the (shifted) AFCAD and the airport details were all present. Hmmmmmm ! Regards David
  3. Will do...... I've just run the scenery config editor which discovered a "structural error".......in the very first entry in the scenery.config .as per----- [General] Title=FS9 World Scenery Description=FS9 Scenery Data Clean_on_Exit=False [ the editor did not like this apparantly spurious bracket. I removed it manually............ran the editor again.......structural error gone ......it displayed the scenery layers and all OK ........no errors I will send you my config file with the glitch removed......... Regards David
  4. Hi Pete I cannot attach my scenery config to a message here........its too big. How do I get it to you ? I have downloaded the scenery config editor.......thanks for that..... Regards David
  5. Hi Pete Sorry for the delay gettihg back to you.......I have had a weekend away. My scenery config Areas have numbering gaps all over the place ......and some area numbers out of sequence..... Do you still want to see it ?........or can I fix it mtself somehow ? Regards David
  6. Hi Pete Thanks for the fast reply,but I am bemused by your assertion that my scenery.config is "wrong" All added airports worked fine and makerunways always did its stuff for RC4...untill I added the first ISD airport.......LIRF. With help from RC support we discovered (by examining Runways.txt) that the addon airport was not being recognised by makerunways......only the default airport was being recorded for RC4. The AFCAD for LIRF was in the LIRF\scenery folder....... I discovered the workaround by accident.......it may be the wrong way of going about things.... but it works !....every time .....untill LICJ which has a display problem as above. LICJ a very old scenery which uses an irregular AFCAD file (LICJ_FB_G.bgl) which I renamed AF2_LICJ_FB.bgl (so I could recognise it) :- This is my Scenery.config entry for LICJ Palermo......... [Area.647] Title=LICJ Palermo Local=Addon Scenery\LICJ Palermo\Scenery Remote= Active=True Required=False Layer=316 Does this data seem "wrong" ? Regards David
  7. hello Pete Lately been installing freeware Italy airports by ISD and others into FS9\addon scenery I have found MakeRways (latest version) will not process the AFCAD if it in FS9\airport\scenery folder I have got around this (so I can use RC4) by shifting the AFCAD into FS9\addon scenery\scenery....... but I have found an airport (LICJ by F Baratti) which will not display properly unless the airport file is in the fs9\addon scenery\LICJ Palermo\scenery folder so the workaround cannot be used in this case..... Any help appreciated David Ireland
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.