AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: knight01 on September 24, 2010, 05:31:27 PM
-
Why is there no aircraft type specified in the "Aircraft field" for regional or biz jets. It just has three dots (...). None of the FlyBe aircraft types are filled.
-
It is a bug that Airnav are investigating. I will let Airnav Development expand further on the issue, as they have a better technical understanding of why this is still occuring.
-
I think the database needs updating, as the blank fields in this list are also blank in the database file.
If they are specified in the database file, the field is populated, as seen in the screenshot for the Lufthansa CRJ (third from bottom).
-
The database is being updated, click anywhere on the line and the data should be populated. If you dont get the silhouette right click on the line and when you get the menu choose " locate mode s code in database explorer. When database explorer comes up you will note that the entry under AT is missing, fill it in and click anywhere on the grid to save. You will have not problems with that aircraft thereafter.
I note your main problems are with RJ85 and E190 aircraft and thy seem to suffer alot.
If it doesnt populate then it will not be on the database. Population may be nearly instant or can take 20 or 30 second depending on a number of things like how busy is the server.
Please feel free to let us know of any unknown aircraft via the database update thread. Unfortunately the database that comes with the unit is a couple of years out of date therefore you can update the newer aircraft which are not on the d/b by auto-populating by clicking on the aircraft.
Alan
Alan
-
Unfortunately until the bug is fixed by Airnav development, you will need to manually update these all individually in your own personal Navdata file. The correct ICAO codes are entered for all these aircraft in the updater database that we are working on. However, the bug prevents the data we are entering in this field from going to users and it is replaced by the corrupted data and ... that you are seeing.
You will also not B77W aircraft invariably come in as B773, despite them all being annotated as B77W in the updater database. It is very frustrating for all of us.
Since we picked up that there was a bug in June, us updaters have been helping Airnav Development to identify what is happening. But we are unsighted on whether Development have the information on why it is happening and their plans to provide a fix.
As it seriously impinges on users, I hope Airnav do provide that information soon.
-
Why is this bug proving so difficult to diagnose ?
I ask purely out of professional curiosity.
-
I do wonder how many man-hours Airnav have expended on investigating/fixing this bug.
-
I do wonder how many man-hours Airnav have expended on investigating/fixing this bug.
The creation of the updater team was in part to alleviate The longstanding ICAO corruption part, which was of course first raised with them in February 09. However it persisted as reported to them again in June.
http://www.airnavsystems.com/forum/index.php?topic=5293.0
http://www.airnavsystems.com/forum/index.php?topic=2673.0
Only Airnav has that answer.
-
Hopefully sorted in the next software edition but only time will tell.
-
Hopefully sorted in the next software edition but only time will tell.
But I should hasten to add that Development have given us updaters no indication of when they plan that next software edition will be or what format the 'sort' will be. It certainly is not at a beta testing stage yet. Therefore in my eyes it remains a big 'hopefully'.