Bratters,
Still trying to get me head around your problem, but this might help you to understand what is going on and/or sort out the problem.
I'm not sure if the columns you posted are the only ones you are showing, or if this was just an example. I've attached a screen shot of my MyFlights list for you to compare.
First if all, regarding the missing airline logos in the list that are showing in the photo details at the bottom. Airline in the photo details is actually Company in the MyFlights list and this data comes from the main NavData.db3 database that has details of the REGISTERED OWNER of the aircraft. The Airline LOGO in the MyFlights list is actually generated from the Flight ID or callsign shown in MyFlights. So if an aircraft is registered as belonging to "John Smith Airways" this will show in the photo details, but if the aircraft has been leased to "Joe Bloggs Airways" and is using Joe's Flight ID, then you will get Joe's airline logo in MyFlights.
Of course, this means that if there is no Flight ID showing in MyFlights, you won't get an aircraft logo - but you will still see the airline the aircraft is registered to in the photo details. The Flight ID is set by the flight crew and it seems that the policy of some airlines is that it must be set and others don't seem bothered. Hope you followed that :-)
The aircraft column in MyFlights shows the SHORT name, the code used worldwide by ICAO to describe that aircraft (AT in the NavData.db3 database). The Type in the photo details in the LONG or plain English name of the aircraft (AN in NavData.db3). MyLog shows both of these, with the short name in the A/C Type column and the long name in the A/C Name column.
If you have missing details in MyLog, these can be populated by using the MyLog > Tools > Populate button - if the data in in the NavData.db3 database, then they will be copied across to the MyLog database.
Also, here is a very quick summary of how the databases work:
- Navdata.db3 comes already populated, this is the main source database for everything you will see in MyFlight, Network and MyLog
- MyLog.db3 is empty when you install RB. It is a completely separate database to NavData.db3.
- When an aircraft is detected "live" (not Network) by RB, the details for that aircraft are copied to MyLog as a historical record. If all the aircraft details are already in NavData.db3, then the record in MyLog will also be complete. If there is no record in NavData, then only the bare details are copied to MyLog - Mode S, ModeSCountry, First Time/Last Time. Auto populate will now check the Airnav server and fill in the blanks in MyFlights and will write the details to NavData - the details are NOT written to MyLog which will still only contain the partial record.
- When you use MyLog > Tools > Populate, this than checks NavData and updates the missing information.
Hope this helps.