Graeme_77

Issue 2327 understood and closed. Rather than a fix, the checklist system with be rewritten for a future update.

I've submitted a feature request that the aircraft be aware of rapid and implausible temperature changes (i.e. changes that are not possible for real, and so must come from a weather engine) and uses that a trigger to update the airframe icing state. However that's not without difficulty as the result could be an unexpected change to the wing ice state. If there's a possibility I'm sure the developers will find it when they have the time, but yes for now with external weather sources just be aware of the potential for ice to be present if the Challenger sim started up in suitable weather conditions, even where a weather injection engine subsequently changed the weather.

Report 2520 Fixed in v1.3.1, February 08, 2022

Service Bulletin 650−34−009 is embodied on the Hot Start aircraft for RNP [AR] capability. In the future it's planned to have SB 650−34−010 for RAAS and SB 650-34-008 for LCY Steep Approach There are a number of STCs as well which I don't have a comprehensive list of, but the landing lights have been modified to the HID landing lights, and you can see the loads for the front units modelled in 3D on the bulkhead beside the WXR antenna. I'll add this information to the Operations Reference Manual.

There is no documentation for the file. As you've seen it's mostly self explanatory. The FO actions and checks are coded into the software and triggered by the XML so it's a case of copying the actions you want. You can see a text-to-speech checklist with the quick turnaround checklist, where the others have voice files.

Thanks. You need to have one of the system 3 hydraulic pumps running in order for the gear doors to move. External AC or APU running with APU Gen on, then Pump 3A or 3B on.

Thanks for the extra info, have passed it on.

Thanks for the video. What exactly do you think is wrong with the Hot Start Challenger SVS display? For me, it looks very close to the real thing.

@BulatThe G1000 SVS and ProLine SVS are totally separate systems. It's unreasonable to expect two different systems to have the same SVS just like it's not realistic to expect a Windows computer to run iPad software. Furthermore, the Phenom G1000 SVS is not an exact replica of the real G1000 SVS either. Please understand this is proper synthetic vision - a computer generated landscape from a terrain database, not a view from a camera on the nose of the aircraft. Here's a screenshot of G1000 SVS, from the same developer as the CL650. It's not that they don't know how to do it, but simply what you are asking for is not what the real CL650 does.

Also, to add to what @Pilsmentioned - it's the temperature at load time that matters. If you have some weather injector that's putting a temperature in or updating after loading, that could be an issue. If you are having this sort of issue, please get into the habit of checking the temperature on the XP weather screen before loading into the Challenger 650.

Report 2492 Fixed in v1.3.1, February 08, 2022 Although user has fixed, code has been hardened against this failure.

Report 2500 Fixed in v1.3.1, February 08, 2022

Pitch for speed is not really a good way to fly a jet! Thrust for speed, pitch for glidepath. It's not a Cessna ;-) For the OP: Blind FD landing with self-induced LOC and GS deviation. https://streamable.com/qq4nq7

This is not design behaviour, but unable to reproduce this error on the latest version. Can you please double check the latest version (it's not a known fix, but a good place to start) and if possible please provide exact steps to replicate. State save airport, location, restore location etc.

Can you please confirm this happened with the very latest v1.3.1 version? Issue 2589 should improve this behaviour. Also please attached the log.txt from the X-Plane folder after any event like this. Thanks.

@Rodeothanks for the bump, this thread would have been missed otherwise. It was already on the bug tracking system, but I've linked this thread in there to ensure it's not forgotten about.

Report 2309 | 2640 Fixed in v1.3.1, February 08, 2022

Thanks, before I file this would you expect the ETAs shown on the MFD window and data to also reflect the off time? In your screenshot you have ETA 1549 with an ETD of 1600 - is this also an issue? (I'd have to look up how the FMS handles predictions with the ETD specified).

Report 2337 | 2305 Fixed in v1.1r1, January 22, 2022

Report 2357 Fixed in v1.1r1, January 22, 2022

Report 2550 Fixed in v1.3.1, February 08, 2022

Report 2585 Fixed in v1.3.1, February 08, 2022

Report 2525 Fixed in v1.3.1, February 08, 2022

Report 2429 | 2586 Fixed in v1.3.1, February 08, 2022

Report 2429 | 2586 Fixed in v1.3.1, February 08, 2022