Board index FlightGear Support Installation

apt.dat unknown problem Nightly 2020.4.0

Need help getting up and running? Installing FlightGear, add-on planes, sceneries etc.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post.

- what OS (Windows Xp/Vista, Mac etc.) are you running?
- what FlightGear version do you use?
- what graphics card do you have?

Please, also see Requesting Technical Help.

Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there.

apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Tue Jan 04, 2022 2:11 pm

I'm having apt.dat and navdata troubles - all the airport data is missing so I've no airports or nav data, I've tried re-install of the nightly - this error about unknown row code 10 pops up both before and after the reinstall -Windows10 nightly 2020.4.0 Jenkins number/ID 4247:4247
I can't think what's changed to cause the error before the reinstall except for removing some joystick .xml files to regenerate them.

Code: Select all
    0.23 [WARN]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1794: readStringProperty: unknown:apt.dat files
    0.23 [WARN]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1212: NavCache: rebuild required for apt.dat files (no file in cache, but 1 such file found in scenery paths)
    0.23 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1445: NavCache: main cache rebuild required
    1.69 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:297: NavCache at:Path "C:/Users/Win7/AppData/Roaming/flightgear.org/navdata_2020_4.cache"
    1.69 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:300: NavCache read-only flags is:0
    1.70 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:336: will create tables
    1.74 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1650: Loading apt.dat file: 'C:/Program Files/FlightGear 2020.4/data/Airports/apt.dat.gz'
    1.74 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Airports\apt_loader.cxx:147: apt.dat format version (C:/Program Files/FlightGear 2020.4/data/Airports/apt.dat.gz): 1000
    4.30 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1661: apt.dat files load took: 2556
    4.30 [ALRT]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Airports\apt_loader.cxx:347: C:/Program Files/FlightGear 2020.4/data/Airports/apt.dat.gz:2112967: unknown row code 10 (10   56.21374130  043.78958510 xxx 107.52  1680 0.0 0.0    90 161161  1 0 0 0.25 0)
    4.52 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:2805: aborting cache transaction!
    4.52 [WARN]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1962: NavCache: aborting transaction
    4.53 [ALRT]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:1752: caught exception rebuilding navCache:C:/Program Files/FlightGear 2020.4/data/Airports/apt.dat.gz:2112967: unknown row code 10
    4.53 [INFO]:navaid    C:\Jenkins\workspace\Windows-nightly\flightgear\src\Navaids\NavDataCache.cxx:205: cache rebuild took:2831msec
    4.56 [INFO]:general   C:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:1481: init package root at:Path "D:/FlightGe
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby wkitty42 » Tue Jan 04, 2022 2:52 pm

on 2021 Dec 23, the older 810 and 850 formats were removed... they were added back on 2020 Dec 25... if your build is/was from between those dates, this explains what you are seeing... please try the latest nightly and see if you still have the same problem...

SF URL: http://sourceforge.net/p/flightgear/flightgear/ci/913eb83e10c1ee5deb95fa12a3604f2a8b541c88/

Commit: 913eb83e10c1ee5deb95fa12a3604f2a8b541c88
Author: Scott Giese
Committer: Scott Giese
AuthorDate: Wed Dec 22 23:55:38 2021 -0600

APT.DAT version 810 and 850 are both obsolete.

Remove 810 parsing.
Eliminate version strings from method names and messages.

SF URL: http://sourceforge.net/p/flightgear/flightgear/ci/a993ff7ccb61ba0f2d7019d69b63771f1c934d14/

Commit: a993ff7ccb61ba0f2d7019d69b63771f1c934d14
Author: Scott Giese
Committer: Scott Giese
AuthorDate: Sat Dec 25 02:16:40 2021 -0600

Revert "APT.DAT version 810 and 850 are both obsolete."

This reverts commit 913eb83e10c1ee5deb95fa12a3604f2a8b541c88.
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: apt.dat unknown problem Nightly 2020.4.0

Postby xDraconian » Tue Jan 04, 2022 4:10 pm

That was my fault. That commit was made to the wrong branch, so I reverted it once I discovered the error.
xDraconian
 
Posts: 406
Joined: Sun Jan 21, 2018 6:53 am
Version: Git
OS: Linux Mint

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Tue Jan 04, 2022 5:02 pm

Thanks wkitty, I am using the latest nightly downloaded today from here which backs up what you're saying about the date

https://download.flightgear.org/builds/nightly/

As for the links you posted I don't know how to find/download the nightly from these (I tried the apt.dat files but access was denied), there are no files in the 'unstable' folder on Git and only the 2020.3 version that I could find. The Git navigation is still a bit of a mystery to me it seems :/
Chris

[edit] thanks xDraconian, could eitherof you point me to the latest full nightly? Is the link above no longer a source?
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby wkitty42 » Tue Jan 04, 2022 5:13 pm

xDraconian wrote in Tue Jan 04, 2022 4:10 pm:That was my fault. That commit was made to the wrong branch, so I reverted it once I discovered the error.

ahhh, ok... i mean, i knew those formats were old but was wondering about their removal since FG still uses them... i just waited to see what would flesh out :)
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Tue Jan 04, 2022 11:36 pm

Any clues where/how to get the nightly as https://download.flightgear.org/builds/nightly/ only has older ones?
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby mrozigor » Wed Jan 05, 2022 8:02 am

You can download files directly from build server - e.g. http://build.flightgear.org:8080/view/W ... tGear/bin/

Just copy them to main directory.
mrozigor
 
Posts: 6
Joined: Tue Mar 26, 2019 5:53 pm

Re: apt.dat unknown problem Nightly 2020.4.0

Postby wkitty42 » Wed Jan 05, 2022 1:06 pm

Volador wrote in Tue Jan 04, 2022 11:36 pm:Any clues where/how to get the nightly as https://download.flightgear.org/builds/nightly/ only has older ones?

please look again... the ones i see on there with ".exe" extensions have today's date on them, 2022 Jan 5...
there may have been a problem that has since been resolved allowing for them to be properly updated...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Wed Jan 05, 2022 4:11 pm

mrozigor, thank you, it is actually still a bit of a mystery to me, the filenames and folders did not match what I have on my windows system and I don't know how to build FG -

In any case, as luck would have it I just spotted that the .exe was now up to date (5-1-2022) on the nightly builds link before I read wkitty's post pointing that fact out. Thank you all. I'll download this and get ready for this evenings GA Wednesday event safe in the knowledge I'll not have to use coordinates to start at the right airport :D
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Wed Jan 05, 2022 4:41 pm

I spoke too soon, the windows 5-01-2022 .exe didn't work, I even deleted the existing navdata_2020_4.cache - same unknown row code appears in the log
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby mrozigor » Wed Jan 05, 2022 5:45 pm

Have you tried to download files from this URL (http://build.flightgear.org:8080/view/W ... p*/bin.zip) and unpack it into main FG folder?
mrozigor
 
Posts: 6
Joined: Tue Mar 26, 2019 5:53 pm

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Wed Jan 05, 2022 6:03 pm

Hi mrozigor - I've just managed to get it to work and I think it's regenerated the nav data (it took a reassuring few seconds to go through the process when starting). I had unpaked the bin folder from jenkins but I didn't know that this wouldn't work as a new 'bin' folder on it's own. Fortunately I had the old bin folder and copied the missing files back into the new unzipped bin folder... long story short it seems to be working but I've most likely butchered things in the process. I'll just cross my fingers for now and hope that in a few days or so there will be a new nightly with everything in the right place. Thanks again for your suggestions.
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Volador » Wed Jan 05, 2022 6:12 pm

I spoke too soon again :/ ( a little knowledge is dangerous ) it's officially broken (by me trying to fix it). Fortunately I had a full nightly from November in my downloads folder , I've installed that and I'm up and running again
User avatar
Volador
 
Posts: 1140
Joined: Tue Sep 01, 2020 4:58 pm
Callsign: Volador, G-VLDR
Version: 2020.4
OS: Windows 10, 64 bit

Re: apt.dat unknown problem Nightly 2020.4.0

Postby Chris_DE » Wed Jan 12, 2022 10:44 pm

Hi, all,

seems that there are about 1600 airports with old [715] taxiway definitions in apt.dat.
These need to be fixed, workaround which did the trick for me (Windows-Platform):

- Unzip apt.dat.gz $Program-Folder\data\Airports
- Open apt.dat in any editor with regex-support [I used notepadd++ ]
- Search and replace ^10\s\s with 110\s
- Save file
- gzip apt.dat to apt.dat.gz
- start Flightgear
- Navdata should now be correctly initilized without abort.

Kind regards

Chris
Chris_DE
 
Posts: 12
Joined: Wed Jan 12, 2022 10:19 pm

Re: apt.dat unknown problem Nightly 2020.4.0

Postby wkitty42 » Thu Jan 13, 2022 9:31 am

i don't think that's the proper thing to do, @Chris_DE... for one thing, the line formats are very very different...

XP-APT715-Spec
Code: Select all
10 Runway or taxiway at an airport.
[...]
Example data
Here is a simplified fragment for part of an airport in apt.dat:

1 5355 1 0 KABQ Albuquerque Intl Sunport
10 35.044209 -106.598557 08x 90.44 13749 1000.0000 0.1000 150 252231 02 0 3 0.25 1
[...]

10          Identifies this as a data line for a runway or taxiway segment.
35.044209   Latitude (in decimal degrees) of runway or taxiway segment center.
-106.598557 Longitude (in decimal degrees) of runway or taxiway segment center.
08x         Runway number (eg “25x” or “24R”). If there is no runway suffix (eg. “L”, “R”, “C” or "S"), then an “x” is used. “xxx” identifies the [...]
90.439      True (not magnetic) heading of the runway in degrees. Must be between 0.00 and 360.00. 
13749       Runway or taxiway segment length in feet.
1000.0000   Length of displaced threshold (1,000 feet) for runway 08 and for the [...]
0.1000      Length of stopway/blastpad/over-run at the approach end of runway
150         Runway or taxiway segment width in feet.
252231      Runway or taxiway segment lighting codes.
02          Runway or taxiway surface code for the runway or taxiway segment.
0           Runway shoulder code. These are only available in file version 701 and later. Here, code 0 implies that there is no runway shoulder.
3           Runway markings (the white painted markings on the surface of the runway. Here, code 3 implies precision runway markings [...]
0.25        Runway smoothness. Used to cause bumps when taxying or rolling
1           Runway has 'distance remaining' signs (0=no signs, 1=show signs).

XP-APT850-Spec.pdf
Code: Select all
110      Pavement (taxiway or ramp) header      Must form a closed loop
[...]
EXAMPLE DATA
[...]
1      21 1 0 KBFI Boeing Field King Co Intl
[...]
110    1 0.25 150.29 A2 Exit
[...]

110      Row code for a pavement chunk header (must be followed by a set of nodes)
1        Code defining the surface type (concrete, asphalt, etc)
0.25     Runway smoothness (not used by X-Plane yet)
150.29   Orientation (true degrees) of pavement texture ‘grain’
A2 Exit  Description of pavement chunk (not used by X-Plane)

so you can see that it is not simply a matter of changing the row code... just doing that and you now have
  • the old lat/lon being used for the new surface type and smoothness
  • the old runway designation "08x" as the degree orientation
  • the old true (not magnetic) heading value as the description...
i won't even mention the row code 113 or 114 boundary termination codes that the 110 row code requires to follow the 111 and 112 node definition lines of the taxiway which are also non-existent at this point...

converting the 60000+ 10 row code data lines to the proper 850+ format manually would be quite painful... a custom line parsing script or program to handle this and place the additional required lines is the only way to go... even then i don't think all the necessary data is available in the original 10 code lines... it may be but i've written this post pretty quickly over the last 30 minutes or so...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Next

Return to Installation

Who is online

Users browsing this forum: No registered users and 3 guests