When I was testing, I didn’t interact with ATC, so I do not believe that is a trigger for uncontrolled fields (controlled/towered fields yes).
However, it is a good point about taxiing too far away, I will check that as well.
When I was testing, I didn’t interact with ATC, so I do not believe that is a trigger for uncontrolled fields (controlled/towered fields yes).
However, it is a good point about taxiing too far away, I will check that as well.
Embarrassed to say I have never once looked at the Objectives window – until you mentioned it. I always relied solely on ATC, which doesn’t help on bush strips. Thanks. The sim is still not logging a lot of legitimate landings, but Objectives does give you an idea of what is expected.
I don’t think the ATC window has anything to do with it. I always announce clear of the runway and it is hit or miss whether or not completion is triggered and the flight is logged.
I usually set my destination to be a parking area at the destination airport, and one thing I’ve noticed is that whenever I park with the assistance of a marshaller my flight is logged. But sometimes there isn’t one at the destination parking area, and in that case sometimes the flight is logged, but often it is not.
What I mean is I use the ATC window to confirm I have taxied off an un-towered airstrip, so that when I shut down, not only does it log correctly, but is also logged at the airstrip, and not it’s vicinity. When the ATC window shows the option to announce I am clear, I park up. It works every time for me.
Before it went broken the logbook worked perfectly…without the necessity of shut down…press return to main menu and it logged…if you try to fly air to air from a point in the air to another it doesn’t log…at the release it worked perfectly…not vicinity nor missed landings or take off…the logbook is broken.
I just flew 3 long flights of over 3 hours today…NONE are on my logbook.
same for me.
Just completed training session No7 VFR flight using waypoints.
The takeoff, and flight times were logged, but the landing wasn’t, despite completion of all objectives, and ‘congratulations’?
The completion of the exercise was listed though in the achievements part.
As always, a bit hit and miss on what it records.
I have just completed a lap of Australia in the C152, and almost half of this is not recorded in the logbook.
What method did you use when you completed the flights, including shutdown?
Yeah, I do the same, (use ATC window to confirm clear of runway) but I still seem to have inconsistent results with flight logging.
I’m A/B testing and prior to 1.8.3 logging worked perfectly. You didn’t need to taxi and shut down. A landing was enough (especially useful at landing strips hemmed in by forests with no parking).
I’m getting flights showing as “vicinity of” locations 100km+ from the final destination and not even on the flight path. If it was just not shutting down/taxi to correct spot then you’d expect it to at least have the “vicinity of” the airport as the final location rather than randomly elsewhere.
As for parking the number of times I’ve been assigned a parking location occupied by another plane or item of ground equipment like a bus is crazy.
Oh and I noticed this issue is now in this week’s Dev Update!
Found another great way to log your flight if it’s not going to the logbook screen after system shutdown - taxi straight into the side of a hangar, this will end your flight and get you a completed logbook entry! ![]()
I’ve received a response from the Zendesk to my bug report of this issue that the dev team plans to deeper investigate this. So issue already has their attention. ![]()
I end the flight when i get to the gate and shut the engines down.
Yes, it´s less problem if you shut down engine but definitely not always. If it´s important to shut down engine. How can a 1 h flight be recorded as 20 minutes and end “Vicinity”, and another flight not be recorded?
The bug with logfile is the most important issue for developer to fix!!!
I have 150 h of flight time and have lost more than 50 h at small airports.
I always shut down the engine, but a few flights are still missing and moreover there are numerous takeoffs missing.
Maybe there’s some subtlety in the way you should shutdown the engine to trigger the entry. But frankly speaking, ANY proper flight should get an entry and a takoff and landing counted, if performed.
Weirdly I’ve not had any issue with take offs failing to be recorded only landings.
Just so annoying.
Before logbook went broken every single flight was logged…the most important thing is that the flight was logged without doing anything…pressing escape to main menu the flight was logged correctly…now is broken or need a series of workaround
I found yesterday that shutting down the engine was not enough, and turning off master switches ended the flight, with the logbook popup appearing for the first time for me. Seems to be very inconsistent though.