[REQUEST] MCDU - DIR: Improve DIR TO

[krangerich]

Is your feature request related to a problem? Please describe.

Improvement for more realism

Describe the feature you'd like to see implemented

• Changes to DIR TO waypoint:
  1. Upon selection of a waypoint from the list: The distance field in 1R should show the distance to the selected waypoint. The title "DIR TO", the waypoint in 1L, the distance in 1R and the "DIRECT TO" in 2R should be turn yellow. Brackets "[]" around the waypoint in 1L should disappear. The arrow in front of the selected waypoint (left side) should disappear. Arrows after the other mode selectors (right side: ABEAM PTS, radial in/out) should appear. Label above 6R should read "DIR TO". Text in 6R should read "INSERT*"

2. After selecting "INSERT*": The waypoint with the current a/c location should be renamed to "T-P" (turning point).

• DIR TO/BEAM: The waypoints that would have been deleted are projected onto the new leg as artificial waypoints.
  3. After selecting a waypoint in step 1, "ABEAM PTS" (3R) should be selectable. When selected, "ABEAM PTS" should turn yellow and the previous selection should turn blue again. The arrow after "ABEAM PTS" should disappear and and arrow in front of the previous selection should appear

4. After selecting "INSERT*" (with ABEAM TO selected): Existing waypoints, which would have been deleted, are being inserted as artificial waypoints, projected onto the new leg. Name of the artificial waypoints are "AB....." (AB + the former name).

• DIR TO/INTCPT: More complicated (see video).

References

Explanation video: https://www.youtube.com/watch?v=PaiQ3vn3vGE (this is based on another simulation, but should give a good picture)

http://www.a320dp.com/A320_DP/nav-flight-management/sys-14.3.0.html

I could provide information from the FCOM/FCTM or the Thales MCDU guide, if required for accuracy.

Additional context

none

Discord username (if different from GitHub):

[Benjozork]

Hello, the DIRECT TO function is already implemented. If there's a specific mode or many features missing, please change your title to reflect that instead.

[Wolverine80]

But does it work correclty as it is implemented? Yesterday I tried to intercept a waypoint in an approach with Direct To. The autopilot flew to the selected waypoint, and once there, turned back to the entry point of the procedure instead of going to the next waypoint in the flight plan. I tried it several times and it was not possible to go on with the flight plan once a direct to waypoint has been selected.

[krangerich]

Sorry, my mistake - I didn't notice the DIR TO waypoint is already implemented. I'll adjust the title and the description to reflect further improvement

[B-KC]

Hi, I noticed this is marked as an "enhancement" however in my experience Direct To isn't working at all thus I feel this should be a bug.

After taking off with a destination airport and approach loaded, doing a Direct To VOR for example shows the direct to on the map and activates it visually, however it never actually flies to that location. It continues on the original LNAV path.

I could be completely misunderstanding the purpose of Direct To in the A320, but I've also flown other approaches where I've done a direct to a 10 mile IAF vs. 15 or 20 and it still ignores the waypoint as well.

[olibarke]

https://app.photobucket.com/u/olibarke/p/ec4b2b7e-fb28-4e4a-b4bf-a3a4b72dc0fc

Additionally when a DIR to is shown it does not collapse the previous points on the FPLN. It should sequence and delete them as you pass each one.

[joseG69]

Hello every one I have the same problem in the DIR TO function. To my opinion it is not only an enhancement, but it is a bug. It makes almost impossible to fly online in VATSIM, as the controllers are always redirecting or short cutting you, most of the time, near the approach. I tried to investigate and realized that the problem reported in #3027 and #2338 and by B-KC in this post happened when selecting DIR TO a waypoint that is in the approach procedure (the images are very clear about that). I made some tests and realized that DIR TO function works fine in other cases, but when you select DIR TO a waypoint that is in the approach procedure, it does not delete the previous waypoints. So when reaching that waypoint, the aircraft turns back to previous waypoints. That does not happen when you select DIR TO a waypoint on route. I have also read some posts in MSFS 2020 forums and realized that a lot of people complain about going back in the approach phase, so this might be a bug beyond the scope of this project. Summarizing, there are 2 different issues in my opinion: 1) The one reported in this post by krangerich. (enhancement) 2) the problem of not deleting the previous waypoints in DIR TO function, which I believe is a bug and has a great impact in flying.

Best regards

[Benjozork]

@joseG69 This issue will be resolved by #2831