we have just released the new SimFly client version 1.2.2.
This version fixes several bugs and introduces important improvements:
In rare cases, a landing rate of 0 FPM was being returned. This issue was caused by an anomaly that we have identified and fixed.
Client performance has been improved thanks to the introduction of a local cache for the main MSFS flight settings, which is especially useful when dealing with unstable connections. This improvement also resolved an issue related to the “engine fs_prop_rpm_1 not found” message, which in some cases prevented missions from being correctly completed using the “End Flight” button.
Once the stability of this solution is confirmed, with the future version 1.2.3 we plan to extend the local cache to other simulators as well, such as X-Plane and Prepar3D.
Note: please remember not to update the client while a mission is still active.
Complete the ongoing mission first, then update the client afterward.
We recommend installing this new version and we look forward to your valuable feedback.
Hello,
It's always annoying when you're in the middle of a flight and then the update is installed. Of course, the mission was simply aborted. And that was just before landing. I knew an update about this was coming this week, just not exactly. But it would be best to add a short informational message beforehand so that people don't even start a flight in the first place. This would prevent a lot of frustration. Thank you.
This update should not have canceled any ongoing missions, as the update prompt appears when opening the client and asks you to update to the new version.
Did you update the client while a mission was active?
Hi Karim,
No, I started the flight beforehand. The mission was simply aborted without me pressing anything. Then I got a message that the update for the new client had been installed.
Yes, they have already informed me and verified the issue. It is related to a problem we resolved about a week ago with the API keys, and they noticed that you haven’t updated yours yet.
In any case, they will contact you directly to provide more information.
I just wanted to let you know that it's better to add an informational notice to the map before installing an update. Past experience has shown that even minor updates can cause errors and problems. This way, user frustration is avoided, and issues can be resolved more quickly and effectively.
Best regards, Slotty1805
We do this whenever we know that a deployment may affect an ongoing mission, except in very rare or extreme cases. Minor fixes are almost released daily, but we are trying to group them and release them together with major deployments, so users can be informed in advance.
In addition, we are currently developing a new system for major deployments, which in most cases affect the moment when “End Flight” is clicked.
The system will be very simple: if a deployment is in progress, when “End Flight” is clicked the action will be temporarily blocked and a message will be shown informing the user that a deployment is ongoing, asking them to wait 5–10 minutes. After that, the mission can be completed correctly.
We wanted to inform you in advance, and as soon as the system is ready, we will notify you.