Double Runways

[unc1rlm]

I have been trying to pin this down... I have UTLive disabled..I have completely reinstalled p3dv4.3. The only scenery is KCLT and GSX with one add-on plane Aerosoft A318/319 Pro (new-just released). I do use FSAerodata.
Default KCLT in p3dv4.3  has runways 18L;18R;36L;36R; 23;5.....After FSAerodata enabled with Navigraph, default now show all the previous and I believe 18C and 36C.  I think this is all correct.

I install Chaseplane and I have talked to the developer and he says that all Chaseplane reads are the BGL's. I am adding pictures of Chaseplane and its runways at Charlotte BEFORE I add FSdreamteam and after. The runways to the right in the list (not showing because you have to scroll with mouse is 23; 5.

Pictures are: Analayze 1 is before FSDT KCLT
                    Analyze 2 is after FSDT KCLT

I ran Airport Scanner and it didn't find any duplicates but it shows whats in the KCLT folder..... I am not a computer whiz...just kinda scratching the head on how to fix (if at all) this runway error....I wouldn't know how to edit BGL or anything else and Keven at Chaseplane is scratching his head too...

I got this back this am from Herve at http://aerosors.freeforums.net: Maybe you understand it better

No..Don't My updates are NOT compatible with FsAerodata
AFAIK, FSDT is a scenery addon that will have a higher priority than default stock files and will inactivate them so any update of stock files will be ineffective
Know the updates I propose only change DEFAULT SIM scenery files (APX26190 is one of those containing KCLT)
They are primarily intended to users not having any 3rd party addon for the airports as initially defined in the default sim sceneries
In case you have problems with either FsAeroData and/or FSDT rendering, please ask them (both have dedicated forums)

Regards

Hervé

Not pointing fingers but just to try and figure it out.
 I found this post this morning and i am not sure that the afcad is wrong     APX26190
https://www.avsim.com/forums/topic/521423-kclt-rw36l-missing/

Thanks,
Bob M.

[virtuali]

I'm not sure what you are asking here. It seems your issues is that some 3rd party utility don't see the correct runways that we surely DO have in KCLT ? If yes, how this could possibly be an FSDT problem ?

- Is FSDT KCLT installed on an higher layer than every other scenery that *might* conflict with it, which includes the FSAerodata files ?

- Are ALL your 3rd party utilities fully compatible with P3D4 add-on.xml method to install sceneries ? We use it for KCLT but, if some of your utilities aren't (Chaseplane, FSAerodata, Simple Airport Scanner), they won't see sceneries installed that way, so they might give confusing results.

[unc1rlm]

Umberto... I have written Chaseplane about the situation...In the picture https://imgur.com/aQJ9c0f... which I click on one of the three 18's it does go to a correct runway 18L/18C/18R and same with 36's ; 36L/36R/36C so I believe there is no issue with you. I didn't discover this till this morning when I decided to click on each one and see what runway i was looking at.

Chaseplane says it only reads BGL's...so anyway..maybe I'll get it resolved. I can't image I am the only one in the world with FSDT KCLT and Chaseplane (which is a great program) with this problem.).. The order of my libraries is: https://imgur.com/quGygi6.... I have Charlotte near the top above FSAerodata..... I know that FSDT KCLT uses the xml addon method so my question is when a addon is added is it suppose to read an xml to get the scenery info?  Maybe Chaseplane is not reading the xml correctly if that is the case?

Well enough of this.. I am very happy with FSDT KCLT...its just the other stuff causing me to pull out my hair.

As a sideline: I just got this back from Jose at FSAerodata just for your peruse:

Hi Bob, thank for your patient and time spent,

I run some tests with MakeRunways and FSAD, default KCLT and a freeware add-on of KCLT available at Avsim library, and below are the results:

1) Prepar3D + FSAD
Airport KCLT :N35:12:50.4200 W080:56:35.2502 748ft
Runway 18C/36C centre: N35:12:49.2862 W080:57:07.1794 748ft
Runway 18L/36R centre: N35:12:46.2087 W080:56:06.5093 748ft
Runway 5 /23 centre: N35:12:56.8016 W080:56:25.9805 748ft

2) Prepar3D + FSAD + Addon KLCT 2018 (3 runways - Avsim Library)
(the priority on scenery list Add-on vs FSAD is not relevant in terms of runways)
Airport KCLT :N35:12:50.4200 W080:56:35.2502 748ft
Runway 18L/36R centre: N35:12:46.2087 W080:56:06.5093 748ft
Runway 18R/36L centre: N35:12:46.6622 W080:57:58.9320 748ft
Runway 18C/36C centre: N35:12:49.2862 W080:57:07.1794 748ft
Runway 5 /23 centre: N35:12:56.8340 W080:56:26.0659 748ft

As you can see, FSAD updates correctly the default airport; when using an add-on, the new runways config is updated correctly.
I don't see any error, either using FSAD standalone or together with airport add-on.

These values are taken from last KCLT runways entries listed on runways.txt or similar file that includes runways, as an output of Makerunways.
As a conclusion, taking the latest KCLT entries from Makerunways files, they should match the active airport runways.

I'm afraid I cannot be of much help at this point,
Any comments, let me know

Anyway THANKS UMBERTO!!!!
Bob M.

[virtuali]

I know that FSDT KCLT uses the xml addon method so my question is when a addon is added is it suppose to read an xml to get the scenery info?  Maybe Chaseplane is not reading the xml correctly if that is the case?

That's one of the two possible issues I listed in my previous reply. Of course, I cannot possibly know how Chaseplane works so, again, it's best if you ask them.

There's only ONE thing sure:

FSDT KCLT HAS all the correct runways in place, they DO work in the sim and, whatever issue your 3rd party utilities have to deal with them, it's nothing that has anything to do with our scenery, which use a 100% standard AFCAD, and it's installed using what is, according to the P3D4 SDK, is the only proper way to install a scenery, which is the add-on.xml method.

[unc1rlm]

Thanks Umberto.....
Bob M.