Experimental Version
The Experimental version is a test version to find problems and issues and to improve functionality based on your feedback. It is not meant to be used for daily use or when you try to do a serious flight on an Online ATC service.
We are currently testing updates to our custom FMS LNAV, and other additional improvements -- see below for a full list.
No Support for Experimental - use at own risk
Please do not seek support for the Experimental Version on Discord and only report issues if you have read this page and the reported and known issues.
New Features to be Tested
- Support for more legs types: CA (partially), CF, CI (partially), CR, DF, HX (partially), IF
- Better turn prediction algorithm with support for overfly, course capture, path capture, direct turn, reverse turn, reversions and more
- Support for marking waypoints as overfly in the F-PLN page
- Realistic ND rendering based on IRL hardware and software architecture
- Fixes for performance issues over long flights
- Initial implementation of the Traffic Alert and Collision Avoidance System (TCAS)
Autopilot and Fly-by-wire
We have made some improvements to the AP and FBW. We highly recommend using a sensitivity setting of -30% to better simulate the increased force you need to push or pull the real sidestick in the aircraft. Please see the screenshot below for an example:
Known Issues
- Stringing issues from the flight plan manager might still occur - will be fixed by the upcoming flight plan manager rewrite
- Some path captures (sharp angle turn into a leg) might be off / intercept at the wrong position - will not affect guidance
- Course capture turns (course to altitude, INTCPT) and CX legs do not adapt to achieved turn radius
- Some turns might revert / de-revert right before they become active in case of speed changes
- Turn reversion heuristics are not tuned perfectly yet
- VM legs sometimes have the wrong course
- Holding patterns embedded in some procedures might not have perfect entries or turn radius
- AF, CD, VI, VR, FA, FM, FC, FD, PI legs are not supported
TCAS Specific Issues
- No support for offline AI traffic (sim limitation)
- No support of multiplayer (MSFS) traffic (sim limitation)
- Possible false detection of ground traffic
- Possible ghost TA / RA due to jumping traffic (improvements and changes expected)
- No performance optimization yet
A Quick Note on TCAS Performance
TCAS relative altitude is now based on plane altitude (true altitude) for both airplanes. This should work exactly as intended for MSFS airplanes relative to one another (though not as the IRL TCAS works). It can still be somewhat of an issue when on a network with non-MSFS airplanes.
The reason for this is that MSFS is the only sim that should correctly compute the true altitude. Depending on the atmospheric conditions, an MSFS airplane flying in the same weather and with the same baro setting as a non-MSFS airplane may be at a different true altitude than the non-MSFS airplane. Said differently, each aircraft could be at the same altitude in their respective simulator, but TCAS would show them at different altitudes.
This is not just a TCAS issue. It is an issue that VATSIM and all the other networks are struggling with so that ATC sees all airplanes, regardless of sim, at the right altitudes, at least relative to one another.
How to Report Issues
Warning
Please read the above Known Issues list and also use the search of Discord to see if your issue has already been reported.
At this time please only report issues via our Discord channel thread:
Experimental - Issue Reports [NO SUPPORT]
Do not expect support or immediate solutions for your issues. We will collect all issues and fix and improve continuously.
Do not open any issues on Github for the Experimental Version!
Download and Install
See Installation Guide.