If you use AFLT for an easy and perfect way to create 3D airport and approach lighting mostly you begin with ADE9 to define runway, taxiway and approach lighting.
The you use AFLT to create the nice 3D objects and purge the lights in your ADE9 BGL.
All looks fine:
But on a closer look you will see some small issues:
There are missing 3D objects (poles, bars or light heads) and strange lights instead.
What now?
I used this way:
I loaded the airport from "stock" in ADE and "saved as" with a different name.
Now I imported in this ADE the file from AFLT "AFLT_LRTM_Bases_9.bgl" and got this picture:
ADE9 did not know thes objects, so I had to use the ADE TOOL "Library Object Manager" to "ADD Folder" and save it. (I had to ignore some errors, because these GUIDs were already imported)
But then I could see the problems:
There were lights instead of bases!
To get coordinates and GUIDs was easy. Click on the wrong object to make it "active" and "right click" to show the XML code.
So I stored these XML codes of wrong objects and fine objects in a TXT file for later use.
Now I could use BGL2XML for "AFLT_LRTM_Bases_9.bgl" to get the XML Code.
Searching the wrong objects with my "lat=..........." from the TXT file was easy and replacing the GUID no problem.
Finally Xml2Bgl creates the correct "AFLT_LRTM_Bases_9.bgl"
I have no idea if the issue is in FSX, P3D also visible and would be glad if this was clear enough for the developer community-
The you use AFLT to create the nice 3D objects and purge the lights in your ADE9 BGL.
All looks fine:
But on a closer look you will see some small issues:
There are missing 3D objects (poles, bars or light heads) and strange lights instead.
What now?
I used this way:
I loaded the airport from "stock" in ADE and "saved as" with a different name.
Now I imported in this ADE the file from AFLT "AFLT_LRTM_Bases_9.bgl" and got this picture:
ADE9 did not know thes objects, so I had to use the ADE TOOL "Library Object Manager" to "ADD Folder" and save it. (I had to ignore some errors, because these GUIDs were already imported)
But then I could see the problems:
There were lights instead of bases!
To get coordinates and GUIDs was easy. Click on the wrong object to make it "active" and "right click" to show the XML code.
So I stored these XML codes of wrong objects and fine objects in a TXT file for later use.
Now I could use BGL2XML for "AFLT_LRTM_Bases_9.bgl" to get the XML Code.
Searching the wrong objects with my "lat=..........." from the TXT file was easy and replacing the GUID no problem.
Finally Xml2Bgl creates the correct "AFLT_LRTM_Bases_9.bgl"
I have no idea if the issue is in FSX, P3D also visible and would be glad if this was clear enough for the developer community-