vAMSYS 5.2.2
Bug Reporting
[Image: ]
When you see a message like this - please do click where it says ‘Please Click on me’ and log a bug report, describing what you were doing when the error happened.
Bugs submitted this way do not need to include VA Identifier, but we do need a description on how you got to the error so we could reproduce and fix.
It is very imporptant bugs are logged - when you get this message - please make the effort to submit a bug report - if it’s reported, it can be fixed. If it’s not reported - it will not be fixed any time soon, if ever.
Tour Logbooks
We fixed couple of issues yesterday and today with Tour Logbooks not getting the progress updated or carried over from 5.0;
Should you or your pilots experience it, first step would be to reprocess the PIREPs eligible for tour in order - leg 1, then leg 2 and so on - this should add it to activity logbook for the Pilot.
If that fails - please log a bug in Featurebase containing - Activity ID, Affected Pilot Username and VA Identifier.
Nightly Jobs - Discord Stats
For Virtual Airlines who have UTC as their timezone (new in 5.2), the midnight job and discord statistics messages did not fire at midnight UTC. We think we resolved this issue and it will run as scheduled tonight.
You may have noticed a drop in Pilot accounts - this would be because of how Frozen accounts are handled in 5.2 - they are now removed after 2 days instead of 60 - the nightly job which we ran at noon to catch up will have deleted all Frozen accounts which were over 2 days old, but younger than 60.
Other changes and fixes
Added a fallbabck in PIREP Processing when we do not have touchdown position reports, so that PIREPs do not get rejected/invalidated with null landing rate.
Fixed PIREPs not being logged towards Tour completion if the Tour had restrictions configured. If you have any PIREPs like this - reprocessing them in Orwell ought to add them to activity logbook.
Fixed an issue with Airport Import unable to process SimBrief settings
Fixed an issue where Airport Manager Bonus Point setting would not get saved in Orwell
Fixed more lazy load issues (you don’t see it as errors, but we log occurences to improve vAMSYS as it basically reduces number of database queries we make)
Fixed Flight Length and Flight Distance fields not auto-populating on route import
Fixed Altitude field in import not being parsed from FL380 to 38000 and similar
Increased the Live Flights histogram in Orwell dashboard from 2 weeks to 1 month
Fixed an issue with ‘Flights From XXX’ table where it would not show some routes due to tag issue.
