Johan G wrote:A totally different thing: I don't know how airports are loaded, but I can tell that FGrun seem to read the entire airports.dat into memory every time I start it (though I'm not a programmer). If possible it might be a good idea to load them into some compact database, like
SQLite.
The first time you start FG Flier, and when you click the 'Refresh' button in the Airports section, it just scans your Scenery directories for airports, and just gets airport ID and runway information. This info is saved into a Python dictionary, and pickled and written to ./fg_flier/data/airports. Once you have that ./fg_flier/data/airports file (i.e., you've started the program once), FG Flier just reads from that to get the list of airports ... but if you download more scenery, you'll have to click the 'Refresh' button to update the list. For simplicity's sake, it works just as well as an SQL database (which I had considered, actually), but without having to set up a new database, user, etc, and dealing with permissions.
Now ... I honestly have no clue how much memory it takes to store that list in a Python dictionary, but the airports file on my machine (basically with just the US scenery) is around 400kb. The program itself takes ~26MB or RAM when I first start it, then up to 39MB once I click on the 'Options' tab, then to 41MB after clicking the 'Paths' tab ... so I can't help but assume that the list needs are rather negligible compared to what it takes just for the wxWidgets. I'm curious to know how big it is for Chrison, lol.