Hi @Geno8015
Yes, the logbook bug (for those that are unaware of it) can be found here.
Whilst your suggestion above would improve the accuracy of your reports, it will still not account for flights that are dropped within a flight session.
For example, I start up MSFS 2024, fly from A to B, end the flight, start a second flight, fly from C to D, end the flight, start a third flight, fly from E to F.
On checking my logbook after the 3rd flight and before exiting MSFS, I see that the first and / or second flights are missing - only the third is shown.
In this scenario - which I have seen many times when I was monitoring my logbook - your tool would never see the first and / or second flight.
The only way around this would be for your app to run during every MSFS session & record every flight as it occurs. This is in effect what LittleNavMap does if you have it running during a MSFS session. Of course, if the LittleNavMap is not running, it will not record any flights, which is actually a good thing when one is using MSFS just to reproduce bugs or work in dev mode, etc.
Note that MSFS and LittleNavMap define a “flight” differently:
- LittleNavMap defines a flight as a takeoff followed by a landing (there are exceptions, such as when one enters slew mode, or -if my memory is correct - hover for a long period in exactly the same spot).
- MSFS defines a flight as the period between your first take off and your last landing. The logbook does not display any landings and take offs in between. The MSFS logbook (IMO) records flight sessions, not flights.