daemotron Posted August 7, 2016 Report Share Posted August 7, 2016 Reference: IXEG 737-300 Classic version 1.0.7 X-Plane 10.50rc1 NDP AIRAC 1608 rev 1 Route flown: LEPA MERO2A.MEROS UN853 LUMAS UM976 SOFFY UQ208 MOBLO UZ662 LAMUR Z67 KORED UN871 DITON T163 ZUE T125 ROMIR UN851 KEMAD P605 AGATI.AGATI2K EDDH Departure: 24R Arrival: ILS 23 Effects observed: The VNAV profile proposes a ToD only 70NM from the runway threshold for a descend from FL360: On a second attempt (the one for which I attached the logs), I modified the ALT Constraint for PISAS from 3000A to 3000 (as 3000ft would be the GS interception altitude at PISAS), but this did not change the VNAV profile. The constraints in the Nav Data (at or above) are OK (apart from PISAS), but the computed VNAV path is way higher (and steeper). At one point, the ND even claims the VNAV path to be at negative altitude (saying I'm 16,600ft above VNAV path while flying at FL125): In real life, the ToD would be somewhere shortly before DLE... Log.txt GizmoLog.txt IXEG_FMS_debug.txt Quote Link to comment Share on other sites More sharing options...
Litjan Posted August 9, 2016 Report Share Posted August 9, 2016 Yeah, there are still a few cases were the vnav calc gets screwed up. We are worling on those. Jan Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.