There appears to be a massive disconnect between what is logged in the “Profile” and what gets logged in the “Log Book”
This might not matter much to the hardcore sim community but I think it is going to matter a lot once the xbox launch happens and we see a lot more casual gamers pursuing the achievements. (because “Profile” logged events relate directly to achievement progress)
Over the past couple of months I have done a lot of “Personal rural bush trip” type flying. A lot of uncontrolled airfields, grass strips, dirt etc. (this issue isn’t simply related to poorly defined grass or dirt strips though, this can and does happen with hard surfaced, well defined runways)
On many occasions I will have a landing logged just fine in the Log Book only to notice that number of landings has not increased in the Profile count.
The opposite can also be true. The Log book might log no landing at all but the profile…the profile thinks you landed at the airport.
As there is no documentation for this at all it’s impossible to know if certain criteria for a “Profile landing” to count.
It seems that some will only pop if you land on a certain runway (even though this may be the WRONG runway due to wind direction) but even this is so random that I can not really be sure.
This also doesn’t appear to be related to network outages. I have not experienced any connection drop for a long time and indeed within the same session (usually the very next flight) I will try those landings again and it will eventually get logged.
There is seemingly no correlation with the “Objectives” either. All objectives for a good landing can be perfectly met…and still whether it be counted or not in the profile seems entirely random.
The profile lists number of different airports landed at though. So it makes sense it’s lower than the log book total if you land at the same airport multiple times. However, I know from my tour I’ve landed at over 7,100 different airports, profile lists 6,174, log book only counts up to 5,818.
The log book doesn’t update until after end flight, so any CTD or end process due to massive slow down will not create a logbook entry. Perhaps the profile updates every time you see the save icon pop up after a landing.
For a landing to count you need to slow down enough on the runway to count as ‘landed’. If you drive onto the taxi way at high speed it won’t count. However at many smaller airstrips it simply doesn’t work. Either the marker is in the wrong place or the landing strips aren’t defined.
Oddly on a bush trip it did count my landing on an unlisted airstrip, basically just landing in a field and finally also the take offs count. On my tour, take offs were never counted, only the first one. So in my stats I have just over 1,000 take offs recorded vs 6,000 landings. (number of succeeded take offs sits at 6,636 in the profile)
The achievements are all pretty buggy and I have no clue what planes I haven’t flown 300+ mile flights with yet for Jack of all planes, and how do you do 10 weekly activities when the activities never change!
Noticed that, there are airports that don’t log at all (Malden Glider Field) or rarely log (Madeira). There are airports that are very restrictive on landings, like EHEH. Approach straight from 300m, no curves. And you can’t even touch the grass after clearing the runway and taxiing out… I like that better actually… but these airports that don’t log 1 for any reason, there should be a black list !
Indeed. I started the process of checking the logs when I was chasing whichever achievements require those to get recorded in the Profile.
I noticed so many irregularities that I just kept checking with every NEW airport visited.
It would be very helpful if we as users could see the criteria for logging.
It may be that landing speed, wind speed, aircraft type etc are all factored in.
For example a series of really good landings that satisfy the log book may not be counted by the profile because the game considered the wind to be too high to actually land safely at a particular airstrip. (I’m guessing. Nothing seems consistent enough to draw good conclusions)
Not knowing what these conditions are is quite frustrating.
I like that better actually… but these airports that don’t log 1 for any reason, there should be a black list !