All Activity

Hello, I am currently working on Microsoft Flight SImulator 2020. And I fly with the A320 NX from FLYBYWIRE. Can I fly with it to other destinations than Great Britain?

Bonjour Dès que je clique sur "réserver un vol", la page qui s'affiche comporte un fond bleu en guise de carte avec mon aéroport de départ et les onglets "sélectionner l'aéroport" et "filtrer par avion" sont vide. Impossible donc de réserver un vol. Merci d'avance Denis Cellier VOE0395

I get this for Virtual.Cargolux. TUI and RYR is fine

Dear, I can't see the SOP as I'm still waiting for the confirmation email. Since yesterday, I clicked on resend email but i get nothing.

Hey! Do visit https://apply.vamsys.co.uk

Hello sir, i want to open my virtual airline with vamsys, my VA is certified in IVAO and i want information, thanks for all

great, i'll give it a try, many thanks

Hi Luca, You can merge them. Navigate to your settings once you login to one of your accounts to start the process.

Hi, You need to start tracking in Pegasus.

Hi everyone, during the course of many years, I do not know how but I realized the I have 4 different account with different email, I couldn’t not find anything precise, I was keen to kno if there was even way to delete those who are not “in use” Thanks in advance Luca

How do i get myself to show up on the flight map. i am filling the flight plane its says its booked i load in but im not there.

We won't be updating this thread any more. Please use the new Release Notes page to see the latest changes to the platform. https://community.vamsys.io/release-notes

This evening we completed an upgrade to the vAMSYS Community Forums which was the last in a series of planned outages which allows us to deliver changes to how we provide release notes (changelogs) and our knowledgebase. Forum version upgrade Probably the least significant change of the evening, we have upgraded the software powering the forums to the latest version offered by the third party provider. There should be no material change in functionality as it's just a patch release. Changelog migration Currently, our changelogs are stored in one long forum post which becomes more and more painful to maintain as we release more functionality, and is not very user friendly (as the newest releases are at the very end of the thread). We have therefore taken the opportunity to use the functionality originally designed to support the knowledgebase to also provide a better platform for our changelogs - which we have now renamed to Release Notes. The Release Notes should be much easier to browse for end users (the latest releases are shown at the top of the page) and is also much easier for Team vAMSYS to maintain - a win win for all of us! If you currently have alerts set up for when we post new comments to the old changelogs thread, you'll need to follow the release notes using the link at the top of the release notes page. The old forum post will no longer be updated. Knowledgebase migration The most significant change we have delivered is the migration (and quite significant enhancement) of the vAMSYS knowledgebase from the old Atlassian Confluence platform, which is now out-of-support and in growing need of replacement. We are pleased to announce that the most of the vAMSYS knowledgebase from the old platform (and many more new articles describing Orwell features!) are now available to browse by clicking Knowledgebase in the menu at the top. We will continue adding articles covering functionality we have not touched upon yet. The new knowledgebase is a living project and will be continuously updated to remain the number one source for information vAMSYS v3 and upcoming v4 functions. Over the coming weeks we will remove references to the old knowledgebase from the platform and supporting resources and direct members still using the old knowledgebase to the new one on this platform, in preparation for the eventual discontinuation and subsequent removal of the old knowledgebase entirely. Only VA staff and owners can view the knowledgebase - if you have any comments on the content of an article please feel free to leave it a review and let us know how you think we could improve (or what you liked). --- Thank you for bearing with us during these planned outages and we hope you like the improvements we have made to the service we offer. If you have any queries, please follow your normal support routes (escalate to your VA if you are a pilot, or if you are VA staff please contact vAMSYS Customer Services). Many thanks for your support, George and all of Team vAMSYS

This is not FAQ Material. Moved to more appropriate forum. Report issues to your VA - they will escalate if needed.

Hello, The map section of the Pegasus application was working fine with no issues up until yesterday. As you can see from the attached images the map shows no land mass, and no aircraft. I’ve re-downloaded and installed the application to no avail. I’ve even matched the map to the live map on my VA’s website to ensure I hadn’t scrolled away from the Center and got lost. ive already consulted the support forum of my VA whom hasn’t found a solution. can you shed any light on this please? regards Luke

vAMSYS 3.9.1 Bugfix release for 3.9.0. VDS [Fix] Max Container Values not saving in aircraft [Fix] Max Container Values not showing [Fix] Missing/Incorrect null check when creating a route in VDS, causing it to fail in some circumstances. [Fix] Remove mandatory field from container notes when editing. Orwell [Fix] Exporters failing due to being unable to look up load factor name, if one does not exist [Fix] Importers failing due to malformed explode() statement [Fix] Pair/Route importers getting stuck due to erroneous container code [Fix] Removed gender-specific pronouns from descriptions of settings. (VAM-131) [Improvement] Changes to Orwell navigation structure for clarity. [Improvement] Removed the smartCARS download link from Airline Management. [Fix] Fixed an issue whereby events were always created as focus airports, even when the Focus Airport option was not selected. Vulcan [Fix] Fixed an issue which meant that holiday entitlements for pilots were never reset. [Fix] Fixed an issue whereby route maps were not always drawn with the correct route, or any route at all. [Improvement] General code quality enhancements.

vAMSYS 3.9.0 Our last planned minor release of v3. Bugfixes will continue, but we have no further plans to implement new features to v3 The biggest change is the Advanced Cargo System (ACS) - you can find out more about it here: Orwell [Improvement] Importers for the ACS [New] VDS Options to enable ACS [New] Display booked cargo in PIREP review VDS [New] Load Factors page to specify LF for cargo operators [New] Containers page to specify cargo for cargo operators [Improvement] Additions to Aircraft, Airport, Route and Pair pages; create and edit modals to add ACS functionality Phoenix [Improvement] Refactored the dispatch page code [New] Functionality for ACS in dispatch [Improvement] No PAX field for cargo operations not using ACS [New] Display booked cargo in PIREP View

How to enable Advanced Cargo System? Advanced Cargo System has 2 'enable' switches. Both are located in Orwell -> Management -> VDS Settings and should be visible to all staff with appropriate access. The switches are located in 'Advanced VDS Settings' section: Show Advanced Cargo Options - enables visibility of settings for staff to set up ACS. It does not activate in Phoenix and is invisible to pilots. This is the switch you should turn on if you want to set up ACS. If you are not interested - this switch should remain off, as you might get confused by additional options which do not apply to you. Enable Advanced Cargo Booking - This switch must only be enabled after you finished the configuration of ACS as per this forum post. Once enabled, pilots will get to experience the ACS. Please note - existing bookings will not be affected. It will only apply to new bookings. How to configure Advanced Cargo System? All steps listed are MANDATORY and must be fully complete for ACS to work. Ensure your cargo aircraft (ones which do not carry passengers) are in their own 'Aircraft Type'. This is done via VDS -> Management -> Aircraft. If you have a mixed fleet list (for example B747 passenger and freighter versions in one type, move the freighters to a new type using 'Add Aircraft Type' button. Give it a different name) Assign Fleet Type to your cargo fleets. This is done via VDS -> Management -> Aircraft only. Expand fleet list of your cargo fleet and click 'Edit Aircraft Type'. In the window which opens, change the Fleet Type from PAX Only to Cargo Only. Be sure to repeat it for all your cargo types. Double-check and insert 'Max Cargo' and 'Max Container Units' for each of your cargo aircraft. This is done via VDS -> Management -> Aircraft or importers. For VDS -> Expand your cargo fleet list and click Edit on each aircraft. Max Cargo is the maximum value in kilograms only (no grams - i.e. full numbers -> 1500 is correct, 1.5 is not). Max Container Units is a new entry. In positive integer only (1, 50, 1000 etc. 50.59 is incorrect) specify maximum available volume in aircraft. We leave up to you how to come up with the value. You can insert maximum number of ULDs aircraft can carry and call it a day. However, for maximum utilization and save you some headache later on when you want to create a pallet loads etc, try coming up with available floorspace and then construct your containers appropriately. Repeat for all cargo aircraft. If you choose to use the importer to edit these numbers, please follow the importer documentation. Create Load Factor Presets You must create at least one Load Factor Preset and declare it to be the Default This is done via VDS -> Management -> Load Factors Please check the note on the Load Factors page and create as many presets as you want. Please use unique names - they are not visible for pilots. All fields are required when creating Load Factor. Load Factor presets allow you to limit how much cargo can be carried on a route, pair or from airport. This is particularly useful if you want to implement a limit on very long routes, where full load is not possible or to better simulate thinner routes. Customize Load Factor assignments. This can be done via VDS. As mentioned - Load factors can be assigned on an airport level, pair level and route level. If no overrides are made, the Default will be used. The order of override is as follows - route -> pair -> airport -> system default. If you choose to use the importer, please follow the importer documentation. Create Containers This done in VDS -> Management -> Containers. Check the note on the page and create as many as you want. All the fields, except notes, are required to create container. Assign Containers This is done in VDS. Containers can be assigned on an airport, pair or route level, depending on your desires. The order of override is as follows - route -> pair -> airport. Enable Advanced Cargo Booking switch in Orwell -> Management -> VDS Settings.

vAMSYS 3.9.0 should be the last minor v3 release adding new functionality. 3.9.0 introduces long awaited and much requested advanced cargo system. Our huge thanks goes to the team at Cargolux Virtual for their request and their help in fleshing out the feature. We consider Advance Cargo System feature complete from v3 standpoint. There might be some bug-fixes and minor changes, but we consider it to be a good start. The system will be expanded in v4 and some of the functionality will be made available for PAX airlines as well. We have posted a detailed article about what the system is, how to enable said system and configure it. Please be sure to follow it meticulously if you are interested. Please continue to report bugs via the usual channels. If you are a VA pilot, please escalate bugs via your VA. If you are VA staff, please report any issues to vAMSYS Customer Services. Thanks for flying vAMSYS!

What is Advanced Cargo System? Advanced Cargo System (ACS for short further down in this post) is our implementation of more detailed cargo loading for cargo airlines. It allows VAs to set up 'container types' detailing what is being loaded (pineapples, engine parts or whatever else may be). This provides greater immersion for the pilot - they pick what cargo they want to carry as well as how much.

vAMSYS 3.8.9 Orwell [Improvement] The user that requested a callsign parameter to be added is now stored with the request. [Improvement] It is now possible to see the user that requested a callsign parameter. [Improvement] Only the user which requested the callsign parameter is contacted regarding it's status. [Improvement] It is now possible to view the IATA code of approved callsign parameters. Aeolus This release also contains additional enhancements for Aeolus, our back office administration system, which is confidential, and therefore changes to this system are not detailed in public changelogs.

vAMSYS 3.8.8 Phoenix [Fix] It is now possible to unsubscribe from vAMSYS promotional emails. [Improvement] The email settings page now prototypically separates email settings into a global and VA-specific category. Orwell [Improvement] It is now possible for a VA to have access to email addresses revoked by vAMSYS staff. [Improvement] Added warning about direct emailing pilots to the pilot settings page. [Improvement] When a VA cannot access email addresses, the pilots list no longer shows this information. [Improvement] The Pilots: Emailable exporter now fails if your VA does not have access to pilot email addresses.

Hi there, Please contact your VA who can forward your details to vAMSYS support. George

Good evening, I just registered on the platform, but the verification email did not arrive, I have been waiting for more than 4 hours, and it does not appear in any of the folders, thank you.

vAMSYS 3.8.7 Phoenix [Fix] Graphical issue on drawing maps when VA provided route is 'DCT' (VAM-112) [Change] WARJ airport ICAO changed to WAHH (VAM-120) [Fix] Changes to marker drawing when 'Limit base jump to bases' is active (VAM-121) VDS [Fix] Language fixes [Fix] Saving default airport stand group would not propagate correctly down the line (VAM-123) Vulcan [Improvement] Better dispatching of statistic generation jobs for json (VAM-122)