Review your
modification and ensure it follows the guidelines in the
Creating a New Modification tutorial.Please read the online version of this document to ensure you have the latest version.
This tutorial covers uploading your custom modifications to the EditVoicepack server, allowing it to be distributed to all EditVoicepack users around the world. It is recommended to read the short section "Sending Updates to the Server" in the EditVoicepack User's Guide, as it contains information not found in this tutorial.
In this tutorial, you will be guided through the upload of the fictive callsign "Bevelstone". As each callsign should only be uploaded to the server once it is not possible to create a tutorial that you can actually complete unmodified. You will have to complete the tutorial with your own modification. This tutorial primarily covers callsigns, with italic text used to outline the differences when uploading other types of modifications.
Review your
modification and ensure it follows the guidelines in the
Creating a New Modification tutorial.
Specifically you should check that no errors are shown when you press the "Ignore Errors..." button. In case you choose to ignore an error, please specify this in the upload comments (see alter in this tutorial). Obviously a real country name should be used instead of "Atlantis" used here.
Right click the
callsign in the main tree view and select "Send to Server...". When the Wizard
opens it will contact the server to verify the upload is allowed. The upload
will be allowed if all of the following conditions are met:
If the upload is allowed the "Next >" button will be enabled. If upload is not allowed the reason for it will be listed, and you must press the "Cancel" button to exit the wizard.
Assuming upload is allowed, press the "Next >" button now and proceed with this tutorial.
The group assignment is used to archive the modifications. This serves the dual purpose of making it easier to find the modifications back and allowing people to only include some of the modifications. While assigning the group for airports and aircraft models and types is fairly straight forward, the callsigns have a bit more complex group structure. As a base line the callsigns should be assigned at least two groups: One entry (and only one) in the "By Registration Country" branch - obviously the country where the callsign is registered), and one or more in the "By Appearance" branch. Each region where the callsign is used should be checked in the "By Appearance" group. If for example an airline operates one route between San Paulo (Brazil) and Miami (United States of America) it should have North America, South America, and Caribbean selected. Even though the planes do not land anywhere in Caribbean they still fly though the region, and can hence receive vectoring from ATC.
If the correct country is not availailable, please specify it in the upload comments (see later in this tutorial).
Virtual Airlines and military callsigns should only be added in their respective branches. Do not include them in the "By Appearance" or "By Registration Country" branches.
When assigning aircraft models and manufactures; please consider if that several aircrafts and manufactures fits in several categories. Boeing for example manufactures Military and GA planes next to the better known airliners.
The upload comment
should include the following:
If you have the ICAO code of the aircraft, airline, or airport please include it as well.
Press the "Next >" button and fill in the Feedback Information page (I will not provide further detail here as the wizard contains plenty information on the available fields). Press "Next >" again to go to the "Confirm Upload Page". If you are sure all information is correct, press the "Upload" button and wait. press the "Finish" button when the upload is complete. If you specified an email address on the Feedback Information page, you will receive an email after the modification has been reviewed.