amyinorbit

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!

As highlighted by @RP31, Cowl Anti-Ice must be on, and 2 minutes must have elapsed, for the Supplemental Ground Wing Anti ice test to complete.

Hi! I'm not familiar with the plugin itself, but I believe this is due to the aircraft using a fully custom electrical system, and therefore not setting the expected data refs to indicate the avionics are powered. This has been logged and is being worked on

Could you please create a separate post, and add more data? We can't do much of anything without a log and screenshots of the issue Thanks!

Hi Ed! Thanks for the report. I believe your issue was that you entered "5000A" -- "at or above 5000ft". Therefore, the VNAV solver starts at your most restrictive constraint (the @2100ft one for CF27), then projects the 3° profile back. 5000A doesn't require the solver to put you at 5000ft, but anywhere above that, so it won't show in the VNAV window, because VNAV is not aiming for 5000ft, just checking that whatever profile it comes up with passes SUM above 5000ft. If you want to make sure that VNAV gets to SUM at 5000ft, you can just enter "5000" as the constraint, and once you do so it will show up in the VNAV window. I hope that makes sense!

Hello! Thanks for the reports -- that's noted, the team will take a look.

Hello! Thanks for the report, it’s a known bug. The team is working on it

This procedure is explained in the FMS primer. You can select the secondary database by click LSK3L, then make it the active one by clicking LSK2L. (please note your custom NavdataPro database seems to be out of date by one cycle now)

Hello! Sorry that's happening, could you check what your X-Plane volume sliders are showing?

The aircraft developer can't really create a workaround for that, that's an issue within the driver. I'm dev on the FJS Q400 and the "fix" we have is more of a placebo, it works in some cases but makes things worse in others. I know it's not a satisfying answer, I'm sorry for that, but until AMD decides to do something about it there's not much for the team to do.

Options for what? The navdata provided by Aerosoft should work as it is when you install it to X-Plane\Custom Data. As for charts, Aerosoft does not provide an API similar to Navigraph's, but you can still use FAA and AutoRouter charts (you can log into these services in the Challenger 650 settings window)