You need to shut down engine / battery so you get the sim to give the menu. Then it logs !!!
If u land leave all on … and then go to main menu … you get the “vicinity” one in the logbook
Hmm … that ATC theory is worth testing … I have to admit, that some time ago I completely stopped interacting with ATC.
But even in the past (v 1.8.x) … when the Log Book was working correctly … I only ever talked to ATC when I launched the aircraft … and I only talked to ATC once, when I confirmed that “I am leaving the airspace” of the airport where I started from.
However, ATC usage should not be necessary for a proper Log Book.
It feels like the subsystem which is doing the “Location reporting to the LogBook” has such a low priority that its messages are “lost” due to timeouts … or maybe the archieving (storage) job is not getting enough “CPU cycles” to succeed. Perhaps a result of some performance tuning in other parts of the system?
But without seeing (knowning) the real source code this is just a wild guess.
1 Like
Unfortunately that doesn’t work for all.
Can’t confirm this. I shut down engine / battery every time, all C&D, and the flight being logged (and having arrival and destination) and/or getting the menu is hit and miss, at least in my case.
No doubt, ATC should NOT be necessary for a proper Logbook entry.
1 Like
Also experiencing inconsistent logbook entries. I have had some instances where nothing at all is logged, but more often what happens is the takeoff and landing counts will be incorrect.
This is quite visible if I fly touch and go circuits. Sometimes the counts are correct, but this is more the exception rather than rule.
I think MSFS tighten the rule how a logbook entries should be recorded. First, if you have developer mode on, you are “developing” not fighting. Secondly, DO “By the book” meaning fallow the ATC’s command all the way to the end.
Here is my own opinion, MSFS’s logbook different from the real logbook, I call it a “flight session”, you can do anything in between like touch and go, re-fuel, land, take off at different places/airports but only the end airport you land and properly “simulated” will log.
Here is an example, Two days ago I flight from RCTP to PHJR, upon arrived found out no one it there to greet me so iI took off and lend 2 more times and did the 2 cents tour taxi all over the place but not thing (I have not tested the uncontrolled airports and do not want to loose the hours I put in) so I decided go to PHNL with is next to it and it logged, so I end up with 1 took off 4 landing.
I did some testing using various combinations of actions and I think I finally may have found a possible culprit that resulted in my flights not to be logged. There is another pause / un-pause function in the sim (not active pause) that I mapped to some buttons to in the beginning days of the sim. This pause prevented the autopilot trim from running away when you pause so I kept on using it. I seems like in the first patch something changed and this hard pause during a flight now results in the flight not being logged. Since the problem with the autopilot and soft pause has been fixed I guess I do not need the hard pause any more.
Maybe worth checking this out if you are having this problem.
PS. I never fly in dev mode or use ATC.
So after executing about 20 left-hand patterns, I believe I have figured out the trigger for ‘getting the popup’ and having a landing logged after a complete shutdown at an untowered airport, vice needing to escape to the main menu manually after shutting down (usually resulting in a ‘Vicinity’ entry in the logbook and a ‘0’ for landings for that flight). The BLUF is that I believe this is caused by a either a poor landing partially off the runway, or landing on the runway, drifting off, and coming back on the runway.
Note this is probably applicable if people are not getting landings logged at towered airports, although I have never had an issue at towered airports as long as I request taxi to parking from the tower, taxi to the correct highlighted box (you need to acknowledge the towers agreeing to your parking request for this to show up), and shutting down inside the box (make sure it changes color).
For my test (it would be great if people could do more runs to validate), I flew a 172 out of KWST rw 32. I doubt these specifics matter but a) it would make for a consistent test and b) RI beaches look great. Should not matter if you start cold and dark (I started on the runway), but if you do start up manually, make sure you request taxi and get to the correct runway stop point (I believe this is the trigger for a takeoff being counted in the log if you don’t start on the runway). I use the ribbon to make it easier, and most of the time let the copilot taxi (he will stop at the hold as long as you don’t request permission takeoff).
Either way, before you take off, open up the Objectives window. It doesn’t really matter when you open this, but its easier on the ground. Take off as normal and fly the left hand pattern. You’ll notice that the Objectives Window will progress through each phase of the flight (on a long flight, this will say maintain cruise altitude of something similar). On final it will eventually tell you to line up, reduce speed, etc, although sometimes it takes a little while for it to figure out you are landing.
Land the plane as you normally would. This is the make or break point, nothing else before this should have changed with how you fly other than opening the objectives window. This is when that matters. If you land on the runway and start decelerating/braking and stay on the runway, the Objective Window should switch to something like ‘Reduce speed to 15 kts and exit runway’. If you slow down and leave the runway at this point and come to a complete stop, the Objective Window will change to ‘End of Flight.’ If you shut off engines and battery, you will get the popup and credited with a take-off/landing.
However, if you land just off the runway, and I believe more importantly go off and back on the runway (I’m still not great at this), the Objective Window will change to something like ‘Apply full power for take-off’. There is no way that I have seen to get this to transition to end of flight other than take-off and landing again. I flew another pattern after this happened and stuck the landing, got the ‘Reduce speed…’ objective, and shutdown, and got the pop-up, along with 2 take-offs/2 landings for this flight.
One more thing to note is that I have not been communicating on the traffic channel for the untowered airport, so I don’t believe the trigger is tied to ATC (unlike for towered airports).
Standing by for questions, again would love it if someone could either validate or may even give a more specific trigger to get the correct objective.
Unsure if this will address flights not showing up at all or the hours not being correct, but it doesn’t hurt to try (really just keep the objectives window open and see what it says after landing).
1 Like
So, I have done about a half dozen flights in the last week and have noticed the log book is not logging the landings at the airport I landed at.
I noticed a couple of landings were a bit “hard”, but I didn’t destroy the aircraft. I just buttered the bread at KMSP and no landing logged.
I’m all updated.
1 Like
Dev mode is off. I’ve not had it on at all for the past 2 patches. The log book is busted. I only get one in about 10 flights recorded properly. I’ve even had 2+ hour flights that have only logged the first minute or so.
Turns out the pause issue I thought caused my problem is not the issue. My last flight was not logged again. Back to the drawing board
Many thanks for your answers!
The DEV mode is one of the obvious reasons behind this logbook saving issue but seems not to be the only one!
The issue has been shared with the team. So even if it’s not displayed on the next top bugs list we are still looking into it.
1 Like
Cool,
I still have never seen many of the pop ups you list with about 200hrs time. Only way I get a logged flight is to set a take off and landing at the world map follow that course. Park at any open spot off the runway this includes jet ramps and shut down, If I get the flight complete pop up it always logs. If not and I exit to main menu about 70% it will log (if I see the validated message pop up along the bottom. I have never used the ATC or any communications at all.
This only works my first flight of the day no other flights will log unless I restart the sim.
None of the experimental procedures that have been suggested nor the ones I thought I had stumbled on give consistent results.
The funny thing is, that if I run LittleNavMap and make a plan or just fly around the flight time is recorded in LittleNavMap everytime.
So, the data is being generated by MSFS, its just the logbook is ■■■■■.
So at least I have a way of recording my hours - which is all that I would list in a real logbook and then add comments for specific occasions when necessary.
Hit or miss on the uncontrolled fields. Sometimes just taxiing off the runway to nearest building and then shutting down will trigger completion and a logged flight. Most times not. I think we’d all like to know the precise criteria for getting a logged flight for every successful takeoff and landing.
Same here after 93 hours my flights are not recorded …
If you could tell me your last flight, I am quite happy to replicate, and shoot a video of what I do. But from my experience, the airport doesn’t matter, towered or not.
Anyone really, preferably short hops, and I will replicate.
To TL;DR my above post, keep the Objectives window open when landing on uncontrolled/un-towered fields.
Once you touchdown and slowdown, the objective should change to ‘Reduce speed to 15kts and leave runway’. If you follow these directions, the objective will change to ‘End of Flight’. If you do a compete shutdown, it will log the landing.
If you do not get the ‘Reduce speed to 15kts and leave runway’ objective, you will most-likely get an objective to take off again. At this point you would need to do another take-off/landing for your landing to log, shutting down will not give the pop-up.
I believe the trigger to getting the objective for taking off again (and not getting a counted landing) is if you leave and comeback in the runway during landing, but this needs more testing.
Most helpful thing to confirm is if people landing on uncontrolled fields can keep their Objectives window open during landings. Note: The objective window is not need to display the pop-up and count the landing, but is the best tool I’ve found to diagnose the issue.
That’s kind of what I do, but I use the ATC window. As soon as the response appears to notify I am clear of the runway, I know I am good to shut down, and also know that I am not too far away from the runway to get a “vicinity” log, not that really matters in the gran scheme.