amyinorbit

That’s good news though, that means it’s not ghosts! I would suggest running the X-Plane installer again just to make sure your world airports aren’t corrupted somehow (which those log messages seem to indicate). Worth also nuking the whole X-Plane/Output/caches directory too for good measure.

that’s very strange, I can’t reproduce any of that on any of my machines. As a last resort, could you please try with clean X-Plane install? The log still shows some scenery oddities even with stock scenery, which is surprising.

Looking at your log, it definitely looks like there is something weird going that corrupted or seriously messed up the airport cache. Could you try without any third party scenery? you are also running fedora which isn’t - distribution I can test or support more than “best effort”. Was there a system update since the last time this worked correctly?

What happens if you try to manually enter any of said airports in the flight plan?

Hello! Please post a log, this sounds suspiciously like the airport cache has gotten corrupted and isn’t returning all airports. If that’s the case: quit the sim, delete X-Plane/Output/caches/uns1, then start the sim again. That should solve it. as for the date being one month ahead, that’s a known issue with this build. I’ve sent the TorqueSim guys a new build that fixes this and will be included whenever the next update comes out

No, the UNS doesn’t set the NAV1 course. It doesn’t IRL either, it’s just not wired this way with this avionics suite. not sure what you mean by “dial it using HDG” — you’d match the heading but with your current heading, then switch the AP mode to HDG. Then change navigation sources to NAV1, set the ILS/LOC front course using the CRS1 knob, then follow ATC instructions u til you can arm NAV or APPR on the autopilot.

Check that there isn’t an FMS message (a yellow flashing “MSG” on the title line of the CDU screen). It’s possible the flight plan file is bad and could not be read (in which case your Log file would be helpful )

To be clear, this is how it is in the real plane — the 525 does not have a separate tiller

To load a pilot route in the UNS-1: Press the [FPL] function key to call up the flight plan page; If there are fewer than two legs on the flight plan, a "COPY PLT RTE" prompt is present on the FPL 1/1 page; Otherwise, Delete the flight plan and insert your departure airport. Select the COPY PLT RTE prompt (LSK 4 Right), then pick the route you want in the list As Pils said, the FMS just reads whatever is in `X-Plane/Output/FMS Plans`, and that's what will be listed on that page

For anyone else checking here: the procedure to change the units in the UNS-1 is described in the UNS-1 manual that is installed alongside the plane

So interestingly LittleNavMap seems to have generated invalid v11 .fms files. The departure and arrival blocks should read ADEP ICAO ADES ICAO Since they are both airports. LNM used `DEP` and `DES`, which are reserved for flight plans that begin or end at waypoints (fix/VOR/NDB/what have you). Might be worth letting the LittleNavMap devs know!

Like Cameron said, what you get with other planes doesn't have much to do with it. The CL650 is a bit more GPU-heavy than the TBM and the Zibo. I had a M1 machine when the CL650 was in beta, and I was seeing frame rates similar to what you reported. The M1 is a best when it comes to CPU workload, but its GPU is a bit weak for the Challenger unfortunately.

Yes, we are discussing the ProLine avionics suite, which is modelled in the HotStart 650. The shortcoming you brought up twice now are not with the simulation, but with the actual, real-life avionics. The aim of this add on is to accurately simulate the real avionics, so the shortcomings will not be fixed if they exist on the real unit.

Like @skiselkovsaid for the other case, thats not a bug; that’s how the ProLine 21 draws course-to-fix legs. Once the plane passes 1,100ft, it will do a right-hand turn to establish on the coded course into D266N.

If it has happened twice, could you please try and get a video of it? Aside from arming APPR much, much too early, I'm not sure what could cause it

I cannot reproduce this even by arming approach. My only other hunch is that you accidentally hit the NAV SRC a button on the DCP, which would have caused the NAV source to switch to LOC

Testing this right now, but my suspicion is that you armed APPR while on the star. If that’s the case, the FMS could have initiated a NAV-NAV transfer, thus setting the autopilot to follow the ILS rather than LNAV.

Hello! Could you try an access https://aeronav.faa.gov/d-tpp/2113/xml_data/d-TPP_Metafile.xml in your browser, and see what it says? From your log it looks like there is a SSL issue when trying to get the charts list from the FAA servers.

Okay folks that’s enough, stay on topic and stop with the ad hominem please.

There’s a whole complex dance that the FMSs have to execute, but in normal ops the conditions are: There is a suitable (read: LOC or ILS) approach procedure linked in the flight plan that the plane is in, or that is coming up down track in your FPL; The plane is within 31nm of the approach airport

Simbrief is pretty hit and miss (and “miss” more than often) when it comes to cruise levels. As Graeme mentioned, these numbers are all in the Ops Reference document that comes with the plane — use it

Things you need to check before the pax will deboardm pax signs are turned off engines are shutdown beacon is off cabin door and main door open

It looks like you shut down the battery master switch before the end of the APU shutdown sequence, causing the APU to go into fault mode. If you open the APU servicing panel (under the number 1 engine), you can press the RESET FAULT button and you should be good to go

This issue is caused by running the APR test while the engines are not running. As mentioned by Bruno, running the test again when the engines are running will fix this

More than happy to help!