YOUR FLIGHT DESK / HELP
Ready for your
first flight.
Use this guide for launcher 0.2.8 and later. Update to 0.2.8 to choose X-Plane 12 or 11 separately when installing AliveGrass. Windows launch testing and package checks have passed; native launch testing of this version on Mac and Linux is still pending.
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.8-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 AliveGrass for X-Plane 12 & 11. One product covers both simulator targets. Checkout shows the current price and available downloads.
- 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, choose X-Plane 12 or 11 and install the matching available download. 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 and select AliveGrass and your store.
- Enter your order number, full name on the purchase and purchase email.
- For simMarket, your confirmed launcher email and entered purchase email must match the authenticated sale receipt. For X-Plane Store, your full purchase name must match the receipt, the order must be unused, and the entered email must match your confirmed launcher account.
- Matching eligible orders unlock automatically. Open My library, choose X-Plane 12 or 11, then install its matching download.
We match against authenticated seller receipt records received by the studio, not a live lookup on the store website. New receipts normally import every minute; email delays can take longer. If you submitted before a receipt arrived, keep the launcher online: pending claims are checked again automatically.
Used orders, mismatched or missing details, refunded purchases and other ineligible claims require studio review. Read the status or review reason and contact support if needed. Do not buy again just to unlock an existing purchase. Keep order numbers and purchase details private.
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, choose X-Plane 12 or 11, then 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. The simulator selector keeps available versions, installed files and rollback backups separate. If a simulator target has no published download, it cannot be installed yet. 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.
AliveGrass installs but no grass appears
If you installed with launcher 0.2.4 or earlier on Linux or Mac, update the launcher to 0.2.8 first. Close X-Plane, then reinstall AliveGrass from My library. This restores the executable permissions needed by the terrain helper. Choose the correct simulator target: X-Plane 11 and 12 require their own matching files. If grass still does not appear, send support your X-Plane Log.txt and operating system.
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.5 and later 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.
Owner: publish one version for both simulators
Create one release such as 1.0.0. Its Files editor provides six independent upload slots: Windows, Mac and Linux for X-Plane 12, plus Windows, Mac and Linux for X-Plane 11. Upload the matching ZIP into each intended slot and verify it before publishing. Replacing one slot does not replace the other simulator or platform files. Customers need launcher 0.2.8 to select XP11 downloads.
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, check your confirmed account email and full purchase name. Matching eligible unused orders unlock automatically after receipt import; claims with mismatched or unavailable details go to 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.
Activation reports a clock or time problem
Enable automatic date, time and time zone in your operating system, synchronize its clock, then restart X-Plane and retry activation. New activation tokens tolerate a clock up to about one day behind the server; expired tokens remain expired. If activation still fails, send support the exact message and your operating system. Never share your activation token.
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 [email protected] 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.
10. Privacy & account security
Your name, email, account details, purchase references and support messages are used to run your account, verify purchases, provide product access and updates, and help with support. These records are stored in our Supabase-hosted studio cloud, which encrypts stored data at rest and uses encrypted HTTPS/TLS connections in transit.
Access is restricted through account and staff permissions: you can access your own customer records, and authorized studio staff can access information needed to manage purchases and support. Account passwords are stored as secure hashes, rather than readable passwords. Supabase security information · Password protection details.
Purchases and donations are processed by PayPal. AionSky Studios stores the order and payment references needed to verify access; it does not store your payment-card details or PayPal password. Manage optional product-update emails in the launcher’s Updates tab.
For privacy questions or account-data requests, contact [email protected]. Never send passwords, confirmation codes or payment-card details to support.
Download launcher