This appears to be the sim compressing the logbook data to keep it within the 16mb limit, the one that looks to be causing loss of entries, and then taking longer now to “decompress” before displaying the logbook.
It would have been better just to up the data limit, but then you would have several million users all taking up an additional amount of cloud storage, perhaps not much individually but cumulatively a considerable amount.
To me I can’t see why it isn’t stored locally on the users machine - but that goes against MS “everything in the cloud” philosophy.
This whole idea of everything in the “cloud” is absurd. This compressing idea, and locking application up, with no PLEASE WAIT, is a IT rookie mistake. Not a good statement of “expertise” for Asobo, in my opinion.
The way the Logbook code works is it reads all logbook entries and then "post"s them in HTML format. With a lot of entries, it will take a long time to load/display.
If you search, the search routine will also read and print all entries in HTML but those that do not meet the search criteria are appended with “hidden” flag. But still, all entries are listed in the Logbook page in HTML, even if only a few meet the search criteria.
The best way to solve this, as I thought to myself when dealing with this a year ago, is to only “post” what can be visible on your specific screen size. Say, if one page on your screen is 20 entries, only publish 20 entries. When you scroll down or up, reload the next/previous 20 entries (or make scroll only 19 so you can still see the last entry of the previous page). That will make it fast. Even search can be the same method.
But no. They will not take any suggestions. They want the community to solve these problems for them.
BTW: I tried to do the above but a new update changed everything (code optimization) and I dropped the idea. I realized I would have to rewrite too much to make it work. I also tried to export the logbook so I could edit it. I couldn’t get their code to work for me. I also tried to delete zero time entries to reduce the number of entries I had, that was maxing out the file size limit.
But yes, you’re banging your head against a brick wall. MS seem to have some sort of philosophy that things must only be done their way. Bit big brotherish IMO.
Fortunately I only check the logbook once a session to transfer the times to my own logs.
The Logbook takes way more time to load now. Before this update, it was bearable. Now it is really, really slow. 2500+ entries in my logbook and it takes 1:05 to load. That is one minute and five seconds to load, which is a lifetime .
My 2500+ entries (that was what it was July of last year). I kept an Excel logbook after about a month from the last entry. I have 871 new entries since then.
Even if I were able to import my logbook, the load time would be even longer.
Another complaint me and others are having is the fact that Search does not re-calculate the totals at the bottom. This would be nice to see how many hours I have in a specific plane.
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes, on the public GA release of SU13, Xbox series X
Provide extra information to complete the original description of the issue:
if you click on logbook, there is a 20-40 second freeze in mouse activity with the logbook saying No Entries… then the logbook will populate with all the entries once it unfreezes. Please can you restore the previous behaviour of the logbook or do something to remove the freeze?
If relevant, provide additional screenshots/video:
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:
Yes
Are you using DX11 or DX12?
DX11
Are you using DLSS?
Yes
If relevant, provide additional screenshots/video:
I have the same problem as many others since latest update. Logbook takes one minute
30 seconds to load. All logbook functions…eg change from “all” flights to “ground to ground” etc.
also scrolling through flights…very slow to activate, many seconds.
How long do you wait? Mine (on a Xbox Series X) appears to lock up but after about 2 minutes it populates and responds. Others have reported even longer delays.
There was a bullet point in the latest release notes for SU13 that Logbooks with 1000+ entries are now compressed and that’s why there’s such a lag in opening them. It’s not optimal, but it appears to be the expected behavior until such time that they can rewrite the whole tool.
I have flown two flights since a relatively painless upgrade to SU13.
At the end of both flights I have looked at my logbook and encountered the following issues.
Logbook took a long time (45 secs) to show any entries (used to be about 5 secs)
Whilst flights have been registered, neither flight recorded any takeoffs or landings. I sometimes lose takeoffs if I dont follow correct departure procedures but never lose landings.
noticed this myself today, it takes forever for the logbook to display now, at first I thought the app was hung. for me it is persistent, super slow every time I try to view the log since the update.
Your topic has been moved into the #gd-commsupport:menus-and-activities subcategory of Community Support where the logbook is discussed, as this seems more an assistance request / “Anyone else experiencing this?”.
The Bug Reporting category is for posting suspected or confirmed bugs that other users are able to reproduce using the template. When reporting in bugs, please ensure you only include a single issue per topic.
You may wish to check out this for the loading issue:
It’s also important to use the search function. If any topics exist, consider contributing to those. If you believe it is a new report, then create a new bug topic using the provided topic template.
it has been this way for me from day one on my Xbox (May 2023).
The first few weeks I flew traffic patterns only just to learn the ropes and get used to my aircraft (Bonanza V35B). My sessions varied from 20 min to 1h30min.
The records in the logbook read 1 take off-15 landings, 9 take offs-2 landings, 0 take offs-0 landings, 19 take offs-5 landings …etc. Quite randomly. Only when I fly from aiport to airport then the logbook records this as 1 takoff-1landing… well mostly. Sometimes this is wrong too.
No idea what causes this, its definitely not due to not following procedures and such.
I have decided to ignore it, since there seems to be no way to do anything about it.
I just watch my hours of flight time grow now
There is a very interesting thread on “what constitutes a loggable takeoff and landing” I did take part in it myself.
If you follow the correct ATC procedure on takeoff for manned and unmanned airfields which includes following the taxiway guidance markers, notifying ATC of taxiing and takeoff intentions etc. you will normally get given a takeoff in the log and as I recall landings literally just require you to land on any destination field runway.
I have two flights where all procedure were followed and no takeoffs or landings were logged.
This is new, to me at least.
.