Which leads me back to my question on how the PMDG FMS logic is handling entering additional waypoints to the loaded approach. There's a lockout for IAF to MAP, is it locking out ANY additions to a procedure?

 

Can you build this proedure - including all the intermediate waypoints - by hand (don't load it)? If so then it would appear the CDU isn't enforcing the lockout properly.

Another Theory: 

 

Maybe the 777 expects the "Terminal Waypoints" to be inside the SID/STAR file?

 

At the moment, they are only defined in the wpNavFIX.txt

 

 

Does adding a waypoint to LEGS page or selecting a DCT to a waypoint that is defined in the SID/STAR file work, without being preloaded on the LEGS page?

 

Examples from the EDDF SID/STAR File: 

 

FIX DF132 LATLON N 50 6.98883 E 8 19.35250
FIX DF133 LATLON N 50 1.83600 E 8 26.80850
FIX DF134 LATLON N 50 1.72900 E 8 31.12633
FIX DF135 LATLON N 50 1.46617 E 8 31.27367
FIX DF136 LATLON N 50 0.66650 E 8 17.01767
FIX DF137 LATLON N 49 57.95533 E 8 31.70733
FIX DF138 LATLON N 49 58.33717 E 8 25.35467
FIX DF139 LATLON N 50 3.41200 E 8 38.22000
FIX DF140 LATLON N 50 3.12150 E 8 38.24600
FIX DF141 LATLON N 50 1.07467 E 8 30.12383
FIX DF142 LATLON N 50 0.51217 E 8 29.81300
FIX DF143 LATLON N 49 58.96433 E 8 28.94983
FIX DF144 LATLON N 50 2.86950 E 8 35.93917
FIX DF145 LATLON N 50 2.60617 E 8 36.07700
FIX DF146 LATLON N 50 6.02033 E 8 38.04317
FIX DF149 LATLON N 50 4.36450 E 8 42.64283
FIX DF150 LATLON N 50 0.61483 E 8 45.10433
FIX DF151 LATLON N 50 3.45517 E 8 50.61600
FIX DF152 LATLON N 50 4.23317 E 8 42.48050
FIX DF153 LATLON N 49 50.48150 E 8 41.43117
FIX DF154 LATLON N 49 58.70233 E 8 35.65467
FIX DF155 LATLON N 49 54.77317 E 8 42.98100
FIX DF156 LATLON N 49 56.03667 E 8 27.46517
FIX DF157 LATLON N 49 47.46600 E 8 40.33767
FIX DF158 LATLON N 49 58.00017 E 8 31.58300
FIX DF159 LATLON N 49 56.97650 E 8 34.41867
FIX DF160 LATLON N 49 52.41917 E 8 32.09700
FIX DF162 LATLON N 50 0.58733 E 8 29.77500
FIX DF163 LATLON N 49 55.92350 E 8 27.27983
FIX DF164 LATLON N 49 51.73450 E 8 21.03717
FIX DF165 LATLON N 50 0.14300 E 8 29.71167
FIX DF166 LATLON N 49 57.29400 E 8 29.33000
FIX DF168 LATLON N 49 56.34950 E 8 36.16767
FIX DF169 LATLON N 50 3.87050 E 9 17.00367
FIX DF170 LATLON N 50 0.92000 E 8 29.77167
FIX DF171 LATLON N 50 0.45750 E 8 29.55183
FIX DF172 LATLON N 49 54.87617 E 8 26.96600
FIX DF180 LATLON N 49 54.31217 E 8 26.70400
FIX DF197 LATLON N 49 58.77867 E 8 31.57683
FIX DF198 LATLON N 49 45.06133 E 8 27.95217
FIX DF200 LATLON N 49 43.20083 E 8 26.90767
FIX DF201 LATLON N 49 47.25300 E 8 14.37167
FIX DF233 LATLON N 50 1.99900 E 8 25.27833
FIX DF234 LATLON N 50 1.59083 E 8 30.58950
FIX DF235 LATLON N 50 1.36283 E 8 30.86233
FIX DF236 LATLON N 50 1.43133 E 8 23.40650
FIX DF237 LATLON N 50 2.34600 E 8 20.43567
FIX DF238 LATLON N 50 7.70883 E 8 15.93083
FIX DF270 LATLON N 50 1.62450 E 8 8.56900
FIX DF271 LATLON N 49 52.18717 E 8 13.64783
FIX DF272 LATLON N 49 56.90950 E 8 11.10850
FIX DF273 LATLON N 50 5.57633 E 8 48.40767
FIX DF275 LATLON N 50 1.36417 E 8 8.70950
FIX DF276 LATLON N 49 51.92683 E 8 13.78700
FIX DF277 LATLON N 49 56.64550 E 8 11.25050
FIX DF278 LATLON N 50 3.35267 E 8 50.63683
FIX DF281 LATLON N 50 7.58467 E 8 55.78033
FIX DF282 LATLON N 49 59.01517 E 8 20.77333
FIX DF289 LATLON N 50 7.32100 E 8 55.92233
FIX DF290 LATLON N 50 1.22817 E 8 30.27817
FIX DF291 LATLON N 49 59.71083 E 8 27.07550
FIX DF401 LATLON N 49 59.59183 E 7 56.96500
FIX DF402 LATLON N 50 4.38200 E 8 16.29133
FIX DF403 LATLON N 50 5.80217 E 8 22.50100
FIX DF406 LATLON N 50 21.73650 E 9 15.49367
FIX DF407 LATLON N 50 23.69250 E 9 10.53517
FIX DF408 LATLON N 50 15.97900 E 8 37.62933
FIX DF409 LATLON N 50 10.22133 E 8 40.99900
FIX DF416 LATLON N 50 19.75867 E 9 21.87150
FIX DF422 LATLON N 50 9.61667 E 9 1.03950
FIX DF426 LATLON N 50 15.05067 E 9 24.50283
FIX DF431 LATLON N 50 4.65850 E 7 51.43817
FIX DF432 LATLON N 50 12.40750 E 8 23.32383
FIX DF436 LATLON N 50 13.86917 E 9 16.92183
FIX DF437 LATLON N 50 16.27517 E 9 6.78017
FIX DF439 LATLON N 50 6.76950 E 8 26.54650
FIX DF444 LATLON N 49 57.59467 E 7 48.93650
FIX DF452 LATLON N 49 55.76917 E 8 3.28433
FIX DF454 LATLON N 49 52.92367 E 7 51.70100
FIX DF601 LATLON N 49 56.36817 E 8 32.31100
FIX DF607 LATLON N 50 1.10150 E 9 14.92967
FIX DF608 LATLON N 49 55.84133 E 8 52.49283
FIX DF609 LATLON N 50 0.54017 E 8 49.82450
FIX DF613 LATLON N 50 5.30167 E 9 10.09517
FIX DF616 LATLON N 50 9.36133 E 9 27.67017
FIX DF621 LATLON N 50 7.26783 E 8 55.74333
FIX DF623 LATLON N 50 10.00400 E 9 7.44883
FIX DF626 LATLON N 50 14.07050 E 9 25.04950
FIX DF631 LATLON N 50 0.37267 E 8 12.73550
FIX DF632 LATLON N 50 1.25533 E 8 20.52883
FIX DF635 LATLON N 49 58.94567 E 8 43.01633
FIX DF636 LATLON N 49 55.60533 E 8 29.13433
FIX DF644 LATLON N 49 47.29333 E 7 55.02100
FIX DF651 LATLON N 49 56.22483 E 8 9.64633
FIX DF654 LATLON N 49 51.96550 E 7 52.26750
FIX DF901 LATLON N 50 3.63133 E 8 52.16650
FIX DF902 LATLON N 50 5.09400 E 8 59.00150
FIX DF907 LATLON N 50 0.86717 E 8 57.94450
FIX DF910 LATLON N 49 57.23117 E 8 21.21467
FIX DF911 LATLON N 49 55.83683 E 8 14.87583
FIX DF914 LATLON N 49 52.69783 E 8 22.09183
FIX DF920 LATLON N 49 57.13783 E 8 20.78883
FIX DF950 LATLON N 49 50.16900 E 8 40.39133
FIX DF951 LATLON N 50 4.26100 E 8 0.49033

 

 

 

Jan-Paul

 

 

Does selecting a DCT to a waypoint that is defined in the SID/STAR file work without being preloaded as part of a SID / STAR.

 

Negative. Looks like the only way to fly direct to a DM... point is an entered procedure. Then you are able to take the waypoint out of the scratchpatch and set him on top.

 

Any real T7 pilot here?

Thats a basic feature of every Honewell FMC. For sure this works on a real world FMC. Otherwise a lot of real world airlines would have trouble.  

 

At the moment I don't have any clue why this should not work.

 

 

I think we need someone from PMDG to investigate this issue.

 

 

 

Jan-Paul

can it be built from scratch. as in enter all the waypoints, not be editing a procedure.

Thats a basic feature of every Honewell FMC. For sure this works on a real world FMC. Otherwise a lot of real world airlines would have trouble.  

 

At the moment I don't have any clue why this should not work.

 

 

I think we need someone from PMDG to investigate this issue.

 

 

 

Jan-Paul

 

Thanks man.

 

Terminal procedures often use local fixes that are only defined for that area. In our sim world, global fixes are defined in wpNavFIX.txt and local fixes are defined in the sidstar file for that location. Pretty easy to open these to verify if info is there or missing. Local fixes cannot be entered into the FMS, they must be read by the simulation from the sidstar.

We're looking into this. Either there's a bug or it's realistic behavior for the 777 FMC. Not sure which yet until I talk to the person who coded it.

Terminal procedures often use local fixes that are only defined for that area. In our sim world, global fixes are defined in wpNavFIX.txt and local fixes are defined in the sidstar file for that location. Pretty easy to open these to verify if info is there or missing. Local fixes cannot be entered into the FMS, they must be read by the simulation from the sidstar.

But these fixes like DM428 ARE in wpnavfix.txt!

Just got this picture from a friend from a real 777.

 

So it's possible to enter these fixes.

 

-gianluca311

 

 

We're looking into this. Either there's a bug or it's realistic behavior for the 777 FMC. Not sure which yet until I talk to the person who coded it.

Any news on this? Would like so see that problem in the "issue tracking thread".

It is a little ambarrassing to say unable direct DF*** to the Vatsim controllers with that new bird.

Hi All,

 

I missed this thread and opened a new one for this exact issue. Maybe the information I posted there regarding this issue in Porto TMA (Portugal) can help the investigation, so here is the link:

 

http://forum.avsim.net/topic/421719-terminal-area-intersections/

It looks like the FMC in the T7 is rejecting any waypoint entry in the form of AANNN (two letters + 3 numbers). Just to see if it was a validation issue, I edited the wpnavfix.txt file (navdata fixes) and changed PR634 (unselectable in the T7 fmc) to PRT34. After that change, I could select the "new" PRT34 waypoint both in legs and in the cdu FIX page.

 

I believe this is something that needs to be fixed, although I don't see it mentioned in the issue tracking thread...

It looks like the FMC in the T7 is rejecting any waypoint entry in the form of AANNN (two letters + 3 numbers). Just to see if it was a validation issue, I edited the wpnavfix.txt file (navdata fixes) and changed PR634 (unselectable in the T7 fmc) to PRT34. After that change, I could select the "new" PRT34 waypoint both in legs and in the cdu FIX page.

 

I believe this is something that needs to be fixed, although I don't see it mentioned in the issue tracking thread...

It is on the issue tracking thread, they will fix it.

Finally