Yes, me too. The same problem.
Hi,
@Cliffyboy1962 it may well be that following correct procedures has an influence on this problem, but not generally so.
Most of my flying is VFR from and to uncontrolled airfields. Even if I follow every rule to the letter take offs and or landings are not logged correctly sometimes.
And on the other hand - If I ignore ATC/radio communication completely and choose my own way for taxiing this is sometimes logged correctly.
And also - even if I land on the center line at my destination it is sometimes logged with ā(vicinity)ā added to the airfield ID.
Touch and goes also seem to be a big Problem for the logbook.
As I said above - Iāve given up on this. 
But Iāll have a read in the thread you mentionedā¦ you never know 
Regards,
Frank
Did another flight this evening and logbook still took a long time to load, however, this time both takeoff and landing was logged, so that problem seems to have resolvedā¦until the next flight.
Interestingly, the flight was VFR unmanned to unmanned and I DIDNT follow any taxi markers as none were offered. Carried out correct ATC protocol for unmanned field and logged a takeoff !
I think inconsistency is the keyword here.
My logbook is at least logging T/Oās and LNGās again after a long dry spell (22Feb23) so Iām happy to just have my hours logged once again. Let face it Rome wasnāt built in a day.
Thankful for this thread as I had no clue as to what was going on. Entering logbook yielded an unpopulated page. First time Iāve encountered this. Tried to exit but nothing clickableā¦page āfrozen.ā
Resource monitor showed MSFS as ānot respondingā necessitating hard shutdown. Rebooted PC, relaunched and encountered same issue. Rinse and repeatā¦same issue. Fortunately encountered this thread and next time I simply waited on the seemingly frozen logbook. Well lo and behold 4:30min later it populated my 5000 entries. Canāt imagine how many other people have performed hard MSFS shutdowns needlessly after encountering the same problem. Asobo must fix this ASAP.
1 Like
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
NO
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
Yes
Brief description of the issue:
Hangs on loading log book. You think the sim has hung and crashed, but if you wait long enough, 30 seconds or more it will eventually show up. At first it will say no entries, then 30 or more seconds later it will populate and show over 2400 entries. Clicking on the slider to partial or ground to ground takes another 30 seconds or more and results in the same number of flights. Tried signing in and out and same problem. Happens in normal mode or safe mode.
,
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Start up sim, go to People, then logbook.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
lCurrent
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OPās steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
1 Like
Same issue since last update. It takes 35 seconds for the logbook to open.
Do you have the same issue if you follow the OPās steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
I noticed problem after upgrade from Windows 10 to Windows 11 and Sim update 1.34.16.0 I have over 3600 Hours of flights in log book.
Are you using DX11 or DX12?
DX11
Are you using DLSS?
No
If relevant, provide additional screenshots/video:
Same issue (logbook shows all flights but takes 30+ seconds to load) 100% of the time after the latest update. Slightly annoying.
What boggles my mind is that the decompression happens every time that the Logbook tile is clicked. This tells me that the decompression is channeled to a temporary RAM cache released to garbage collection every time Go Back is clicked when viewing the log.
Excuse me, but this seems like a terrible idea. A decompressed logbook with 3,000 rows of just alphanumeric data probably uses around 1 MB of RAM, a minuscule amount of RAM compared to what MSFS uses while flying, a drop in the bucket if not a drop in the ocean. Why release this data to garbage collection when exiting the logbook?
The decompressed logbook data in RAM should not be released to garbage collection until Quit to Desktop is clicked and confirmed. The logbook data in RAM would have 1 row added after the end of each flight to keep it current.
With all the decompressed logbook data in RAM after the first time the Logbbok is viewed, the logbook would render at least as fast as it did before SU13 in all subsequent views in the current MSFS instance. If the logbook data decompression process was moved to be part of the MSFS startup process, there would also be no delay the first time the logbook is accessed in an MSFS session.
Also, why it takes 30 seconds or more to decompress only about 1 MB of alphanumeric data is a valid question.
3 Likes
I keep losing flight hours and keep freezing at the exit of the flight. Everything after this ā ā ā ā SU13!
1 Like
Same here.
Bug is still there in SU14 beta
My sim stopped logging time back in April. Approx 830 hours, It got fixed with the last update. But now takes up to 5 minutes to loadā¦.sim is frozen as it loadsā¦
This 'ābugā is a SU13 āfeatureā. Compressed logfile as some peopleās logfiles had reached the 16MB limit and had stopped logging flights. It gets decompressed every time you click on logbook.
This āsolutionā was because many users (myself included) hit that 16MB limit of storage of logfile so didnāt get any flights stored for 2 months in my case, and is now fixed.
Other than the speed of decompression (in my case it takes 2min!), the main problem is the fact they didnāt put a message up saying āplease waitā or āprocessingā and instead it defaulted to āno entriesā and system hang until logfile decompression ended.
Please donāt fix this by leaving users with no logged flights again.
I had never had an issue with flight logging previously (only have 555 hours since launch), but experience the slow load that everyone is speaking about after sim update 13, plus now it stopped logging since October 11.
Itās currently logging flights for me. unfortunately their one glove fits all (compression/decompression) approach to fixing the 16MB limit is the reason everyone is having the slow experience with this.
I have 1500 hrs logged in my logbook and probably about 100 more missing that didnāt get logged between July and August this year because of me hitting the 16MB limit.
Hi
Im running the version 1.34.16.0 and I have experianced a significant delay when loading the logbook since the last version upgrade. It takes aprox 25-30 second longer for loading the loggbook than before.
I cant even load my logbook now it just causes the sim to not respond and I have to end task in the Task Manager so I donāt bother trying to look at it anymore. This started since last World Update. It doesnāt affect my Hours flown, that still gets updated.
1 Like
How long have you given it to respond? FS āhangsā for me for a full 2 minutes when itās decompressing the logbook file, but it always comes back eventually and lists the file contents. If you have a lot in your logfile it does take a while to decomress it. Not sure why. Introdued as a SU13 āfixā for large logfiles.
1 Like