Jump to content

Lukas Jankauskas

vAMSYS Platform Administrator
  • Content Count

  • Joined

  • Last visited

  • Days Won


Other groups

vAMSYS VA Owners

Lukas Jankauskas last won the day on May 13

Lukas Jankauskas had the most liked content!

Community Reputation

4 Neutral

About Lukas Jankauskas

  • Rank
    vAMSYS Developer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi! Soundpacks are configured by the Virtual Airline using Orwell -> Management -> Pegasus Sounds. To enable them, or set up a custom soundpack, as a pilot - login to Pegasus, navigate to settings. In the 'Sounds' section, you can enable announcements set up by the VA, or set up your own - be sure to follow the 'Custom Soundpack Guide' provided if you go down that route.
  2. vAMSYS 3.8.5 Phoenix: [Fix] Fixed URL to the forums for the description of Account Merge feature. [Improvement] Added error message when user tries to merge account with himself. [Fix] Fixed an issue causing inability to delete bookings, throwing a message saying 'Booking Not Found'. [Improvement] Reworded yellow notification when viewing a PIREP which is pending review. It no longer asks for a comment to be left if the PIREP does not require one. [Improvement] VAM-94 Pilots will no longer be able to delete bookings when we det
  3. Account merge feature is intended to be used by pilots who have multiple user accounts. For example, I have 2 user accounts - one under a@domain.com, second - b@domain.com. User a@domain.com has pilot accounts VAM0002, ABC1249. User b@domain.com has pilot accounts VAM0004, DEF1587. Instead of maintaining 2 accounts and 2 logins, I can opt to merge them into 1 login under same email. How to merge 2 User Accounts? Login using your 'main' account - main account is the one you wish to retain - in my example, it is a@domain.com. Navigate to My Settings ->
  4. If you are denied registration for a particular VA, you need to contact the VA in question.
  5. Further to our communication in 2020 on Pegasus release, we are now announcing end of life for smartCARS support. As of 22nd April, we will render no support for PIREPs filed using smartCARS. Previous PIREPS filed using smartCARS will remain open-able at least until vAMSYS v4 and will retain scoring/processing support until 22nd April. Past this date, we will offer no ongoing smartCARS support. If you have not already – it is now definitely the time to upgrade to Pegasus – our in-house tracker. If you have Issues with Pegasus, you can report them using the support links in Peg
  6. During our Christmas Message posted at Discord last year, we announced our intent to stop active v3 development and focus our efforts on v4 at the start of 2021. But we found ourselves not quite done yet and you have offered us some amazing suggestions, which we worked to implement in v3, pushing away our intended end of active development date to the point where most of you probably do not even remember we announced in the first place. As of 22nd April, we are stopping active development of v3 and refocusing our efforts to vAMSYS v4. Be not afraid – v3 is not being forgotten – it w
  7. vAMSYS 3.8.4 Aircraft type filtering is back! Phoenix: [Feature] Aircraft Type filter in Flight Centre -> Book Flight [Feature] Aircraft Type filter in Flight Centre -> Destination Map
  8. vAMSYS 3.8.2 Vulcan: [Fix][VAM-56] Internal reporting issue by trying to load a file on certain endpoints Phoenix: [Fix][VAM-79] Removed broken Report a Bug link [Fix][VAM-59] Flight Map should now correctly center over active flights - no matter where in the world they are [Change] Increased max boundaries on flight map
  9. vAMSYS 3.8.1 This is internal change to accommodate new server structure and there are no visible changes to any users.
  10. vAMSYS 3.7.3 Phoenix Change: We are no longer sending out emails for every PIREP status change - option to receive email when PIREP was filed, completed, accepted, rejected, invalidated have been removed. Change: Pilot My Settings page email options have changed - PIREP Emails have been renamed to PIREP Needs Reply. Change: Display on PIREPs pending a review. The counter of the queue position you are in now excludes PIREPs needing a reply from Pilot and now depicts your position in the queue as if they did not exist. You can be queue-jumped if some of
  11. vAMSYS 3.7.1 This patch release is predominantly about notes - there are new options to keep internal notes on a PIREP - Staff can use it to note down why, for example, a PIREP which would ordinarily be rejected got accepted etc. This feature needs to be enabled. Also, there is a new Pilot Notes function enabling Staff to leave notes on a Pilot level - they will be shown on each PIREP review. ------------------------------------------- Changelog: Phoenix: Change: View More button at the bottom of Current Flight List removed Change: Current Fli
  12. Minor Release 3.6.0 - Manual PIREPs This change is predominantly focused on our commitment to deliver outcomes of the Manual PIREP Consultation. Two big changes: Manual PIREP Import PIREP Claim System - very much in Beta at the moment, with improvements based on feedback and use. Eventually, we expect to replace existing Manual PIREP facility with PIREP Claim System. Full changelog: Orwell Fixed METAR and TAF retrieval in applicable pages. Improved Airport importer when deleting airports - it will now delete orphane
  13. How to enable the system? VA Owner or a member of Staff with Management access needs to navigate to Orwell => Management => Airline Options. Scroll towards the end of the page where 'Miscellaneous Settings' are located. Toggle 'Enable Claims System' switch if it is not in the 'on' position already. Click Save. How to access the system? Once the Claim System is enabled, it can be accessed as follows: Submissions by Pilots => Phoenix -> Flight Centre -> Claims Reviews by VA Staff with PIREP Review access => Orwell -> PIREPs & Liveries -
  • Create New...