Graeme_77

Report 2488 Already fixed in v1.1r1, January 22, 2022

Exactly, and you can see that in the FMAs! VFLC / FLC / VVS / VS. Even VALT indicates ALT with VNav so it will capture VPATH.

Scenario 2, part B and C : That’s VNav doing what it’s supposed to do. Either turn it off, or clear the constraint. Use VS or FLC. Scenario 3. Easiest to use FLC at high altitudes, then VS to manage the descent profile accurately at lower altitude. Remember VNav on the 650 is a “modifier”, not a mode like it is on a Boeing. So with VNAV turned on you get VFLC and VVS. Without it you have FLC and VS. The only difference is VFLC and VVS will obey any magenta altitude constraints shown on the PFD, as well as the blue altitude constraint. Hope that makes sense?

Here's the intermediate to final part of the approach when using the TPAPA arrival into WITBY. Again all nominal. https://streamable.com/hqcqzx You can see me select VOR1 using the BRG SRC menu - this doesn't affect the approach, but does allow me to see the ILS DME while using FMS nav.

I've test flown the approach without issue: 5000ft on the arc, 3000 selected with vnav. FMS nav "magenta needles" with the nav-to-nav "blue ghost needles" Approach mode armed giving LOC and GS white FMAs Descending from 5000 with VPATH, and LOC and GS both remaining armed. Establishing on the centreline, nav-to-nav transfer presents the ILS with "green needles" and autopilot transitions to LOC and GS guidance. Becoming properly established. Stable on the glideslope at 2000ft, landing config, no odd indications all the way though. If you are flying the approach differently, can you explain what you are doing in order to provide some steps to replicate? Also please try flying the approach in the sequence shown in the pics to evaluate how that behaves.

Report 2483 Already fixed in v1.1r1, January 22, 2022

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

Report 2482 Report 2302 Fixed in v1.1r1, January 22, 2022

Did you watch the video demo provided in the product? It shows you exactly how to do this. Also pinned to this board

We understand how frustrating crashes can be, but there isn't enough information to help diagnose at the moment, should this event reoccur please send a full copy of the logfile. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

Investigated. Not fixable: Out of memory condition. The machine has utterly exhausted its memory pool. Not really something we can fix. When the OS says we can't get any more, that's it, we can't get any more. We understand how frustrating crashes can be, but this crash is system related. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

Investigated. Not fixable: Out of memory condition. The machine has utterly exhausted its memory pool. Not really something we can fix. When the OS says we can't get any more, that's it, we can't get any more. We understand how frustrating crashes can be, but this crash is system related. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

Investigated. Not fixable: Out of memory condition. The machine has utterly exhausted its memory pool. Not really something we can fix. When the OS says we can't get any more, that's it, we can't get any more. We understand how frustrating crashes can be, but this crash is system related. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

There isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

In this case there doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but there isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

Thanks Bruce. I'll leave the thread unflagged at the moment (meaning it won't go to the developers right now) until we have more information on what's causing the issue. Your help in replicating the issue is appreciated. I've seen a couple of logs mention SkunkCrafts, but that may be coincidental given the timing. Please add to this thread or post a new thread if you're able to identify what plugin is apparently incompatible.

In this case doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but simply there isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

In this case doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but simply there isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

Thread closed. It's not possible to diagnose "me too" or "same problem" posts. We need to see full logs as their own separate thread. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

There isn't a CL650 crash showing in the log, but we'd like to investigate this further. Can you please post the full flightplan, and if possible recreate the error with a screenshot of the FMS FlightPlan before entering the direct-to.

In this case doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but simply there isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

In this case doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but simply there isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

In this case doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but simply there isn't enough information to help diagnose at the moment. We need to try and identify what is causing the crash, so please try repeating a short flight, offline, in a stock scenery area, with minimal plugins. If you get a crash or pause, please allow X-Plane a few minutes before closing it. Then resubmit your crash logs.

In this case there doesn't appear to be a Challenger 650 crash in the log. (waas issues are common, and not a causal factor). That's not to say the Challenger wasn't a factor in the crash, and we understand how frustrating crashes can be, but there isn't enough information to help diagnose at the moment. Thread closed. Please submit any new crashes with a full log.txt file as a new thread to allow tracking. Thanks for your co-operation.

Thread closed. Please submit any full log.txt file as a new thread to allow tracking. Thanks for your co-operation.