xplanereviews wrote: ↑Thursday 02 Jan 2025, 01:37
Since X-Plane (laminar Research) updated to v12.1.3 the current Seattle Airports and Seattle City have been showing loading errors...
It notes that the Earth nav data is corrupt? Thanks
The following is just a comment by another user (not an official statement). I hope it is ok to post it here.
The latest XP12 versions now check whether airports of type 1 have regular runways and complain if not (there was no such check in XP11).
Seattle Airports / City packages contain a couple of airports which are in fact only heliports or seaports (with no real runway) but coded as type 1.
The affected airports are clearly listed in log.txt, also the location of the apt.dat file(s) containing their definition.
Such types can be quickly changed to type 16 (seaport) or 17 (heliport) with any plain text editor and then the loading error should disappear.
A similar case is explained in this article for other scenery https://forums.x-plane.org/index.php?/f ... nt-2839310
I hope this helps.
I am still enjoying Drzewiecki Design products even in XP12.
Your reasoning for not investing in an XPlane 12 version of Seattle Airports and Seattle City makes sense to me.
I am new to flying and really want to try out your scenery. Is there any way you'd consider a Kickstarter to raise money to support you in building out an XPlane 12 version of Seattle City and Seattle Airports? I know I'd contribute.
Let me say that some airports can be expected for XP12, but it's hard to tell if it will happen with Seattle. We hope to see good sales results, which will allow us to think about further projects.
