ois650

There have been no other reports of this happening and given the checklist is due a complete re-build we will consider this closed.

There have been some fixes to hold exits since this was posted. We will consider this closed as fixed in 1.5. Brgds

Logged, thank you.

Unfortunately there's no backtrace or sign of a crash in your log file, it just stops. VRAM may be an issue.

Airframe is definitely borked. I will pass this on.

I attempted to replicate this on 1.5, the behaviour of my CDU was identical however I did not get a crash on pressing continue (tried multiple times). We'll call it non-reproducible for now but if it happens again I'm happy to dig further. Brgds

@BottleRocketeerfiled for investigation, thanks. @fleXiBleunfortunately your log file does not contain a backtrace, it just stops. Make sure you are sending the log directly after your sim crashes.

Good afternoon, Thanks for your report, I have filed this for further investigation. Best regards

The avionics allow you to do that already

There's been some changes to how TACAN/DME works in X-Plane over the years. It's caused issues in other airplanes before so I would put this one down to X-Plane. It would seem that X-Plane 12 TACAN will behave properly.

It won't arm because you've no takeoff N1 value. Enter the temperature in your thrust limit page and try again.

Thanks for the report, it's possibly the way the ATC plug-in has formatted the message. We'll take a look.

Correct

Hi Lukas, Unfortunately unless there's a backtrace to the Challenger there's not much we can do. Any crashes we've seen so far have been clean crashes with traces, not freezes. Perhaps check Event Viewer if it happens again.

Hi Mark, Should be no issues with replay mode.

There has been no changes to the Challenger since the 12th of February.

@zrh28 apologies for the radio silence here. At this point in time work is ongoing on new features and outstanding bug fixes. It is worth mentioning that any new features have been in the works for a long time and are not taking precedence over the start of VR work. As there is no official development roadmap I cannot give you a timeframe of when VR compatibility will happen. I can tell you however that it is most definitely on the list as a significant minority of customers are VR users. Brgds

Hi Tim, This has now been logged. Brgds

Hi Tim, Apologies for the delay in responding. I have requested that the F keys, escape, return, enter and tab are made exempt from CDU keyboard capture. Brgds

Hi Tim, A checkbox would be useful. I am unsure as to how changeable the pilot actions are on the fly, but I have made the request. Brgds

If you're flying offline then realistic atmosphere is enabled and there will be a difference between XP's altitude output and the Challenger's indicated altitude. --------------------------------------------------------------- This is being looked into and any updates will be posted here. Seeing as this issue was fixed in the first update this is quite unusual.

Everything is modelled, so using the QRH/FCOM to troubleshoot is the way to do it.

Even though it's covered in equipment fields, operators still file NAV/SBAS. For reference, this is what I am using: PBN/A1B2B3B4B5D1S1 NAV/SBAS DAT/1FANS2PDC SUR/260B RSP180

Hi all, I will report this for fixing in the next update. Thank you. Brgds

Interesting, thanks for linking.