YOUR FLIGHT DESK / HELP
Ready for your
first flight.
Use this guide for launcher 0.2.4 and later. Earlier versions may not include NOTAMs. Windows installation has been confirmed on the owner’s PC. Native Mac/Linux operation, simulator compatibility, complete live payment-to-access delivery and real update-email delivery are still being checked.
1. Install on your platform
Windows · Intel/AMD 64-bit
- Download the Windows .exe from the download page.
- Open it, follow the installer and launch AionSkyStudios Launcher from Start or your desktop shortcut.
- If SmartScreen says “Windows protected your PC”, use More info → Run anyway only if offered and you trust this download.
If Smart App Control blocks the download, it has no individual “Run anyway” override. Contact support with the exact message. Do not disable your device’s security protections. Microsoft guidance.
Mac · Apple Silicon or Intel
- Open Apple menu → About This Mac. An M-series chip means Apple Silicon; an Intel processor means Intel.
- Download the matching ZIP, unzip it and move AionSkyStudios Launcher.app into Applications.
- Try opening it once. For an unidentified-developer warning, go to System Settings → Privacy & Security → Open Anyway, then confirm Open if you trust the app.
Malware or damaged-app warnings need investigation: send the exact message to support. Apple guidance. The launcher’s chip choice is separate from the plugin: current AliveGrass Mac plugin binaries are Intel-only, so an Apple Silicon Mac needs to run the compatible X-Plane installation using Rosetta. Simulator compatibility is still being tested.
Debian, Ubuntu and Linux Mint · Intel/AMD 64-bit
Download the .deb and open it with your system’s package installer. Alternatively, open a terminal in its download folder and run the command below, substituting the filename if you downloaded a newer version:
sudo apt install ./AionSkyStudios-Launcher-0.2.4-Debian-amd64.debAPT installs available dependencies. Open the launcher from the application menu. This package is amd64, not ARM. If dependencies or startup fail, include your distribution/version in a support ticket. Native compatibility checks are still pending.
2. Create or sign into an account
- Select Sign in, then create an account with your name, email and a password.
- Check your inbox and spam folder for the confirmation email. Enter its confirmation code in the launcher. Use Resend if necessary.
- Sign in. New customers can shop without waiting for owner approval.
Use Forgot password to request a recovery code, then enter that code and your new password in the launcher. Keep passwords and email codes private. Signing into an account does not by itself grant product access.
3. Buy a new product
- Open Store and select the correct simulator edition. AliveGrass XP12 and XP11 are separate products: XP12 is $15; XP11 is $7.99. Checkout shows the current price.
- Read the product details and download policy, then continue to PayPal.
- Complete payment in PayPal and return to the launcher. Access is granted after the server verifies the completed payment.
- Open My library to install your purchased edition. If the browser did not return correctly, use Confirm completed payment beside the pending order.
A cancelled or failed payment does not grant access. If PayPal charged you and access is missing, open a support ticket with the PayPal order reference. Do not pay again just to retry access. The studio’s digital-download policy is shown before checkout; read it before purchasing.
4. Already purchased at simMarket or X-Plane Store?
- Create and confirm your launcher account, then sign in.
- Open My library → Link a purchase.
- Select your store and simulator edition. Enter the order number, name on the purchase and purchase email exactly as recorded by that store.
- Submit the claim. The studio manually checks its seller records and approves or declines it with a reason.
- Once approved, the product appears in My library. Install it and set your update preferences.
Order numbers are not automatically checked against those stores. A pending claim is not download permission. If declined, read the reason and contact support to correct mismatched information. Do not buy the same edition again while waiting for review.
5. Install or update AliveGrass
- Close X-Plane completely.
- In Settings, choose the root folder containing the appropriate X-Plane installation. Configure XP11 and XP12 separately if you use both.
- In My library, select Install or Install update. The launcher chooses your operating system’s ZIP, verifies the download and installs into the product’s configured plugin folder.
- Wait for Installed before starting X-Plane. Simulator folders must be writable by your account.
XP11 files cannot be used as XP12 files. Your library shows available and installed versions separately. A prior managed installation is preserved for rollback; use Rollback with X-Plane closed if an update causes trouble. Rollback does not repair unrelated simulator or scenery issues. Open installed folder lets you inspect the managed files.
6. How updates and NOTAMs reach you
| Notice | Where you receive it | What you do |
|---|---|---|
| Plugin release | Updates tab and desktop alerts for followed editions; optional email when enabled for that edition. | Close X-Plane, open My library and install the update. Read the release notes first. |
| Launcher release | A version banner and desktop alert when a newer version has a download for your OS/chip. | Download the installer. Quit the launcher and install/replace the app. Updates are manual, not silently installed. |
| NOTAM news or advisory | NOTAMs tab and a desktop alert for each published revision. | Read the notice and any workaround. Mark it as read when finished. |
| Urgent NOTAM | NOTAMs tab, desktop alert and an urgent banner across launcher pages. | Read and follow the studio’s instructions, then acknowledge it. |
Launcher 0.2.4 checks connected content approximately every 10 seconds while running. Older versions check their existing update features approximately every 30 seconds. This is periodic checking, not guaranteed instant delivery. An offline or fully quit launcher cannot receive desktop alerts; it checks again when opened and connected.
Enable Desktop notifications in Settings and allow notifications in your operating system. Keep running in background lets checks continue after closing the window while the computer is awake; it does not automatically start the launcher after restarting your computer. Use the tray/menu icon → Quit to stop it fully. Do not rely on desktop alerts during sleep, offline periods, OS notification suppression or network failures.
In Updates, follow each edition you want and enable “Email me about…” for product release emails. Those emails can arrive while the launcher is closed, subject to the sender, inbox filtering and delivery. NOTAMs and launcher-version notices do not currently send email. Changelogs are separately written by the owner and do not automatically create notifications.
Publishing a newer launcher is separate from publishing a plugin release. Updating website text, product pictures or a NOTAM does not require another launcher build once you have a version supporting that feature.
7. Every launcher tab explained
| Tab | Purpose |
|---|---|
| Discover | Studio promotions and the featured collection. |
| Store | Browse editions, screenshots, descriptions, prices and PayPal checkout. |
| My library | Purchased/approved products, installs, updates, rollback, linked claims and PayPal order status. |
| Updates | Plugin releases, release notes, unread notices, edition follows and optional email preferences. |
| NOTAMs | Studio news, known issues and urgent guidance. Resolved issues may remain visible; expired or withdrawn notices disappear. |
| Changelogs | Manually published product change history, filterable by edition. |
| Donations | Optional PayPal contributions to support future addons. Donations do not purchase a product or grant library access. |
| Support | Create a ticket and keep your conversation with the studio together. |
| Help | These installation and usage instructions. |
| Settings | Simulator folders, desktop notifications, background running and cloud connection settings. |
| Account | Sign in, manage your session or sign out. The owner console is shown only to authorized staff; ordinary customers cannot make themselves owners. |
Galleries can be browsed using the arrows, thumbnails and play/pause controls. Open a product for the larger screenshot view. Product pictures are real simulator captures; aircraft, liveries and airport scenery shown are separate content.
8. Common problems
No confirmation or recovery email
Check the entered email and your spam folder. Use Resend and the newest code. Avoid rapid repeated requests. Contact support if delivery continues to fail; never send your password or confirmation code.
My purchase is missing
Confirm you signed into the correct launcher account and bought the correct edition. Check My library’s PayPal orders or linked-claim status. Try Confirm completed payment if available. For store purchases, wait for studio review. Give support the order reference and purchase email.
Download, verification or installation failed
Check your connection, free disk space, simulator folder and write permission. Close X-Plane, then retry. A failed hash check must not be ignored. If it repeats, include the exact error and product version in a ticket.
The addon caused a simulator problem
Close X-Plane, read NOTAMs for known issues and try the managed rollback if available. Include your simulator version and product edition in a support ticket. Follow the studio’s instructions for any diagnostic files.
I don’t see update notifications
Open the launcher and check Updates/NOTAMs directly. Confirm it is online, desktop notifications are enabled, your OS allows them, and you follow the correct plugin edition. Check that email alerts are enabled separately if wanted. A fully quit launcher cannot show desktop alerts.
Local preview or cloud connection problem
Public builds connect to the studio cloud by default. Local preview uses sample data and cannot accept real purchases. Do not substitute secret API keys into cloud settings. Contact support if the production cloud is unreachable.
9. Contact the studio
Use Support → New support ticket while signed in, or email aionskystudios@gmail.com if the launcher cannot open.
Include your operating system/version, Mac chip or Linux distribution where relevant, launcher version, X-Plane version, AliveGrass edition/version, exact error and steps to reproduce. For purchase issues, include the store/order reference and purchase email. Keep passwords, recovery codes and payment-card information out of tickets and screenshots.