Device: iPad
Operating system: iOS
I posted a while back and am still having issues with landings counting. I followed all the steps someone had listed including landing past the threshold.
I did find something curious.
I went to solo mode with landing count turned on, on the bottom of my display.
Even though solo mode doesn’t register the session landing count in your accumulated count for live flights, the counter algorithm within the solo session presumably registers landing by the same criteria as for live flight (the count is just lost when you leave the session).
Anyway, with two different aircraft I was testing (using short final), I was getting a count registration for maybe 3 out of 4 landings, but consistently getting non-registrations about 1 out of 4 times (perhaps even a bit more frequently), even though I was within the landing zone and otherwise within what appeared reasonable descent rate etc.
I just went back a 3rd time. Same result: regularly missing landing detection with no identifiable cause.
I feel like the communication between the server and the system would be much more precise than the one provided in pilots’ displays. I have tested it before, and the information shown on pilots’ displays seems to usually be a rough estimate of what’s going on-when I tested different aircrafts’ overspeeds on Casual for some aircraft, despite actually flying 350 knots (or whatever the limit was), and showing exactly 350 on the HUD, the display at the bottom of the screen varied and often the alarm came up as early as 346 knots, and as late as 353.
But, presumably the pilot’s device is telling the server what reality is calculated locally on the user’s device (maybe I’m wrong??).
I frankly don’t believe that. I would need strong evidence to accept that. The IAS on the HUD from all my experience is always in lock step with the IAS on the bottom data strip.
And I’ve never seen a landing recorded on the bottom data strip that didn’t get communicated to the server in live mode (assuming no interrupt in network communication).
Of course I don’t know the precise inner workings. This is an assessment/judgement on my part.
Landings I experienced not being registered locally may mean nothing, but my hunch is that it more likely than not has some relevance.
The point of that being, that although server-system communication would be very strong, and the only way it could fail being a network reason, the code for intra-device calculating is more simple (either it works or it doesn’t), and there could be more factors in play when it doesn’t work or is inaccurate.
I don’t know. Have you tried to test for missed landing count under the conditions I stated or in live flight?
I need to keep it simple by looking at the testable evidence.
Testing one more time in a consistent environment (aircraft and location, different sessions, but not exiting IF):
I continue to get regular missed landing counts in solo mode (with the bottom screen count variable active). I get a count or two, and then not, and the cycle repeats.
So far, however, I cannot reproduce this in live flight, that is, no missed landing counts (from new testing on top of my entire experience since first using IF). And the server total recognizes all the counts accumulated during my flight.
So, in other words, your landings in multiplayer are registered correctly, even in the pilot screen, while your solo landings are not? That could be explained by the fact that only live needs a direct connection to the server for these types of things-in solo, where the entire process is internal, could be holding more inaccuracies.
Yeah, but my data size for the current test in multiplayer is only 5 consecutive landings. 5 out of 5 registered correctly. I maybe did 30 landings or so in solo.
The op has an issue with landing count (in multiplayer) and a compelling couple of screen shots.
I’m curious about connecting the dots to the op’s support request.
I get 5 out of 5 correct registrations (and a memory, if correct, of proper landing registrations in multiplayer over a long period of time). The op is showing an anomaly. Something has got to give.
More data(?)
edit: It’s also important to note the op’s replay screenshot doesn’t show any server disconnect events for the duration of the session.
A search of missing landing count issues shows most of them explained away as resulting from disconnect.
And in fact, the op’s session ending stats show credit for XP and flight time, with zero landings, even though the replay shows landing in the landing zone.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.