Hi devs, just updating that landing score again with issues on airbus.
After update was fine, now those last days back again with wrong scores.
in others thirds partys: ex: -250 on simfly goes -450
Also for Boeing and I have reported both planes last week via ticket.
No update received yet.
Hi, in the next few days we will verify this and keep you updated. Thank you for the report.
May I ask which third-party apps you used for the comparison?
Also, which flight simulator are you using?
1 Like
third-party apps:
Volanta and vabase(from tanoairlines)
1 Like
Regarding the landing rate, I notice many times SF’s detection will be different from LRM or Volanta, but sometimes it is not, so I would like to share my experience about the landing rate detected by SF.
After I’ve been observing and testing for landing rate detected, I can say SF’s algorithm has both accuracy and deviation in the following ways. (this is from my own opinion, and it covers both MS2020 & XPlane 12)
For the landing detected, I think SF’s detection rate will come close to very accurate as following:
- If the aircraft sinking rate is not too fast when the plane is about to touch down, in other words, you flare the plane nicely, let it almost float (or give it just a little bit time) before the wheels touching the ground, I notice that FPM detected will be predictable by looking at the instrument.
If you look at the arrow pointed to “100” indicator, FPM rate will be between 100-200 depending on how you hold it (could be drop below -100 a bit if you still pull a stick), this is something SF’s detection is very good and the behavior is the same both MSFS2020 & XP12. (In this scenario, Volanta will result in softer rate, maybe around -65 to 80, which I think, is not accurate, SF’s detection is better since we can land by using instrument, not land by feeling)
-
But if the sinking rate is too much, the aircraft comes down fast and then touch down, even the indicator is the same as picture, the landing rate might not fall in between 100-200. (It might be more than 200 or less than 100, depends on your holding). This behavior is the same as Volanta.
Next is bouncing, I observe from the replay when bouncing detected, and it is really bounce, even just a very very little bit. (Sometimes it interprets as bounce but it is the runway slope itself, not from the landing). There is a scenario, where the main wheels are just ripple, not float after touch down, but just ripple, SF will interpret this as bouncing.
So, I think if this sensitivity can be decreased just a little bit, that would be perfect. (Volanta cannot detect bouncing unless it is really noticeably). Overall, I think SF’s detection is good enough for FPM rate when flaring the aircraft appropriately. I like its accuracy or predictable behavior.
This is from my opinion only, and I’m willing to hear from the others what do you think. So we can share it and find the appropriate algorithm fine-tuning together.