MakeRwys not scanning AFCADS

[jagman]

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

 

  

[Pete Dowson]

4 minutes ago, jagman said:

 I have found MakeRways (latest version) will not process the AFCAD if it in FS9\airport\scenery folder

It scans for AFD BGLs is any folder which is included in your operating Scenery.CFG file. It reads through the Scenery.CFG file and find BGL is all the scenery folder listed there, , and in the order listed (because that's the priority order).

So, your problem is that your "FS9\airport" folder isn't listed in the Scenery.CFG file as a scenery to be loaded. And there's no default 'airport' folder either -- you or an installer must have created that!

8 minutes ago, jagman said:

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.....

You are going the wrong way about solving such problems. Your problem is that your Scenery.CFG file is wrong. It does not reflect the scenery you want FS to load.  Sort that out, don't use bad work-arounds which don't solve the real issues.

The log file, the one called "Runways.TXT", tells youthe lines being read from Scenery.CFG, in the correct order, and how they are processed including the AFD BGLs found there.

Pete

 

[jagman]

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

            

 

            

            

[Pete Dowson]

5 hours ago, jagman said:

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....

 

Well, if this entry is in the SCENERY.CFG file:

[Area.647]
Title=LICJ Palermo
Local=Addon Scenery\LICJ Palermo\Scenery
Remote=
Active=True
Required=False
Layer=316

then MakeRunways will certainly have processed it PROVIDED that it is continuous with other layers -- i.e there are layers 1 to 315 with none missing AND sections [Area.001] to [Area.646] with none missing.

As far as I knew FS processes in the same way -- until there's a gap in numbering. Then it stops.

Perhaps you'd etter post your SCENERY.CFG file so I can check?

And was there no mention of Area 646 or 647 in the Runways.txt log file. No mention of Layers up to 316? What was the last layer processed as shown in that file?

Pete

 

[jagman]

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

 

[Pete Dowson]

19 minutes ago, jagman said:

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 ?

Both. I want to see whether FS truly does ignore gaps in numbering. All my experience says it doesn't. Let me see your file and I'll create similar types of gaps in my own file to test.

Best program I found for both renumbering your SCENERY.CFG properly and tidily, and also for moving things up and down properly too, is SceneryConfigEditor.exe. (https://sourceforge.net/projects/fs-sceditor/)

Pete

[jagman]

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

 

               

[Pete Dowson]

38 minutes ago, jagman said:

I cannot attach my scenery config to a message here........its too big.

                How do I get it to you ?

ZIP it up first -- it will be much smaller then. You can attach it to an email to petedowson@btconnect.com.

Pete

 

[jagman]

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

 

 

 

 

[Pete Dowson]

8 minutes ago, jagman said:

removed it manually............ran the editor again.......structural error gone ......it displayed the scenery layers and all OK ........no errors

Does MakeRunways scan your missing layers now?

MakeRunways uses standard Windows functions to read the file, so if there are syntax errors it will affect it.

Pete

 

[jagman]

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

 

[Pete Dowson]

Since the  addon scenery\scenery is always in the default part of the SCENERY.CFG file, naturally, with that part of your CFG file still being okay, it will always get scanned.

The problem will be discontinuities in the numbering later on. I haven't got time to look at your SCENERY.CFG file yet -- probably not till the weekend -- but meanwhile use the Scenery Congi Editor to get everything all numbered in sequence. Then try to keep it that way.

There are many other programs which would be affected by a numbering mess. I would be surprised if FS wasn't (I don't think FSX or P3D would like it) but maybe FS9 was different. I can't test that as I haven't had an FS9 installation for years. FSX is old enough (11 years now!).

Pete

 

[jagman]

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

 

[Pete Dowson]

1 hour ago, jagman said:

  I am sending you (by e-mail) the scenery config file after the config editor has (apparently) sorted it out.

No, it is a right mess still.  You evidently aren't selecting the right option. You want this one:

Actions menu -> Reset area and layer numbers and reorder the file

1 hour ago, jagman said:

right at the end of the file the paths and afcads appear which indicates to me that makerunways has detected the afcads.

Sorry, I don't know what you mean by this. If you mean the Runways.txt file, it logs all the data (and more) that it extracts from AFD files properly discovered.

Pete