OuterMarker

There it is, cheers

You're very welcome. By the way, in the pocket on the left side you'll find the AviTab tablet :-)

I noticed these occasional freezes with the Entegra version as well, although it's definitely less often than every 5 minutes on my system. I'd say maybe twice an hour but I'll pay more attention to it next time.

There is a bug so you can't see the cover but the clickspot still works fine, it's in the net on the right side

Hi, I understand that and I do appreciate your help! I didn't feel the need to post multiple identical logs since neither showed a backtrace (I checked my fully loaded installation, no scenery and vanilla) and due to the nature and replicability of this crash it was obvious to me that this is unrelated to any plug-in or add-on. I get that you can't replicate each and every crash scenario though.

I removed all plug-ins and tried again with an almost vanilla X-Plane. Maybe I wasn't clear enough, to recreate this CTD let the F/O finish the shutdown checklist, scroll back up to TAXI LIGHTS and double click it with the push select button.

Does this really seem like a plug-in issue to you? I doubt it to be honest.

This isn't the original log but since this is reproducible every time I just loaded my latest 1000ft save state and recreated the crash. Log.txt CL650_Log.txt

Hi everyone, after the F/O finished the shutdown checklist I tried to manually advance to the securing checklist page without triggering the F/O to actually start the checklist. This usually works without issues however I accidentally turned the knob twice and landed back on the first item of the shutdown checklist. Without realising this I clicked the "push select" button once, the TAXI LIGHTS item got unchecked and when I clicked "push select" again the sim crashed. After that I loaded the auto save to check if this was actually the cause and it crashed again so I hope this is reproducible. Cheers

I know you guys are busy and I haven't read the entire changelogs yet but I think this has gone unnoticed.

I noticed something odd with the nose gear door extended Edit: Disregard, has already been acknowledged.

Thanks! That's more or less how I've been doing it as well. For more accurate fuel calculations I tried entering the step levels to the respective waypoints during preflight but you have to do it seperately for each waypoint and that felt like they were recognized as constrains and not as a new cruise level.

Hello everyone, is there a (correct) way to enter step climbs into the FMS? Or do I just initiate the climb when it's time to do so without telling the FMS beforehand? Thanks

Thanks. While this happened I googled and found the manual of a Proline 21/FMS-3000 that said: "Delete extra waypoints/legs, or wait until there are fewer than 100 legs in the flightplan." which made me think I would eventually be able to enter the complete arrival. This was the flightplan suggested by SimBrief. ~2800NM, 74 waypoints + 4 SID + 17 arrival + 3 missed app = 98 + TOC and TOD? EDHK LUGE1N LUGEG Z998 RAMAR L23 TORLO BINKA M602 VAVUN L996 DENKO L619 ADVAB L981 INROG M860 KUGOS UM860 SIN UW704 CRM UM688 ULTED UT301 IMKEN W3 KIXOB UL223 EGSIR T217 RUBAK UL223 TOTNO T217 DASDO UL223 LAGSA T217 LAM UL223 SIR L223 VUTEB VUTE3C OMDB

Is time acceleration okay or does this cause the same issue?

Thankfully I was aware due to this thread but it would have happened to me as well.

Happened again with other STARs as well. I tried to enter the waypoints manually and at one point it said "FPLN FULL", maybe that's the reason it crashed when selected? I now have 25 waypoints + 4 missed approach remaining and still get "FPLN FULL" when I try to manually add a waypoint to the arrival

Loaded the save state, tried again and it happened again so this should be reproducible. Log.txt CL650_Log.txt

Hi, after an uneventful 5 hour flight I chose the ILS 30R at OMDB and after I clicked the VUTEB3C arrival the FMS stopped responding, I got an FMS-FMS DISAGREE message on the right FMS followed by a CTD seconds later. Cheers CL650_Log.txt Log.txt

Hi guys, I was well into my preflight, probably 30 minutes. Walked into the FBO ~5 minutes prior to the CTD to issue my preflight request with 2 crew, 8 pax and the fuel truck. I went back to the cockpit and didn't touch anything from that point to the CTD. The fueler arrived and asked for my request, I was checking my phone so I didn't immediately react and after about 40 to 60 seconds the CTD occured. If you need anything else let me know. Cheers Log.txt

Hi guys, the Challenger looks beautiful inside and out but maybe due to the X-Plane light bleed issue the wood looks extremely shiny and reflective. I don't know much about texturing but if there is a way to somewhat reduce this in the future I'd highly appreciate it! Cheers

Click one of the ATS disconnect buttons on the thrust levers and then re-engage using the ATS button in the Glareshield.

Hi guys, I noticed that my log has over 3000 identical FMOD error lines. 0:04:34.469 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. Cheers Log.txt

Thank you very much! I took a lot of screenshots as well but there are no further problems. I switched to ADC 2 and was able to continue the flight before I noticed all of this was caused by the covers being on. After all this is a nice demonstration of the system depth On an unrelated note, I did notice that when reaching TOC and TOD I get single digit FPS for a couple of seconds but I've only completed one flight yet so I'll get back to you if this persists.