skiselkov

Please post your full Log.txt.

Try switching Try changing your audio output device in Windows, then changing it back. Also, try assigning one device as the "default communication device". The reason for this is audio initialization in the GPWS engine failed. Usually just doing these actions solves that problem

Bug has been fixed and the fix will be shipped in update 2. Thank you for reporting!

Found the source of the problem. Fix will be in update 2. Thank you for reporting.

Fixed, will be in next update.

Ah, oops. -50 degrees C ISA deviation is what caused it. I must clamp the ISA deviation value.

I'm afraid this doesn't look like a crash we're causing. No stack trace on the first one and the second one only contains stuff related to apparently the Windows Driver Model audio driver mapper (wdmaud.drv), none of which is under our control.

Fixed in update. The crash was indeed caused by an unexpected FPLN FULL condition. This fix takes care of addressing the crash, not the "FPLN FULL" state. The simple fact that you "only" have 25 waypoints remaining doesn't meant the flight plan isn't full. It counts all waypoints already passed as well. I'd like to see your ginormous flight plan that somehow managed to end up being more than 100 waypoints long.

Crash fixed, will be in next update. Without the route file, I cannot address the underlying route parsing issue. Open a new issue with the route in hand, closing this one for now.

Fixed, will be in next update.

Fixed, will be in next update. As a temporary workaround, it appears you've removed your Custom Data folder, or the contents of it (removed updated nav data) and are attempting to reload an older state file of the CL650 which uses this data. For the time being, your two options are: put the custom nav data back in, or create a new airframe that doesn't attempt reload the old state file

Incorrectly inserted manual descent constraint at the start of the flight plan, the airplane is not allowed to climb after passing a descent constraint: After inputting "C" on LSK 2R, the FMC correctly computes a continuation of the climb:

Can you describe exact sequence of edits you did to set up the flight and the sequencing problem in more detail? I suspect the PBD waypoint got interpreted as a descent constraint (simply adding "1200A" isn't going to necessarily make it a climb constraint, the "^" or "v" arrow above that number is what determines the class of constraint). You can toggle the climb/descent constraint flag on a custom waypoint by putting "D" or "C" into the right side next to the altitude. To elaborate a little bit, I suspect you had no SID, and only a single PBD waypoint that you inserted as a descent constraint (which is the default). Consequently, the FMC thinks the rest of the route to the next MISSED APPR will be a descent path.

This is indeed normal. The reason is quite simple: the ATS needs an N1 limit target to operate. Otherwise, it would have no idea what the maximum allowable thrust is. This value is supplied by the FMC. The FMC uses performance tables made by the aircraft manufacturer to determine what the takeoff thrust limit is supposed to be and if I show what the table looks like, you'll immediately see the source of the problem: Your SAT is +35 C. At that temperature, the FMC has no data to compute a takeoff N1 target, so the target blanks and the ATS goes to FAIL (and cannot be re-engaged). Take the cowl A/I off, FMC goes back to the normal takeoff tables and voila, ATS is back in business.

Thank you, fixed. Will be in next update.

Fixed, will be in next update.

Fixed, will be in next update.

Fixed, will be in next update.

Please don't file multiple reports into a single topic. Makes it difficult keeping track of what was fixed and what wasn't. Having trouble reproducing this one (doesn't crash for me). So I'll try an analytic fix without verifying it.

Excellent report. Reproduced & fixed in next update.

Resolved, fix will be in next update.

I've had this happen once and found it's one of the master WARNING|CAUTION buttons getting stuck. This sometimes happens if your mouse push & release happens on the same X-Plane frame - X-Plane then doesn't deliver the mouse-up event to us and thus we continuously think you're holding the button pushed in.

This also produces a while "EXTERNAL DOOR OPEN" CAS message, which alerts pilots to the fact that some service panel isn't closed and locked.

The ENG BLEED line on that page is only informational. The engines will readjust lower after a bit to try and pull out of the red. If that doesn't happen, you can set a lower N1 target in "TGT" (LSK R3). Then push LSK R3 to activate the reduced TGT value and that will get the ATS to pull back even further.

Thank you, I've managed to reproduce this bug and fix it. Fix will be in the next update.