Have you used Developer Mode?
NO PC Specs:
Intel i9-9900k
Motherboard ASUS Maximus XI
64GB (4X16GB) DDR4Corsair Vangence @3766 MT/s
MSI GeForce RTX 3090 Suprim X
OS install disk: Samsung Evo 970 Plus, 500GB nVme PCIe 3.0
Sim install disk: Samsung Evo 970 Plus, 2TB nVme PCIe 3.0
Windows 10 Pro (Version 21H1, Build 19043.1415)
Simulator Version 1.21.18.0 (Steam Beta)
Nvidia Driver Version: 496.76 Aircraft:
Diamond DA40 TDI Area of the World / Flight Plan:
Europe, Austria, short flight from LOLO to LOLT Airport (If applicable):
LOLO 3rd party addons you were using at the time (Mods/add-ons/community content)
happens with and without Mods, related airport mods:
LOLT - Seitenstetten: LOLT - Seitenstetten fĂĽr Microsoft Flight Simulator | MSFS
LOLO - Linz Ost: [LOLO] - Linz Ost Airfield, Austria fĂĽr Microsoft Flight Simulator | MSFS Peripherals:
Logitech X56 HOTAS, Thrustmaster T.flight rudder pedals, Streamdeck Feedback/Bug Description:
If I fly, lets say from LOLO to LOLT (but it doesn’t matter since I have the bug with each flight), I get an entry from LOLO to LOLT with the correct flight time, but I get an additional entry with a “ghost flight” from LOLO to LOLO with 0 minutes and no start or landing.
I am not sure if this is related to the fact that I also do not get the flight summary after turning off the plane (now it sits in the sim waiting for me to hit the ESC key)
This was not present in the regular SU7 build. The option to show the logbook entry after shutting down the aircraft is ON. The logbook however does not show up at the end of the flight → maybe this is related to the wrong entries in the logbook.
Optional
[X] Multiplayer session or [ ] solo flight
Multiplayer settings: [ ] Live Players [X] All Players [ ] Group Only
Weather settings:
Live weather Server: [ ] East USA [ ] North Europe [ ] West USA [X] West Europe [ ] SE Asia
That is present in the regular build. It happens when you have the option to have the logbook pop up when ending a flight turned off, which came with SU7.
All they have done is have the sim silently press the Continue button on the logbook pop up screen, and just as it did pre-SU7 is it generates a 0 length log entry if you don’t fly anywhere.
Turn that option back on again, and when you end your flight, and the pop up appears press Continue, and it will do the exact same thing. Press Main Menu instead, and it won’t.
That option only solves one problem, but not eliminating the empty log book entry issue.
I wish I could go back in time and advise myself to always use LittleNavMap as it captures a log more reliably. I’ve been lucky that my logbook has never reset to 0 hours as it has for some but I have lost flights due to CTDs. With LittleNavMap at least it still captures the flight even if there is a CTD though it may not capture the landing if it CTDs before that. For me I lost a lot of flights because of CTD when just trying to exit the flight after landing.
I’m now gradually manually entering in old flights from MSFS into the LittleNavMap log, and going forward always tracking flights with it. Bonus, LNM also allows exporting to csv so you can do some log analysis with spreadsheet which is not possible with the built in logbook. I also track flights with Volanta but as far as logbook functionality LNM is the best.
The point is, that option is on as it was in SU7. Therefore this thread. It seems to have issues in SU7 beta
I’ll update my initial post to make this clear.
My Logbook has loads of these 0 hr entries. Is it really that hard to update the sim to ignore anything that’s 0 like has been suggested. Oh and it’s certainly not just the hotfix beta that does this.
Yes that is true, but only when the automatic logbook pop up was DISABLED. With the beta now the behavior is also visible when the automatic logbook pop up is ENABLED. This was not the case in normal SU7 - at least for me.
I just finished a flight with logbook ending enabled, it did not log a ghost entry, like it does when it was disabled for my previous flight (I’m in the beta via Steam):
I doubt it’s plane-dependent. I’ve had this happen since SU7 with every plane I’ve flown (DC Designs F-14 and F-15, SC Designs F-16, FlyingIron P-38L, Volocity, Pitts, etc).
How long did you wait before actually exiting? I normally leave this function on (and ignore the “ghost” entry in the logbook) but I noticed yesterday that if I exited the flight section almost straightaway there was no nil entry.
My preference would still be an option to delete unwanted entries - having the sim doing it automatically would be useful but would probably need more intensive programming than a simple delete function.
It’s not plane dependent. It’s dependent on whether you press the “Continue” or “Main Menu” buttons on the logbook popup screen at the end of the flight. And if you have that new SU7 option turned off, to supress the popup then it simply presses “Continue” for you anyway, leading to the empty logbook entry.
I believe that but has been around since release. I just ran a search for this behaviour, and I found something I posted in October last year, but it looks like its a variation of what we have now:
I think those shots are from the pop up screen rather than the logbook proper, so when I get home I will search for takeoffs from EGUN to see if there really were zeroed log events from that time.
Required
Optional
