Logbook not logging

My logbook has cheated me out of several flights, including two 300+ nautical mile flights just today.

Same as the OP - game shows correct flight information, I click continue… and the flight isn’t logged.

This is exasperating. I just started a few days ago, and I’ve probably lost at least a third of my total flight hours, possibly as much as half.

As reported by others - when you kill the engines the choice to go to the main menu or continue pops up - if you exit tot he main menu, the flights seem to be recorded correctly – if you choose continue - the flight isn’t record.

So until this is fixed - will have to forgo proper shut down procedures if you want the flight logged.

I can’t explain why this is bothering me so much, but I have been gradually flying GA aircraft from KEWR, now about to head to HEBA. The logbook doesn’t log accurately, and if at all.

I too probably have about 40 hours not logged. Playing MSFS, I love the product but make no mistake - all of us are glorified BETA testers.

1 Like

I will say that since I started using Return to Menu from the pop-up window every time, instead of Continue, it has logged all of my flights properly. That’s only about one night’s flying, though (five flights) so I don’t know if that really solves it or if I’ve just been lucky.

I haven’t had a single flight log since Sep 15th and if I can get the dialogue to pop up at the end of a flight it’s always the same A320 KDFW-KDFW 0 minute flight.

LOOK AT THE DATE OF THE LOGBOOK ENTRY
You can quickly identify the date your logbook started misbehaving by looking at the date of the most recent log entry.

EXIT DEVELOPER MODE – DON’T JUST TURN IT OFF
It appears that developer mode – unsurprisingly – may interfere with the logbook triggers. Specifically, if you are messing with CFG file parameters and using developer mode to resync the plane, it may keep the logbook from updating.

Go to the developer mode menu (upper left in flight screen) and select “exit” to exit developer mode. It may be that just turning it off in the options screen still hangs up the logbook logic.

HAVE THE OBJECTIVES WINDOW OPEN
To make sure you meet all the objectives for a flight, keep the objectives window open and complete them all.

USE ATC ASSISTANCE FOR TAXIING TO GATE / PARKING
Departures seem seem to always log correctly since the early December patch – takeoffs and in-air departures. Landings seem to be much more picky, but here’s what has always worked for me:

At controlled airports you don’t have to use ATC for landing, but after you land, exit the runway onto a taxiway. Tune ground, and ask to taxi to the gate or to GA parking. Turn on navigation assistance before you do this. ATC will provide instructions and blue arrows to the parking location. Acknowledge the taxi instructions, then taxi to the indicated space – it turns green when you’re in the right location. Kill the engine and then kill the master battery. You should get the end of flight menu – and I always exit to the main menu instead of continuing the flight.

At uncontrolled airports, you won’t be able to get ATC taxiing instructions, so just kill the engine and then the battery as soon as you get off the runway and stopped on the taxiway.

REFLY THE MOST RECENT LOGBOOK FLIGHT TO “UNHANG” IT
Make sure you’ve exited developer mode, then click on the most recent logbook entry. You’ll see an option to fly that flight again. Re-fly it using the techniques above to end the flight.

HOW TO KNOW IF IT FIXED THE LOGBOOK PROBLEM
If the procedures above fixed the problem, you should see today’s date for the logbook entry. If it didn’t, it will still be the date when it first broke.

A320 / ENGINE WON’T SHUT DOWN BUG
If you are unable to shut down the plane’s engine, then you may not be able to trigger the end of flight logic, or it might not correctly trigger the logbook logic even if you do get the end of flight screens.

Try flying the most recent leg with a different plane whose engines WILL shut down. I think it’s just the landing, taxiing, and shut-down portion that is necessary to make the logbook work again.

Good luck and happy flying!

2 Likes

Same here

Missing TAKE - OFFS only from small airports.

The moment I shutdown after marshalled to the stand, I get a pop-up with the correct route and the correct hours. However, after clicking continue and complete the other shutdown items (e.g. lights off, magnetos off, fuel tanks closed, etc…) and the proceed to exit the scenario back to the main screen, and then enter my logbook it shows the departure runway to be the same as the arrival runway with 0:00 logged (e.g. dep: EHAM, arr: EHAM, flight time: 00:00:00, even though the real departure airport was EHRD).

When you fly in a VA and you need to cut the engines off to validate your flight, the MFS window appears with the options “Main menu” and “Continue”. Il you click on “Main menu” you can’t validate your flight in the Virtual Airline. (the tracker indicates No complete flight). If you click on “Continue”, you can validate the VA flight but on the MFS logbook, the time will stay at 00. Could you please fix this ! Thank you !
Stéphan

Hi, mine shows everything except takeoff again.

For me, the log works. I’ve used it since januari.

Most important for me is landing 0/1. The log sais 1 if I land properly. I fly damage on (always), I like to land safely anywhere where I want to land.This requires practice with small aircraft and the trick to learn that is log validation and getting 1’s for landing in your logs. There is AI in this game, to qualify your landing. Maybe there are hundreds of rules for airliners with all communication enabled, I don’t know. Trust Yet64 has found them (see above)

I fly propellors to small airfields, that do not require approvals or communication. My comm settings are off.

As far as I know, my landing is properly logged (1) on any set destination airport, when:

  1. I keep damage on Hard
  2. I land on the set target destination (you HAVE to set destination to be logged !)
  3. keep my plane on the runway (destination runway ! choose the right one !)
  4. I don’t stall and drop too deep on arrival (only glide landings are approved)
  5. when I end the flight on handbreak, >> on the runway <<, and
  6. return to main menu to check my log

Wishlist:

  • replay
  • be able to list only good landings
  • be able to see the log without going back to main menu
  • log would give clue about what went wrong
  • save the log (what’s the max line count ?)

I really do not see why anyone should have to play their game, of this is the way you have to do every little thing we think you should. Just to get credit for an actual flight from point A to point B I do not see why everyone should be forced to do something they don’t have time for and would actually ruin the quality of enjoyment for each individual. I really think that will ruin the player count for the game because people will find a way to fly without all that extra demand to fly their way. Sure keep that aspect for people who want to do it, but do not force it on people who do not! Many want to just fly the airplane for freedom sake. So to be tied to a list of hoops you have to go through just to get credit for a beautiful take off /Flight/ and Landing. Ruins that experience when you get done with what you know was good and the Developers want to get all huffy and puffy about the fact you didn’t use their idea while you were having fun? Let me go to their house and tell them how a TV should be watched. I mean come on folks this doesn’t make you made enough to spit nails really? To spit nails you have to first file a spit nails plan, then you have to get clearance, Then you have to play 30 minutes of wait for the guy with the cart full of nail buckets to get there and hand you those nails. Call the tower, Do you still want to play spit nails when they say you can? Whats is it going to take to convince them I don’t want to spend 14 hours reloading my game of 143 gigs everytime they decide to play with a small 8 meg feature? They should really start listening to some of you, and just do the job, quit sitting in three chairs, and tell us all how they think ice should form on your plane no matter what. When they clearly do not know what it does look like when it forms anyway. Sorry I just went overboard maybe but it just isn’t right to tell people how to enjoy their time. It is right to make their time as well as ours count for something besides their personal favorite whim. And they Know that!

1 Like

I’ve actually found that if you land and shut off the engine and electric system off the flight is logged, you don’t have to taxi to parking. So if you start on a runway and shut down on the runway, you minimize your time and get credit in the log. Do not fly in developer mode if you are interested in logging the flight.

1 Like

Thank you for the calm reply, I was told that developer mode would let me change airplanes while on excursions with friends. So I enabled that in order to go along and have fun. I had no idea it was going to wipe our 50 landings and 20+ takeoffs. as well as 4/5’s of my log bog. I found out the hard way. I have since set it back but here is the thing. If they would make that switching airplanes available without developer mode would that not be cool? Why do you have to be a developer to change airplanes without having to go all the way out and back in? Would that cause extra usage for their server? OR, does going all the way out, and logging back in with another airplane, not cause as much traffic, and usage of an not at all necessary procedure? Are the developers guilty of ignoring that and what people want, or is there an actual reason behind the extra hoops that the USER,“Customer” , actually their bosses are now having to go through. It’s like the agony of a toothache waiting for them to not get what 75% of the true well known experienced users are trying with every ounce of honesty to explain to them and they say things like [Not in exact words] {Sorry that you think its a game not a simulator}. The customers will win the argument if they have to simply go back to X plain or Prepar 3d or DSC for that matter which has already garnered 2/3rds if not more of what used to be FSX players. Or did they not, or still will not, even consider that fact.

1 Like

The pic below shows the last time on 3/3 that the log logged something. It happened to be the F-15C. Since then I have flown the F-15D, Mooney, P44, Typhoon, King350. None Logged.


I flew something every day since and every time the log book shows at the end of the flight it shows me the same thing as you see below. The last F-15C input.

I’ve noticed since 3/8 I get credit for takeoff but no landing …both in Cessna and f15. Wonder if something is not working again

1 Like

When this happened to me, they asked me if I had my Developer Mode on because nothing logs with that activated. When I turned it off everything started working again.

4 Likes

I guess this is still an issue as I got this today 23/04/2021

1 Like

I stopped looking at it after the last update when they emptied it out on me. Useless logbook :crazy_face::crazy_face:

1 Like

This is a rather old post. This issue has been resolved, so there’s really no need for anyone to chime in.
Thanks to all who replied. Much appreciated :blush: