hehehe…
Pilot’s FS Global Ultimate Next Gen mesh and Horizon sim’s VFR GenX3 all volumes.
Granted the autogen does not look great, but the global mesh is orders of magnitude better than what’s in msfs20 right now. VFRGenX3 uses imagery that was licensed/bought from Get Mapping.
Still at low altitude, say below 1000ft it looks kinda’ flat, but it looks great at and above ~1500ft, plus it’s all offline.
It’s the same as looking on google maps if that’s your thing.
No,m that’s not ground time. That’s because you probably accidentally hit continue, then exited to main menu.
Your initial flight is logged, as you can see from you penultimate flight. Then the final flight of 0 minutes has the same departure, and destination as the previous flights destination, KDVT.
It has nothing to do with ground time, just how the flight logging works.
I know because I did this accidentally the other day as SU6 swapped the Main Menu, and Continue buttons. Hitting Continue logs the flight you just completed, and effectively starts a new one. If you now hit Main Menu, you didn’t fly anywhere so it writes a new 0 time log entry.
Looks like we’re going to have to wait a little longer for MS/Asobo to correct this issue with the logbook pop-up screen appearing during shutdown because it wasn’t done in Update 6…
I would like to see a dedicated keyboard shortcut to call up the logbook.
If that was implemented, I could go through shut down procedures at my pace, and once done open the logbook.
I would also like to see a function to delete an entry. This applies in particular to the time I spent between the logbook appearing now and (after I press “continue”) the time it takes me to completely shut down the a/c. This time is now logged as a flight with zero duration and zero take off or landing (rightfully so, but the whole entry into the logbook is totally useless).
Like I said: I need to press “continue” for a complete a/c shutdown. In many planes, killing the engine is enough to trigger the Log Book screen - ie. too early
There’s something I haven’t tried. As you may know, enabling dev mode stops your logbook from updating.
I wonder if you finish your flight, hit the Continue button, then enable dev. mode so the zero entry can’t be logged, it may still log the first flight correctly.
It does work, however it seems to create an empty log entry when you exit to the main menu, as if you had pressed the Continue button, and then Main Menu.
There’s probably some Chinese proverb that states that: “if you take the time and effort to fix one thing, at least make sure you’ve fixed it well”. Doesn’t apply here obviously.
Yeah they finally gave the option to get rid of it, been a long time coming! This never meant the logbook would work correctly since it never has. If you want a proper log then I suggest you get a logbook and write it down, it would be more accurate and fun that way anyway.
While I appreciate we now have the toggle to stop the logbook from automatically opening, would it be too much to ask that it can properly sense takeoffs from untowered airports? It seems to missing landings as well. I use pilot2ATC and not the in-sim ATC, even though Pilot2ATC is a more accurate representation of proper communication, it seems to really to mess with MSFS ability to log take offs and landings
Turning the new feature off it correctly logs my single flight when I return to the Main Menu. I’d rather have this than have them silently hit the Continue button to hide the window from appearing, rather than actually stop it from appearing at all, to block those zero length flights from filling the logbook.