Airport: Weekly cycle first movement & Airport Profit Split, decrease in PAX payout

Dear SimFly. I noticed today that the airport payout has changed. Normally, the PAX payout is not like this. Is there anything changed? Please kindly help clarify, Thank you very much :slight_smile:
Please see below:

5 Likes

I believe that out of respect and ethics, the community deserves a proper explanation. If they break a bone without any anesthesia, the pain relief should be just as strong.

Hi,
we identified the issue about 5 minutes ago thanks to your reports.
We’re currently investigating the situation — today’s deploy was a major one, especially on the Brain side.
As soon as we have updates and the situation is restored, we’ll let you know right away.

2 Likes

Dear Karim,
Thank you very much, for your prompt action and update on this matter. Please kindly update once everything is back in place, cheers.

3 Likes

Thank you! We hope you can resolve this. Best regards.

1 Like

I hope so too. After a flight of 4,5 hours, receive 0,98 PAX is something annoying. I can not spend so much time for this…. sorry. And for the accumulated hours (many users involved) in all this SimFly voyage.

1 Like

We’re working on it — as we mentioned earlier, this issue was caused by a major update released today.
A reduction in PAX Token earnings compared to what you should have received has never happened before.
We’ll update you as soon as it’s fixed.

3 Likes

Hi everyone,
the issue with reduced PAX Token earnings has now been fixed, as well as the problem with license and aircraft selection in missions.
Everything should be back to normal.
We look forward to your feedback!

1 Like

Thank you so much. Will report you back if found anything unusual. :folded_hands:t2:

1 Like

Greetings!

Today I noticed that my registration in the licensing system has disappeared.

Thanks for the report — I’ve forwarded it to the development team to get it resolved as soon as possible.

1 Like

We apologize for the recent issues and inconveniences — they were caused by the latest optimizations made to certain areas of the platform, as we’re still in a phase of active development and new feature releases.
These updates were necessary to improve overall performance and stability after several deploys, but unfortunately, they introduced some temporary problems that we’re already working to resolve.

Of course, this is not meant as an excuse, but as a commitment to do better.
From now on, we’ll take more time to test and verify each update before release.
We’ll soon reach a stage where fewer changes will be needed, and therefore fewer issues will occur.
We’ll also be more careful in the future to ensure that similar situations don’t happen again.

3 Likes

Thanks, friend. Best regards!

1 Like

The issue you identified has been resolved.

1 Like