I land on 21, taxi down to the end, an announce I’m clear of the runway. All good so far. I turn left on to 03, to take taxiway B to parking. But because I taxied back on to the runway, the sim assumes I want to take off again. The “Objectives” window has now changed from shut down to request takeoff clearance. I continue to taxi to parking, and because the sim expects me to take off again, the normal logbook popup does not trigger. I go back to main menu, my flight is logged, however it is one of those “Vicinity” ones, as I disrupted the flow by going back on to a runway.
I knew this was going to happen, I just wanted to illustrate it. What I could have done to avoid this would be to shut down at “1”, just to the right of runway 12, or “2”, taxied off, and around on the grass to parking, avoiding runway 09/27. Either of those would have logged my landing correctly, and not a “Vicinity” log either. The other way would be for me to take off again, then land again to do 1 or 2.
I’m not sure why it’s so convoluted to have to go through the trouble of making sure you follow the objectives in order for takeoffs and landings to be recorded…
Wheels leave ground = takeoff
Wheels back on ground = landing (allowing for a bounce or three)
This should be the case regardless if you’re talking to ATC or not, and seems like it should be much simpler to program.
Also, the highly intrusive logbook popup right after you shut down engines needs to go away. If anything, maybe a less intrusive button at the top or bottom of the screen for 20 seconds or so where you CAN end the flight, but not in the way of continuing your normal shutdown procedures, and without triggering a new 0 0 0.0 logbook entry.
100%. The “objectives” are (or should be) irrelevant to the logbook. I leave the ground: that’s a takeoff. Log it. I return to the ground: that’s a landing. Record it. I can walk away from the landing: that’s a great landing! I do both on the runway (as opposed to a taxiway, or the apron): hey, I’m not Harrison Ford!
I found out one more bug:
In last versions of sim when I flew from A → B, then B → C, then C → D in one row, only the last leg of the trip C → D was recorded in the logbook.
After update SU5 if I fly bush trip from A → B, in the logbook is the followin record:
B → B with 00:00:00 flight time.
I am so dissapointed from Asobo. I lost in this way about 700 hours which are not in my logbook.
I flew mostly bush trips, many legs in one row, but only the last leg was recorded in the logbook.
Just “for the record” … The “takeoff = zero” bug is still present in v1.18.15.0
I no longer care that much anymore, since I switched to external tools (via SimConnect API) for logging my flights. But still … this should hopefully get fixed at some point.
I’ve been successfully logging flights for a while now. Just about to hit 900 hrs. It’s important to now use Dev Mode if you want the flight time logged. I’ve noted also that if you select Continue at the end of a flight, the flight is logged and a new entry of 0 hrs is logged also. Otherwise, returning to the menu simply logs the flight as expected.
Depending on what you do or don’t based on the navlog that the sim expects, it might still not log parts of the flight or even not show the confirmation dialog at the end at all.
With all I know I’d still don’t manage to get it to work consistently (developer mode is off all the time on regular flights).
Just for the record … this bug is still around in 1.19.8.0
(Edit: to be more precise … while time tracking typically works for me since a few releases ago … the takeoff-landings count is still basically always zero … if it counts something, it is the landings)
The “confusing part” still is … if it can track the “flight time” correctly it should understand “ground time” as well … and naturally the transitions are takeoff and landing. But since those counters are still linked to those “objectives” the tracking makes no sense (to me)
That’s not the point. The point is the pop up that appears as soon as, for me flying GA, I either flip the avionics switch or the battery switch. It’s not a huge problem, for me at least, as I’m pretty much done with my shutdown at that point, and they are the only remaining cockpit switches left on, but I would still like to have the option.
I’ve not re-tested this in months, but there used to be a bug where if you click on the Continue button, that recent flight would not be logged in the logbook, but the flight you then “continued” would be, unless you performed another shutdown, and “continue”.
That at least would allow you to perform a shutdown, and start up again to continue flying if you chose to.
I basically would like to retract my previous claim … as the sim clearly can NOT track flight time correctly.
I just took the drone cam for a spin to search for the ground cracks at KPHL … I never even touched a single button in the aircraft … nor did I turn on the engine etc. … and now it tracked 5 minutes of flight time … and the sim did that on two occasions.
Now … I think I can guess what is going on here. In both cases I did “crash” the aircraft (according to the sim). So it is most likely a misguided if-then-logic in the sim which say … well … if the aircraft “crashes” then it must have been flying … right? … so lets log the time. (OK, still no landing or takeoff counted, but just a “magic” crash flight)
What actually is happening here is this …
Moving the drone away from the aircraft at some point removes the 3D scenery from the GPU … and at that point the aircraft “crashes” … even when it is parked “cold and dark”
I parked my plane, put the parking brake on, then took the drone on a trip over the mountains about 40-50 miles away. When I came back to my plane it was upside down, and nowhere near where I had parked it.
Download some bush trip from Bush Trips for Microsoft Flight Simulator | Flightsim.to
and fly whole trip n one row. Notice all individual flights on piece of paper and in the end of trip compare your paper with logbook.
Let us know the result. Good luck!
The logbook has been hit or miss since game release. It says I have 79 hours since game release, really??? The logbook is a joke. I know I spend at least 1 hour 4 times a weel flying and testing plane and checklists in this game, just based on that average, I know it’s more than 79 hours. Some flights were in excess of 2-3 hours, and if I terminated them early, should have gotten the time elapsed. FSX seems to reset logbook monthly, not sure why.
