Re: It's time for a new default airport

I've been able to secure some scenery made for other flight sims that I can convert and use in FlightGear. I'm still tuning some things, so I haven't uploaded anything to the database yet, but I have very good packs for Minneapolis (KMSP) and other smaller airports in Minnesota, and I have a pack for Detroit (KDTW) that is far more detailed and advanced than anything else we have in FlightGear. I can try and talk with other creators if we have other places in mind, but that's what I have for now. Lagos (DNMM) would be a cool default airport, but I'm not sure how popular it would be.
________________________________
From: Scott Giese <[email protected]>
Sent: Monday, June 15, 2026 2:48 AM
To: [email protected] <[email protected]>
Subject: Re: [Flightgear-devel] It's time for a new default airport


I'm supportive of a change, especially due to BIKF being unusable on next with WS3.  It's completely broken as-is.

I haven't noticed much attention toward creating new airports over the last few years, but there have been some.  Might be worth seeing what's available.

BIKF was totally undeveloped when it was chosen, so 'existing and complete' doesn't need to be a constraint when selecting a new default airport.  If a undeveloped airport is chosen, there will need to be some interest from the scenery community to build it.

Scott

On 6/15/2026 12:55 AM, Josh Davidson wrote:
Hi,
It's now been 6 years since he changed, lets change it...

BIKF besides will due to it's location have not very bright lighting often, so it doesn't showcase FlightGear fantastically in my view...

Let's change it, I think it would be great!

--
Josh Davidson




_______________________________________________
Flightgear-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel