![lost pilot logbook lost pilot logbook](https://cdn11.bigcommerce.com/s-29nzvnn/images/stencil/1280x1280/products/688/15067/ha-loglrg-b-1-web_dynmd__37927.1578779799.jpg)
LOST PILOT LOGBOOK HOW TO
HOW TO KNOW IF IT FIXED THE LOGBOOK PROBLEM Re-fly it using the techniques above to end the flight. You’ll see an option to fly that flight again. Make sure you’ve exited developer mode, then click on the most recent logbook entry. REFLY THE MOST RECENT LOGBOOK FLIGHT TO “UNHANG” IT You should get the end of flight menu – and I always exit to the main menu instead of continuing the flight.Īt 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. Kill the engine and then kill the master battery. Acknowledge the taxi instructions, then taxi to the indicated space – it turns green when you’re in the right location. ATC will provide instructions and blue arrows to the parking location. Turn on navigation assistance before you do this. Tune ground, and ask to taxi to the gate or to GA parking. Landings seem to be much more picky, but here’s what has always worked for me:Īt controlled airports you don’t have to use ATC for landing, but after you land, exit the runway onto a taxiway.
![lost pilot logbook lost pilot logbook](https://img.youtube.com/vi/7TLYb0pu0FE/hqdefault.jpg)
LOST PILOT LOGBOOK PATCH
USE ATC ASSISTANCE FOR TAXIING TO GATE / PARKINGĭepartures seem seem to always log correctly since the early December patch – takeoffs and in-air departures. To make sure you meet all the objectives for a flight, keep the objectives window open and complete them all. It may be that just turning it off in the options screen still hangs up the logbook logic. Go to the developer mode menu (upper left in flight screen) and select “exit” to exit developer mode. Specifically, if you are messing with CFG file parameters and using developer mode to resync the plane, it may keep the logbook from updating. It appears that developer mode – unsurprisingly – may interfere with the logbook triggers. You can quickly identify the date your logbook started misbehaving by looking at the date of the most recent log entry.ĮXIT DEVELOPER MODE – DON’T JUST TURN IT OFF Granted, I know, that this is “just a simulator” and that we won’t be held accountable to the FAA/CASA or other regulatory bodies around the world but that is not the point - the point is that they are simply going to have to trust us! In the real world it’s a federal crime to make false logbook entries. For the minority who might be inclined to cheat, they’d only be cheating themselves.
LOST PILOT LOGBOOK PC
Please allow us pilots to edit our own logbooks as we do in the real world! If you think people are going to cheat, you’d be mistaken - I truly believe that the vast majority of PC pilots won’t cheat. My logbook has thus far cheated me out of 109.7 hours flight time, not counting today’s 7.9 hours. I feel it’s worth saying here that I’m never, ever rude or condescending to them. What’s the point in reporting bugs to Zendesk when they can’t even be bothered in replying to me? I’m talking about at least a dozen reports to them that go back over many, many months - not once have I received a reply, other than emails from them acknowledging my bug reports. I click “continue” then go to my profile, then I go to my logbook only to find a take-off from the same exact airport I just landed at zero hours and zero landings were credited! How long is this bug going to go on for? I reported this (and many other bugs) to Zendesk several times already but they never, ever replied!! All I ever get is an acknowledgement email saying that my bug reports were received. I just lost another 7.9 hour flight! Right after parking and shutting down the engines, the logbook comes up showing the correct flight parameters.