Re: It's time for a new default airport

Hi Folks,

On Mon, Jun 15, 2026 at 10:49 AM Scott Giese wrote:

> I'm supportive of a change, especially due to BIKF being unusable on next
> with WS3.  It's completely broken as-is.
>
This bug is being tracked as
https://gitlab.com/flightgear/flightgear/-/work_items/3410.

It just needs a small fix in the runtime WS3.0 loader.  I know what the fix
is.  I just need to stop working on the voxel clouds for long enough to fix
it :).  I should have it fixed for TP1, so that shouldn't be a blocker for
using it as the default airport for that release.  That's not to say that
we shouldn't have a different airport.

Of course, if anyone wants to take a look at fixing it themselves, they are
very welcome.  I've updated the issue with some guidance to help anyone who
might want to have a go.  It's a fairly straightforward bug, and easy to
test.

Best regards,

-Stuart

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