Leaderboard

The relative terrain elevation overlay is actually something I've been considering to implement, but since I saw it was being put into XP11.20, I didn't bother. But we do have a completely custom TAWS-B page which does the same relative terrain contouring coloring plus of course all the aural and visual annunciations of the real Garmin TAWS with all modes modeled (PDA, RTC, ITI, NCR, impact point prediction, etc.).

2 is fine for normal planes and I think the IXEG flies just fine with that. I only use higher values for helicopters, where it helps with the constant fine control adjustments.

Hi I purchased XP11 & ixeg several days ago and really happy with it (after being devoted fan of PMDG B737NG on FSX). It is a very fluid, immersive and realistic simulation of B737CL, on par with PMDG, if not beyond. However, there is a number of bugs which I discovered having completed about 10 flights so far: 1. While on ground, unable to enter CRZ speed in FMC (e.g. "0.7", "0.72", etc.), "not allowed (or so)" message prompts, this is however possible when airborne; 2. Unable to enter DES speed and speed restriction in FMC, although EXEC prompts, fields remain blank; 3. ANP value not given (0.0); 4. Climb de-rate (apparently) not removed gradually to full CLB while climbing to cruise flight level; 5. By switching seatbelts off at night time cockpit becomes lit with light (dome light apparently); 6. On takeoff, after rotation, "glideslope" aural message plays (I always set NAV1 prior departure to ILS for emerg return, as per SOP); 7. Autobrake either does not perform at all or performs insufficiently for the selected position (I DO arm spoilers on approach with the appropriate light illuminated, and there is no "disarmed" light upon rollout); Please, consider allowing entry of raw coordinates and/or radial-distance waypoint in FMC. This is a pretty crucial thing, I couldn't believe at first it was still not implemented, as it is such a basic thing to have. In general, FMC needs significant further development and refinement. VNAV issues, HOLD page, inhibition of DME-VOR-GPS, custom waypoints, fuel predictions, supplementary pages & functions, etc. It would be also nice if you could specify what exact FMC software version you replicated (U5.0, etc.). Own failure model would be nice too (I'm aware about that small LUA script). Other systems, designs, dynamics, performance (especially fuel burn) are spot on! Thank you!

I always thinking of what a helicopter pilot once said. "If you are in doubt, there is no doubt". I probably should had followed his advice on this landing attempt METAR: 151550Z 15021G31KT 9999 VCSH SCT020 BKN030 04/M01 Q0981 NOSIG RMK WIND 1200FT 13052G67KT

Problem solved with regard to autobreak and sinking aircraft in the 50ft approach of the rwy causing violent Touchdown Effects caused by XPrealisticPro by disabling in the IXEG B733 the aircraft returned to function perfectly.

Regarding the autobrake: Try to fly without X-Enviro to test this - there have been occasional reports about the ground friction getting affected in some weird way - just to test, disable it in the plugin menu. Also, un-assign your hardware thrust lever and use the default keys (F1/F2) instead for this test - sometimes thrust axises aren´t calibrated properly and "0" throttle angle is not achieved, even with hardware at stop. You can also output the relevant data to screen to test this (go to the DATA OUT tab). There will be no "disarm" light if the autobrake fails to work because thrust is not at idle - since it is not "disarmed". There will be a "disarm" light if you disarm the autobrake with manual brake input, though. Also note that there is an X-Plane bug that will prevent the autobrake from working again if you reject a takeoff and then do a second one and try to reject that as well (iirc). Cheers, Jan