Logbook not logging

Logbook definitely not working properly for me either. It seems to get my flight time correct usually, but is not consistently logging landings or takeoffs.

In my case (since SU5 and Hotfix), the Logbook shows everything except takeoffs and landings. I went as far as a COMPLETE clean install yesterday; empty community folder, all “default” settings and no change.

Brief description of the issue:

Since the latest update, I’ve noticed that not all my flights are being registed in the Log book. Example, I did a flight twice and only the first one was recorded. Also, I recently updated my OS to Win11 from Win10 and when I viewed the log, some recent flights that were recorded are now gone.

Are you using Developer Mode or made changes in it?

Not using Dev Mode.

Have you disabled/removed all your mods and addons?

Mods have no impact on this issue.

Provide Screenshot(s)/video(s) of the issue encountered:

Not applicable

Detailed steps to reproduce the issue encountered:

Not applicable

PC specs and/or peripheral set up if relevant:

Not applicable

Build Version # when you first started experiencing this issue:

SU11 build


[/wrap]

Does this topic cover your issue?

In my case no information is stored for a flight. As mentioned, I even had recent records removed. I’ll do some more testing but it has played up consistently since the latest update. It’s a little annoying as I’m 20 hrs off 2,000 hrs.

After further testing, every flight I log gets logged but replaces the previous flight. There must be at lease eight flights that have been lost in the last few days due to this. At this rate, I’ll never get to 2,000 hrs, as it seems to have stopped me around 1,980 hrs. Let’s say I do a flight of 3hrs. It get’s recorded and I now have 17hrs to go. Then I do a quick circuit of say 5 mins. The previous 3hr flight is replaced with the 5min flight and I’m back to 20hrs to get to my 2,000hrs.

I noticed the other other day I flew for 45 mins but got a single 5 min log entry for the flight. Often I get two log entries for one flight, one long and a tiny short one which I guess is split at landing time and the short one is just taxiing and shutting down.

FYI: I saw this post a few days ago stating that the issue is with the active pause function. When in a flight, if you pause the flight then the logging stops. So you get your flight time only up to the point that you paused the sim. Flight time after the pause is not logged.

That could have been my cause. I do remember purposely and accidentally using active pause, but am not certain of that flight specifically.

During my testing, I didn’t use pause.

The pause is definitely affecting my logged flight times. But maybe there’s other factors as well. There’s definitely a bug with the log times so maybe there’s multiple causes.

I heard something tonight - that there is a cache size for the log book and if you reach the maximum size it can’t grow further. I’m wondering if this is why every flight I log overwrites the last flight, so the total hrs basically can’t grow further. It’s disappointing, as I’ve been working towards my 2,000 hrs and I’m 20 hrs off reaching it.

Since SU5 my logbook shows all my flight as 00:00:00 hrs with the same departure and arrival airport.
I fly the FBW Dev version and do my flightplanning via Simbrief. (only select my departure position in MSFS)

Is the Developers Mode active?

No, it’s off

I run a separate program, Volanta, to log flights. It’s significantly better, and it’s free. Try it.

As this topic seems to be still open: My logbook hasn’t recorded any take-offs since beginning of September. Landings and flight times seem OK, though…

Workaround. Set RWY as departure.

HI! I have same issue. My Logbook don’t login since 14 Sep. 2020. I hope it’ll be solved soon.

There’s certainly some issues with the logging of take offs and landings. We tend to do touch and go’s on small airports between larger destinations, and these are no longer being logged. Even taking off after a full stop landing doesn’t get logged. Very frustrating, and I can only assume has occurred after the latest update as it seemed very consistent before then.