Repository navigation
FOQA-Sim 0.11.4
0.11.4 ties FOQA-Sim to Pilot Aptitude, the site its landing challenges come from. There is no address to type: Pilot Aptitude is already under Challenges → Sites, and you only press Sign in.
Challenges
- Pilot Aptitude is built in. It is in the Sites list from the first start and can't be removed (you can still sign out). "Add site" is gone.
- “Fly this challenge” works from Pilot Aptitude. As in 0.11.3, the button on Pilot Aptitude puts you on final once you are signed in. Links from any other website are not opened: FOQA-Sim says it opens challenge links from Pilot Aptitude only.
- Before challenges open there, the Sites list says "Challenges aren't open on Pilot Aptitude yet." FOQA-Sim checks again when you open the Challenges screen or press Sign in, and once they are open everything works without a restart or an update.
SHA-256 of FOQA-Sim_x64-setup.exe: 6c11c826f2305d18106848dd1b83cf2f5975300867840261e6d3f549da2408ed
Also in this release (0.11.3, not published on its own)
0.11.3 makes a landing challenge a single click: "Fly this challenge" on a site puts you on final in an undamaged aircraft with no traffic around, a crash puts you back there by itself, and the attempt ends and uploads once you stop. It also fixes localizer and glideslope findings on approaches flown without that runway's ILS.
Challenges
- “Fly this challenge” on your own site puts you on final. From a site you are signed in to, the app no longer asks or stops at the briefing: it takes the challenge, places the aircraft and starts the ranked attempt. If something is red in the pre-flight check (no flight loaded, another aircraft), it shows the briefing with what to fix. Links from other sites still ask first. An attempt still open from earlier makes way for the new one.
- Every attempt starts from the same clean start. The first attempt saves the start as a clean flight; every attempt then loads it back, waits for the sim to settle, and places you at the start, so a crash or damage never carries into the next attempt. It takes about 15 seconds and is shown in the attempt log. If the sim does not finish loading within a minute, nothing is placed and the attempt asks you to fly again, rather than leaving you where the sim later moves you.
- No other aircraft during a challenge. The clean start has the sim's AI air traffic off, so no airliner crosses your final and leaves its wake behind.
- NAV1 is tuned to the runway's ILS when you are placed, if that runway has one.
- A challenge flight starts at the challenge start. Placing you on final now ends the flight you were in (kept as its own flight, or dropped if it was only a few seconds) and starts a new one on final; the attempt, its debrief and its analysis all use that one, with no takeoff that never happened.
- A crash flies you again by itself. The sim does not report a crash to other apps, so FOQA-Sim reads the impact: a touchdown at 4 g or 2,000 fpm or more ends the attempt and starts reloading the clean start a second after the impact.
- Wing, propeller and nose strikes are crashes. A landing that ends with a wingtip or the propeller on the runway (a ground loop or nose-over, or touching down with a wing too low) no longer scores: the attempt ends as a crash and Fly again starts by itself, the attempt log says what struck, the grade is held at zero and the debrief shows it as a high-level event. FOQA-Sim tells it from the attitude on the ground (more than 12° of bank in a light aircraft, 8° in an airliner, or the nose more than 5° down, for half a second).
- A challenge finishes when you stop. Once the aircraft has come to a stop after the landing (under 2 kt for 3 seconds), the attempt is graded and uploaded at once; no need to press Finish or wait two minutes.
- Every challenge is graded the way the debrief grades the landing. A challenge file may name an older scoring method (landing-1, landing-2); it is now always graded with the current landing assessment, so the attempt's score and the debrief's never disagree. The briefing shows the method actually used.
- Signing in to a challenge site works with sites that route in the page address (like Pilot Aptitude): the sign-in request now reaches the page.
ILS deviations
- Deviations count only when you land on the runway the ILS belongs to. With another runway's ILS tuned (a parallel runway, the opposite end, another airport) the needles still move, often to full scale, but say nothing about your approach, so localizer and glideslope findings are left out there, as a real FDM program does.
- How FOQA-Sim tells: the recorder now records the localizer's course. The ILS belongs to the runway you landed on when that course points along the runway and the localizer needle is near the middle as you touch down on the centreline. The opposite end points the other way; a parallel runway's localizer points the same way but reads near full scale when you are on this runway's centreline. The sim does not report reliably which airport and runway the ILS serves, so the course and the needle are what is used.
- If you retune on the way, only the part flown on the landing runway's ILS counts.
- Flights recorded before 0.11.3 have no localizer course, so their localizer and glideslope findings are left out entirely: no finding is better than a wrong one. The same goes for the approach before a go-around, which lands on no runway to compare with.
Localizer and glideslope findings may disappear from flights you already recorded; they are analysed again after the update.