Please read disclaimer.txt and privacy_policy.txt located in the downloaded folder before use.
Non-commercial use only. Contact me for commercial use.
DOWNLOAD: ➡️ StableApproach 1.4.0-beta.4 ⬅️
This is the first version which works with X-Plane 11 and 12 (no native M1 support yet, sorry).
There have been a few other changes as well, making StableApproach look much nicer and less intrusive (at least in my opinion).
beta 4, please delete all old aircraft profiles located in this folder:
(X-Plane 11/12)\Output\preferences\StableApproach\aircraftConfigs
Changelog 1.4.0:
beta 4:
- New welcome window design. Shows an overview of all requirements for each aircraft
- Added menu button "Show aircraft details"
- Added delta-G measurement for touchdowns
- When using an aircraft with default profile, no profile will be saved anymore
- Fixed rare error during landing analysis (at least I hope so)
beta 3:
- Fixed crashes on Linux / macOS (no native M1 support yet, sorry)
- Improved approach monitor (see above)
- Cleaned menu
- Changed report window layout and added descriptions to requirements
- Minor bugfixes
beta 2:
- Added X-Plane 12 support
- Design changes
- Added _notification window_, which shows errors and updates available
- Removed old _splash window_ (the small window showing _loading_ during startup)
- Moved _Approach monitor_ window to top right corner. (by default, can still be moved around and saved by right-click)
- Added requirement templates for easier aircraft configuration (VAs, read below!)
As usual: If you have any issues or ideas what to improve on, don't hesitate and send me a message 🙂
⚠️ Important for Virtual Airlines ⚠️
X-Plane 12 users: to avoid two different userIDs when sending reports to your VA, copy your StableApproach config file from XP11 to XP12.
It is located in this X-Plane folder: /Output/preferences/StableApproach/general.cfg
This way you don't have to change your userID in phpVMS each time you switch between XP11 and XP12
This is a beta version of StableApproach. The VA Admin needs to make some changes to their GitHub to make it work again.
For VA Admins:
From Version 1.4.0 onwards, managing of aircraft profiles has been greatly simplified by the use of templates.
Each aircraft profile can now link to requirements located in the requirement_templates.json file.
Old profiles will still work fine nonetheless.
As of today (2022-09-10), I've only updated the 737-600/700/800/900 with the new profile format. All others will follow in the next few days.
All beta versions of StableApproach will use the beta branch of your GitHub Fork (instead of main).
This means, you'll need to create or update the beta branch:
- Go to your VAs StableApproach Fork
- Either create or select the beta branch

- Click Sync Fork and confirm with the green Update branch button

Depending on the changes you made, you might need to discard those and apply them again. - Make sure your plugin_version.json file in the beta branch still contains your VA settings. If not, just apply them again.
If you have any problems, don't hesitate to contact me on Discord. GitHub is not always easy in this regard.