Rastuasi

The default version on the store is NOT 12 compatible, you'll need a specific invite for that.

Most likely, I had same issue since prior to the last update, we were instructed to close it if asking on discord

Checklist in this bird has you pressing TO/GA before taxi, so perhaps you're doing it out of order?

Considering the validity and legality of that link is in question, no Hotstart shouldn't bring awareness to it. Us users can share, but not them.

Interesting, well it's worked in the past. I'll copy back in my backup of the previous CL version and confirm again while watching the datarefs.

I saw the AP engage button not working either. This was both trying via joystick assignment, saitekpanel AP button (using your ini @Pils) and via dash AP engage. Everything was setup as done in previous versions. Is there a dataref I can monitor to see if it's being properly triggered.

You only want to use VNAV in climb during an immediate SID that has alt and/or speed restrictions. Do not use it full the full climb as you will end up crashing the plane. It is already documented here that you use IAS/FLC mode to climb long term. The ATS will shut off if on climb too long and the AoA gets too high/speed too low due to temperature checks

No i agree that you need your own report, but there's now 3 CTD that happened at APU gen shutdown, thus a pattern may be forming. My reload is due to corrupted airframe, guessing that the CTD caused the state to not save correctly.

Haha, guess you didn't watch Toto's streams then? He showed that menu off in those.

Your apu crash may be related to mine:

Might be related to my report: https://forums.x-pilot.com/forums/topic/24078-filed-2802-ctd-upon-turning-off-apu-gen/

@oisin650 Please find attached the mp4 of the crash. I cut out cruise, descent and landing as those went as expected (minus a semi awkward landing in 34 knot gusting with 14knots of it being crosswind. I also cut out the stupidly long taxi I had to do due to poor planning on arrival runway (needed opposite side of Orlando). However, I show the post-landing checklist, engine shutdown and securing. It was on securing, I shut down the APU GEN, clicked the ISO and 10th Stage buttons, went to press packs and the CTD happened. Hopefully this helps! If you need other portions of the flight let me know! Do know, I didn't record take off nor climb, forgot to start OBS.. so only have cruise and onwards. CL60_CTD.mp4

@oisin650 I may have recorded video of my shutdown as of that first crash. It may present nothing, but I can snip out down to the taxi to shutdown and upload if you think it'll help. I thought maybe it was something I did, but I did the same process this time and it worked. So please let me know!

Did a few more tests today and yesterday. Tried loading up the previous airframe, but this time not restoring trajectory, simply putting it at a new airport on the other side of the country, same crash as the previous logs. Loaded up a separate airframe, did flight from KGLD KCBK VOFWE FEGIT KGLD doing the RNAV 30 approach. Parked, shutdown and all went without a hitch. So at this point, I think something wacky is up with the airframe file possibly and the libc.6.so is having issues with it? Attached that airframe as it seems specific to it. Additional details: OS: Arch based linux, custom distro. Gnome: 41.3 Windowing System: X11 Graphics: Nvidia RTX 3070 Processor: AMD Ryzen 7 3700x 8-Core x16 RAM: 32 GB 3333b0f3dd3b6a71f7720a27.zip

Tried loading up on approach, 10 minutes before the CTD and I get a "wind sheer" alert after unpausing and then a CTD. Tried without any custom scenery or plugins, please see another set of logs attached. Not sure if it helps pinpoint, but I loaded up a different airframe that I had, loaded up the battery, turned on apu and let it sit, then loaded up the APU GEN and then shut down APU Gen and APU without issues on that airframe. CL650_Log.txt Log.txt

Upon reloading into airframe to try to continue shutdown of battery, same CTD, plane is not in a useable state for the moment.

Completed a flight from KLAL to KMCO, upon turning of APU GEN got a CTD. CL650_Log.txt Log.txt

Odd cause I never use real date and time, updated my navdata last night, just checked and yep, sim date says 2018, no crash and it doesn't error out in fms, sees the update just fine.

That's not classified as maintenance technically. You're not changing the oil, you're merely filling it up from the reservoir, similar to filling her with fuel. Maintenance on oil would be the 50 hour replacement.

Then you're not doing the proper adjustments up the FLs, for long cruises you'll do step climb and slow down as you lighten up to a M.72 cruise speed. Doing so, you'll see 4000 nm easily in this CL60.

Correct, FO waits 2 minutes then does the apu transition checks, once done he turns on the apu gen and moves onwards.

It's not a matter of "reading out" he will. If you have your hints on, it'll show a . in the top bar. Basically, once you hit that, the FO waits for the APU to fully warm up and then he'll proceed. It generally takes 2 minutes and you do not have to manually mark anything complete.

It will also fail if you are climbing long term in VNAV mode as it ends up pitching too high up to try to meet the climb to TOD rather than just hold an IAS. If that's the case, exit VNAV mode on longer climbs, lower the nose, pick up speed, once back at speed initiate climb in IAS again and reset the ATS.

And yet, there are those of us, like me, that have left the bird on the ramp during blizzards over night and come back to find no ice buildup. It definitely does not seem to be consistent.

4000 nm is possible when slowing it down to the LRC values. Put in M.72 into simbrief and it'll get you into the safe profile to say you have the range. It defaults to M.80 and that will not be possible. Also know that you will have to manually slow down and climb as you get lighter. I have never done it, but there are discussions galore on the subject in discord and I've seen a thread here before as well.