inselc

Member
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good news - this issue seems to be fixed as of 1.0.9.26! Note for pilots experiencing a similar issue in 1.0.9.26 There is no warning displayed on the MCDU if the entered constraint is in conflict with another one down the line; for example: Waypoint 1: ALT constraint "FL90 or above" Waypoint 2: no constraints, expected FL93 ... Waypoint 6: ALT constraint "6000ft or above" If you edit Waypoint 1, and enter a new ALT constraint that is lower than Waypoint 6's, it will be ignored: Waypoint 1: ALT constraint now "at 4000ft" Waypoint 2: no constraints, but expected FL is still FL93! The Aircraft would have to climb again to comply with Waypoint 6's ALT constraint, if it were to descend to 4000ft at Waypont 1! Waypoint 6: ALT constraint "6000ft or above". Not sure if this is consistent with real MCDU functionality, but certainly something to look out for. Thanks!
  2. Flight Sim Platform: Prepar3D v4 Brief: When manually entering speed or altitude constraints on the MCDU ACT F-PLN page, the vertical and speed profiles are not re-calculated. The entered constraints are not respected by the autopilot. How to recreate: Start off with a new flight and load the "Ready To Start" panel state Load the aircraft with 9598lbs of fuel, 34 pax and 1250lbs of cargo On the CAPT MCDU, open the F-PLN INIT 1/3 page Enter "EDDH/EDDF" into the FROM/TO field (no company route found) Select "RETURN TO F-PLN INIT" Enter "300" into the CRZ LEVELS field Enter "100" into the CI field Switch to WEIGHT INIT 2/3 page Enter "9.6" (10^3 lbs) into the BLOCK field Enter "86.0" into the TOGW field Enter "22.4" into the TOCG field Enter "19.2" into the ZFWCG field Open the ACT F-PLN page Select EDDH Select SID Select "15" from the RWYS list Select "IDEK6D" from the STD SIDS list Select "INSERT" Select IDEKO Select AIRWAYS Enter VIA "Y900" TO "TIMEN" Enter VIA "UL126" TO "PIROT" Select "INSERT" Scroll down to waypoint PIROT Enter "/23000" into the scratchpad Press the right hand LSK next to PIROT Select "DES" Select PIROT Select AIRWAYS Enter VIA "T152" TO "KERAX" Select "INSERT" Scroll down to waypoint ROBAR (directly after PIROT, distance 23NM) Here you can see the first issue (see attached image): The altitude prediction for waypoint ROBAR is displayed as "FL300" in small print. I expected the FMS to recalculate the descent path (since "DES" was selected earlier), to reach FL230 at PIROT and maintain the altitude constraint (FL230) afterwards. The same applies when altitude constraints are added mid-flight, with the complete routing to EDDF (including transition and approach) set up in the FMC. Press the right hand LSK next to ROBAR (empty scratchpad) to open the VERT REV AT ROBAR page Enter "280" into the SPD: AT/BELOW field Select "RETURN TO ACT F-PLN" Scroll down to to waypoint EMBAD (directly after ROBAR, distance 24NM) Here you can see the second issue (see attached image): The speed prediction for waypoint EMBAD is displayed as "300". Again, the FMS should recalculate the speed profile to maintain the last constraint (280). The same applies when entering a speed constraint mid-flight. During flight, the Autopilot ignores the manually entered altitude constraint: PFD displays "PROF TO 23000", but the magenta circle stays at 30000ft even when passing PIROT. Related reports: "Altitude Restrictions Not Recalculating TOD or Profile", posted May 9th 2017, concerning Version 1.0.7.3 "MCDU: Re-calculate TOC/TOD", posted July 18th 2017 I hope this is helpful.