FSXA How Do I Save My AFLT Project

[kmanning]

H Don, or any experience user of AFLT,

I've been trying to figure out how to save my project, staying up all hours of the night trying to figure this out. Yes, I know there's a menu that says "Save Placement Data" and Save Placement Data As." I've done that everytime before closing AFLT. When I click "Save Placement Data," it does save my project, and as an xml. So, I close AFLT. Every time I come back to finish where I left off and open AFLT, it doesn't load my saved data that I've saved. It appears to only load the airport reference file, which I guess is what it's supposed to do. But what do I have to do to load my saved data so that I don't have to go back and start all over again?

Ken.

 

[GaryGB]

Use the AFLT "Save Placement Data As" option in that dialog box.

Do not re-use the proposed existing filename that AFLT may otherwise intend to output; instead use a modified version of AFLT's proposed filename.

Be certain to enter a modified name with pertinent info and a date in the name of the output file.

Also be certain to use no blank spaces; so for example, the output filename should use underscore (underline) characters as spaces but not blanks.


Always save a ZIP of any / all files that (even potentially) 'may' be over-written before AFLT is allowed to over-write it with an updated output file.


Don was thorough in researching how airfield lights look- and are placed- in real world airfields.


If AFLT output of both custom light types is FPS-limited via FS2Kx SDK for custom replacement lights, perhaps we can still use AFLT's data in other ways.


Don asserts AFLT makes AFD-type airfield light positioning closer in appearance to IRL.

You can extract his XML for light placement, and use it with FSX default XML code for built-in AFD lights to otherwise still use FSX' default AFD-type airfield lights.

In other words, you can use AFLT to generate improved placement coordinates that are substituted to place FSX' KBHM AFD-type airfield lights.


After you successfully master saving your AFLT project data, you can make use of the XML code that it outputs as source data to modify KBHM's lights.

Ultimately, the edited XML source code can be used to make modified versions of KBHM airfield lights that have for example, merely been re-positioned.


NOTE: In most cases, airfield lights are pre-programmed objects associated with other AFD-type infrastructure objects that have fixed parameters.

Thus, wirhout ADLT, one may not be able to edit most parameters for AFD-type lights, as they are simply toggled ON / OFF as associated features of other objects.


Don does not go into details as to which attributes are different in the lights created by AFLT; he merely asserts they may be more true to IRL lights.

Since FAA criteria do not vary much- if at all- throughout world wide airports, AFAIK, not many airports have custom lighting that does not follow FAA lighting criteria.


FAA Taxiway Edge Light criteria info is here:

https://www.google.com/search?q=FAA...wgcJMS4xMC4yMS4xyAd2gAgA&sclient=gws-wiz-serp

https://www.faa.gov/documentLibrary/media/Advisory_Circular/150-5340-30J.pdf

https://www.faa.gov/Air_traffic/publications/atpubs/aim_html/chap2_section_1.html


So, I do not know that much needs to be- or should be- made custom for airfield lighting that can not be dealt with by ADE, AFX, FSXPlanner etc.


As AFLT custom lights seriously impact FPS , it may be best to use it as an editor GUI, then use AFLT's XML to update a custom airport's XML.

IIUC, that way we may use default AFD-type lights and avoid the FPS issues.


AFAIK, the FS2Kx AFD lights are built into either the FSX executable- or another DLL- as optimized objects that render with high priority and high FPS at run time.

So, if you dislike ADE's GUI to edit airfield lights, then AFLT can be used to edit those lights and generate XML to be integrated with KBHM's default XML.


At some point that may involve manual editing of XML code elements within a text editor like NotePad++.

Otherwise, you may need to find another airport editor with a GUI which you like.


It may be that the issues which you most want to change, are best dealt with by Don's other utility - Apron Edge Lights Processor:

https://www.fsdeveloper.com/downloads/49296-Apron_Edge_Lights_Processor.zip


"Apron Edge Light Processor

**************************

Apron Edge Light Processor is a small utility developed for my own use that will adjust the color, brightness and spacing of apron-edge lights in a FS9 or FSX airport file (.bgl).

Start execution of Apron Edge Light Processor, specify the path to the airport file and set the desired values for the other parameters.

When ready, click the Go button. The selected airport file will be updated. No backup file is made so you may wish to back up the airport file before modifying it."


IIUC, Don refers to your custom KBHM airport BGL and/or XML for the build you wish to modify.

So, that 'should' be the file for both input- and output (after making a ZIP backup)- by Apron Edge Light Processor.



But, before abandoning ADE's GUI AFD-type light editing features, I would recommend first to review the ADEv165 PDF Manual in detail:

http://download843.mediafire.com/x6...lxti9A/8rp6jr7en9xwdls/manual_english_165.zip


PS: I have attached a ZIP of the XML code for FSX' default KBHM; it does not include any potentially required default APX2420.bgl- or OBX2420.bgl- scenery library object placements.

You may wish to review that default airport XML, to see how KBHM is actually coded as source data (...and which is able to be compiled by SDK BGLComp.exe).


It was extracted from its default source multiple airport BGL via Windows NotePad from:

[FSX_install_path]\Scenery\World\Scenery\0302\Scenery\APX2420.bgl

...using scruffyduck's BGL2XMLGUIv110:

http://www.mediafire.com/file/c35bxkqe2ngn5u2/Bgl2XmlGui.zip/file

GaryGB

 

[tgibson]

Have you confirmed that the file you told AFLT to save is actually present?

 

[kmanning]

Have you confirmed that the file you told AFLT to save is actually present?

Yes. It's in the AFLT Project\KBHM folder. It includes the Placement.xml that I've just saved, project.ini, and the StockData.xml files.

Ken.

 

[kmanning]

Hi Gary and Tom,

Here's what I've found out so far. When I open my ADE stock taxiway lights in AFLT, I can drag the taxiway lights and move them where I want. But AFLT does not save those changes when I re-open AFLT, even though I've clicked the "Save Placement Data." But when I open my ADE stock without the taxiway lights in AFLT and add the taxiway lights myself from scratch and place them where I want, AFLT saved those changes after opening AFLT again. I also tried dragging and moving a couple of lights to another location and AFLT saved those changes after closing and re-opening AFLT. So, as far as saving the placement data, it works only when I add the new taxiway lights myself from scratch. According to a google search, one can edit an ADE stock taxiway lights in AFLT and ALFT will save those changes. But that has not been the case and I also know that many times, google searches are wrong.

Ken.

 

[kmanning]

Use the AFLT "Save Placement Data As" option in that dialog box.

I've tried that but it still won't save the changes I've made. But it will save the data if I add the taxiway lights myself. But I prefer to edit them if possible.

As AFLT custom lights seriously impact FPS , it may be best to use it as an editor GUI, then use AFLT's XML to update a custom airport's XML.

So far, I haven't had any problems with the frame rates. I have the Nvidia RTX-3060 which is pretty fast, 12GB.


Ken.

 

[GaryGB]

According to a google search, one can edit an ADE stock taxiway lights. But I haven't been able to do that, and most of the time, google searches are wrong.

Ken.

Please explain the (3) distinct assertions you made in this statement:

* "One can edit an ADE stock taxiway lights" (...do you mean 'in' ADE ?)

* "I haven't been able to do that" (...do you mean edit stock taxiway lights 'in' ADE ?)

* "most of the time, google searches are wrong" (...do you mean most of the time, 'your' google searches are wrong ?)


To reply with any meaningful info, when you type your posts, we need you to be more accurate, and clear in your wording.

GaryGB

 

[kmanning]

Please explain the (3) distinct assertions you made in this statement:

* "One can edit an ADE stock taxiway lights" (...do you mean 'in' ADE ?)

No, in AFLT.

* "I haven't been able to do that" (...do you mean edit stock taxiway lights 'in' ADE ?)

What I meant to say is that AFLT won't save the changes I've made. I can edit the ADE stock taxiway lights in AFLT meaning that I can move and drag them around, and also place a single taxiway light where I want it. It just want save those changes when I close AFLT and open AFLT again. The lights are back they way they were as though I never moved them.

* "most of the time, google searches are wrong" (...do you mean most of the time, 'your' google searches are wrong ?)

Yes, especially with topics like this. An example is that a google search will tell you that you can exclude taxiway lights in ADE by using the exclude rectangle. That is not true. There is no selection in the Properties that gives you the option to exclude taxiway lights. The only items that can be excluded are the items listed in the Properties when using the exclude rectangle. One has the option to either select the item or select ALL. But the only items that get excluded when you select ALL are the ones listed in the Properties.

To reply with any meaningful info, when you type your posts, we need you to be more accurate, and clear in your wording.

NOTE: see my edits above.
I think I am very clear with my words most of the time when I post. It was very late and was getting tired.

Ken.

 

[GaryGB]

What I meant to say is that AFLT won't save the changes I've made. I can edit the ADE stock taxiway lights in AFLT meaning that I can move and drag them around, and also place a single taxiway light where I want it. It just want save those changes when I close AFLT and open AFLT again. The lights are back they way they were as though I never moved them.

Please ZIP and link the AFLT project; also ZIP and link the original ADE project (using ADEv179x Menu > Project > Back Up)

Yes, especially with topics like this. An example is that a google search will tell you that you can exclude taxiway lights in ADE by using the exclude rectangle. That is not true. There is no selection in the Properties that gives you the option to exclude taxiway lights. The only items that can be excluded are the items listed in the Properties when using the exclude rectangle. One has the option to either select the item or select ALL. But the only items that get excluded when you select ALL are the ones listed in the Properties.

Indeed, Google AI manages to get at least one or more thing wrong when it attempts a multiple related topic reply to a query.

NOTE: see my edits above.

I think I am very clear with my words most of the time when I post. It was very late and was getting tired.

You do indeed, typically make a valiant effort to explain things in text replies.

I suggest you more often just save some time (and get more rest) by posting links to complete sets of files when asked.

GaryGB

 

[kmanning]

Hi Gary,

Sorry for the late response. I didn't read your post until late last night. I hope these are the correct files. If not, just let me know. I'm sure I got the ADE project file correct but it's the AFLT project that I'm not sure about. All I know to do is to launch AFLT and open an ADE xml file and that becomes the project file for AFLT. There is no menu in AFLT that gives me the option to save as an AFLT project file, other than saving a placement data file. But AFLT will not open that file if you point to it in AFLT because it's not an airport file. But if you need it, let me know. Here are the links below:

https://www.mediafire.com/file/7xwgm6yg080icbj/ADE+Project+File+Using+Project_Backup.zip/file

https://www.mediafire.com/file/ge2zg3sf4lwfl9w/AFLT+Project+Files.zip/file

https://www.mediafire.com/file/3in0...ort+1986_Final+Alignment_ADEX_KM+(2).ad4/file

Ken.

 

[kmanning]

Hi Gary,

I went ahead and posted the AFLT Placement Data File and the Stock Data file. See below:

Ken.

 

[tgibson]

You say it only saves files with lights you added not just moved. What if you add one or two lights to the stock data and save that?

 

[kmanning]

You say it only saves files with lights you added not just moved. What if you add one or two lights to the stock data and save that?

Hi Tom,

I've might not have made it clear but AFLT will save the placement data file. Yes, I can add additional lights to the stock and AFLT will save those additional lights. But if I simply move or drag the stock lights to another location, as if I were editing the stock lights, those changes are not saved. So, when I edit the stock and save the placement data, close AFLT and reopen AFLT again, the lights go back to their orginal position, as though I've never edited them. I hope that clears things up.