Version 1.3 development - what to expect

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Version 1.3 development - what to expect

ATC Behavior Changes 

1. The application now fully supports traffic separation - airborne and on the ground. 
Airborne - for separation and conflict avoidance - vectoring and speed instructions will be given to user and AI Traffic aircraft at the same level.
Ground - taxi hold position and follow the aircraft instructions will be issued accordingly

2. Implemented go-around ability.
3. Improved, more realistic runway selection according to the airport environment.
For example - at KLAX,  runways 24R/06L and 25L/07R would always be used for landings, and 24L/06R and 25R/07L for takeoffs.

4. Improved ATC controlling stations boundary behavior.
 5. Improved altitude clearances by avoiding short segmentation clearance.
For example - on flight clearance, initial climb altitude is calculated using more realistic factors, thus providing a much higher altitude.
The same happens during descent.

6. Improved vectoring during approach/departure when necessary.
For example: In instances where vectoring is a part of the SID/STAR procedures, it is now available and applied as appropriate.

7. Added speed instructions for separation.

User Flight Experience

Departure/Arrival runways and procedures are now changing and being adjusted both during and before the flight, 
according to environment conditions like weather, and taxi to runway priority.

There is also the option to skip the application flight planning screen when importing a flight from SimBrief.
The application will automatically adjust departure/arrival runways and procedures according to the environment.

The ability to change departure/arrival runway/procedure has been enhanced by allowing changes from the flight menu on any stage.

Voices

Voices and phraseology improvements are expected in this version. 
More detailed information will be provided later.

AI Traffic

1. Fixed AI Traffic behavior which improves major issues regarding disappearing aircraft and landing teleportation (for MSFS).

2. Improved amount of non-parking traffic, and traffic injection time.

Application Stability

Reduced application CPU usage – the application will settle in to use only about 5%-10% of CPU (depending on the selected amount of AI Traffic). 
To clarify – the application must have real time control of AI traffic - therefore CPU usage is required.

Next releases and future plans

MSFS Marketplace encrypted scenery

*If you are using MSFS Marketplace encrypted scenery, currently, the application  has no way of reading this scenery from BGL files. So, what happens now? Users see the add-on scenery but the application can only use the default scenery of the flight simulator.
Sometimes, for example when an airport’s layout differs between the default and the add-on scenery, you might see AI aircraft parked incorrectly,
 maybe even parked with its nose driven into the side of a building.
This is because the add-on  scenery has a building footprint that is different from the default scenery, and the application has no information on this due to the scenery encryption.
The good news is that there are many (probably most) airports where add-on scenery does not differ in position.
In these cases our users will not notice any peculiar behavior.

However, MSFS now provides an API which completely avoids this issue. 
Utilizing this new API are in the plans for one of the next releases of version 1.3.

User Interface and VR support - version 1.4

Application window improvements and support for VR are planned in version 1.4