Leaderboard

Feature update for you good people. We've implemented the G1000 Emergency Descent Mode. That means no more setting up the simulator and walking away to take a nap. A brief demonstration: https://www.twitch.tv/videos/253395611?t=02h40m35s Now the avionics is watching for pilot alertness. The allowable time interval for pilot interaction is altitude dependent, but varies from 20 minutes at 15,000 ft down to around 8 minutes at FL310 (decreasing exponentially, so only about 10 minutes at FL250). If pilot inactivity is detected for the aforementioned period if time (no buttons pushed or knobs actuated on the G1000 avionics), the avionics will start a graduated process of alertness checks: First it issues an advisory CAS caution + one aural chime:"ARE YOU ALERT?". The pilot has one minute to respond by pushing any button or clearing the caution via the attention getters. After 1 minute passes and the pilot hasn't responded, the system issues a non-advisory caution saying "HYPOXIA ALERT". Non-advisory CAS cautions different from advisory ones in that the message stays blinking and the yellow "MASTER CAUTION" button stays illuminated. The pilot again has 1 minute to respond. Final call, the system issues an "AUTO DESCENT" master warning CAS message, illuminates the red MASTER WARNING button and a continuous aural chime is heard. If the pilot doesn't respond for one more minute, the red "EDM" AFCS mode is annunciated on the PFD, the autopilot preselects 15,000 ft altitude, switches to the FLC pitch mode to initiate a descent and selects maximum airspeed. On descent the engine will over-torque without the pilot making power adjustments, but the torque limiter can hold the engine at 108% safely for several hours, so it's a small price to pay for regaining consciousness. During descent, the system ignores pilot input. The only way to disable EDM mode at this point is to disengage the autopilot. Upon leveling off at 15,000 ft, the system resumes monitoring for pilot input for 4 minutes. If during those 4 minutes the pilot touches the avionics, EDM mode is canceled. If not, a second descent to 12,500 ft is initiated after the 4 minute timeout. The system now ignores pilot input and descends down to 12,500 ft remains there. At this point, the only way to disable EDM mode is to disengage the autopilot. That's all for now folks!

X-Plane 11.20 added an art control that lets me kill the background on the PFD. This has in turn allowed me to design a shader to pull some pixel removal tricks and finally sneak it under there:

If you check out the airport in the map view (M) you can see that the opposite ILS (runway 10L) also has the frequency 111.10. I think it may be possible that you are catching a signal for that ILS inititally. To check that theory, click the checkbox on the general setting page in X-Plane 11 that says "Disable downwind ILSes". Let me know how that goes! Jan

It worked perfectly.. I came across a new problem altogether. Here is whats happens 1) I program my FMC for KSBN -> KORD (PRADY, ILS RWY 28R VOLGR transition). It is a short flight 2) I dialled the ILS frequencies (111.10) for the Captain as well as First officer, entered the CRS as 273 for both 3) During flight and after crossing VOLGR, I engaged LOC. While the LNAV and VNAV was still active 4) This is where the crazy things happen, as soon as the LOC is captured the plane would completely fly away from the APPROACH course. I mean it would start flying to the left. At this time, I had to re-engage LNAV and press LOC when plane lined with the approach path WPTS. It would now capture localizer as if nothing had happened. The CRS remained unaltered. I would then engage APP to land Can someone please help me understand what’s happening here? I repeated this exercise over 4 times (flew from KIND to KORD, chose ILS 28R, VOLGR transition) it did exactly the same thing as mentioned in 4th bulleted point. I checked the CRS for 28R in Chicago O hare’s details, it is 273 (www.airnav.com)

We have some more performance improvements ready to go here, and some small bug fixes. The main thing we're working on is VR support; right now we're waiting for Laminar to look into some things on their end, as it seems as though X-Plane's SDK isn't behaving as it should in VR mode. But that's why VR is still in beta. Right now I'm calling it 4.7, but we haven't really talked about a release plan for it yet.

Hello I would highly appreciate if someone could make a Jordan Aviation livery, for the IXEG such as this one.