GreenPilot86

Thanks for updating us with the probable cause. I wasn't aware that anti-ice was modeled and rarely use it as I am not in a cold-wx area at the moment. However, just for laughs, I tried a takeoff just now from PANC (wx: OAT -4C with light snow) and went through my normal checklist, without activating any ice protection though conditions warranted it. I never got any messages about anti-ice / ice protection. Like you, I generally do not turn on the pitot / static heat until lined up on the runway and ready for TO, so I always see those messages, along with the Parking Brake. I accelerated to Vr and took off, but never got any warning or caution. It seems that in my particular aircraft, anti-ice is still not modeled and like you were able to previously, am able to operate without it. I have never used the Datalink option, I wonder if that is related. Or else something got updated in your sim when this started a few weeks ago?

A couple to add to my already long list that I inadvertently left out: FSLTL traffic injector Grand Tour Flight Planner - this is only before a flight, and only if I am considering multiple flights, to get distances between airports MS Excel has a great FORECAST function that I use to estimate my fuel needs more accurately, in conjunction with my log which tracks actual fuel usage and distances. I can't tell you the number of times Simbrief has declared my fuel insufficient when I've entered my flight data, only to have plenty to spare when I make the actual flight. I also use Excel to evaluate possible jobs and cargo in Neofly.

My workflow for MSFS 2020: (Apps in green are always used, those in purple I only use sometimes) MS Excel spreadsheet (flight logs and planning) Neofly 4 Web Sites: Sky Vector and SimBrief, sometimes Windy as well Navigraph Charts (import Simbrief flight plan) Pilot2ATC (if I decide to fly with ATC) Little Nav Map (import Simbrief Flight Plan) OBS Studio (if I am recording my flight) Add-ons Linker: This will launch the following programs: MSFS 2020, Pop-Out Manager (admin mode), Air Manager (admin mode), FSUPIC7, Axis and Ohs (admin mode) Add-Ons Linker closes once the sim is launched, the rest stay on during the entire flight. I do use the Elgato Stream Deck XL during flight (thank you @guenseli), but I don't use the app itself within the context of a flight, only to add or rearrange / organize buttons occasionally.

I've been flying the CJ4 exclusively in MSFS 2020 for the past 5 or 6 months and have not seen this particular problem. I just now completed a mission PTPN-PKRO without incident. However a couple of months ago I also had something strange happen - on two consecutive flights, as I climbed above 10,000', I got a warning about cabin pressure (do not recall the exact wording) and the cabin simply would not pressurize. I continued the flights without any other issues, but am still baffled as to those occurrences. I suspect something I may have changed in the flight plan caused it but not really sure and have not had any problems in a long time, and have not been able to replicate it. Otherwise, the CJ4 is a beauty to fly in 2020. I guess I would check the flight plans for something unusual, if it's something that's just started. If you can, do a flight from before this started happening and see what happens.

Simbrief for flight planning, but not used during flight. During the flight: Add-Ons Linker to start the following: MSFS 2020 Pop-Out Panel Manager Flight Recorder 0.24.0.0 Air Manager FSUIPC 7 Axis & Ohs Mobiflight GSX Pro Navigraph Charts / SimLink Little Nav Map Pilot2ATC v3 / FS-ATC Chatter FSLTL OBS Studio

Hi, Dave, I know you said it will be fixed. Just as another data point, same issue here with 0.0.26E. Here is my flight plan: TNCB/10 N0323F250 ARUB1R ELUMO DCT DAVLA DCT TNCA/11 Just Validating and then Filing the plan duplicates. It was actually fine in 0.0.26C (different flight plan). Hope this helps.

Pilot2ATC 3.0, early access v. 0.0.20 Today's flight: TFFF - TGPY (routing: TFFF/10 N0318F240 KISE2R KISES A324 DUSAL DCT TGPY/10) Initial clearance was for 6,000'. When I was handed off to Martinique Approach I was given clearance to flight level 120, however, before my co-pilot could respond, ATC started to speak again (presumably to nag me to switch frequencies, this has started happening a lot lately when ATC has a long message for me that includes a handoff.) My co-pilot cut off the second ATC tx to respond to the first one, but all of a sudden my assigned altitude is 7,000' instead of 12,000'. Also I get notice to expect the RNAV approach to rwy 10 (at TGPY, which was correct), but I was barely out of the departure airport when I got this. No further instructions to climb. I asked to climb to FL 240 later (as per the original plan) and was granted. However, after this ATC ignored me until I asked to descend to 3000' just before RIBOR (only 10 or so nm before DUSAL where the RNAV transition is supposed to start.) ATC (by now Piarco Center) denies my request but then proceeds to have me descend to FL 030 (so the same thing essentially!?). After passing DUSAL with no further instructions on the approach I proceed to request the RNAV approach to 10 (which I thought I already had), but ATC just gave me a "...with your request." response. The flight ended there. Am I doing something wrong? Many other flights are OK from start to finish, but a large number end up like this, with ATC just all of a sudden unresponsive. Log is below: Any help is appreciated.

I am having the same problem...ATC forgets about me. This started over the summer with v2.7.0.2. In that version, I could request an enroute descent and sometimes that would "wake up" ATC and start guiding me through the arrival and /or approach. However, where I used to get instructions on what to expect before the TOD, I never get that now. It is the same in v3. On today's flight (KRNO-KHND) all seemed fine until I passed waypoint FUULL at which point I should have been handed off to Los Angeles Center, but never was. I passed the TOD without hearing from ATC at all. Over the past couple of days, I tried requesting an enroute descent, as I could do in v2, however the controller simply said they could not handle that request. I did not do so today, I merely stopped the flight after passing the TOD without further instructions. Log is below. Hopefully this helps. Please let me know if I have something not set up correctly, or doing something wrong, or if you need more info from me.