4 hours ago, MariuszKr said:

Exactly this. Having been in this hobby for over 30 years, I’ve seen how standards have evolved, and we shouldn't be moving backward. We paid for an advanced study-level airliner, not a basic mod where you can just shrug off missing core systems. When key features are cut to meet a deadline, it’s a rushed release, period. Glad to see someone else in this community who actually cares about precision and holding developers accountable.

You paid for an advance study level airliner built for 2020, with a maybe it would be made compatible for a sim platform that wasn't even released yet. Why don't you cool your jets and let them do their thing. It was explained to you why the CPDLC didn't make in the last release and will be implemented in a future update. Everyone with a brain knew the status of the Ifly in 2024 because they were upfront telling everyone that sp1 would be the last update for 2020 before moving on to 2024. It's been experimental from day one for 2024 with just a compatibility patch. There was no hidden agenda or conspiracy. The plane flies and works fine until they release whatever the next update. until then why not find something else to fly until then. Or you can continue to rant.

I can confirm too that iFly 737 Max 8 works great in both 2020 and 2024, and it is completely understandable that 2024 version is experimental, because 2024 is still a moving target developing between frequent System Updates, Imagine the work for developers too, adjusting every time the add on for new sim versions.

Unfortunately I had my 3rd CTD at the 2 to 2.5 hour mark with the iFly MAX 8 in FS2024 today. Last night I completely uninstalled and reinstalled it in the hopes it would not happen again. This not something that usually happens on my system with other aircraft and the iFly MAX 8 before SP1.

It is my opinion something is still a bit haywire with the FS2024 install at least for some users. This has been reported by some others out there. I do know its an experimental build but not sure if this specific issue is related to that? Its possible this new build in SP1 is just very resource heavy and many mid level systems just give it up after a period of time. Hopefully someone else out there has found a fix for it? For now I am not going to fly with it much until an update comes out that hopefully addresses the issue.

8 hours ago, MariuszKr said:

Cutting key features like CPDLC to meet a deadline is the exact definition of "rushed,"

I would agree with that statement, as far as it goes. But, it requires a deadline, doesn't it? Where's the deadline here? Where have you ever seen iFly or anyone associated with them announce a release date target for... Anything?

I really don't think you understand CPDLC that well, if you consider it a "core feature" of flight simulation. We don't even bother with it while training pilots in level D simulators, if that tells you anything (it probably should). As someone who does use it every day at work, I'll reiterate what LRBS said - the percentage of use in domestic operations varies quite a bit. Even oceanic, there are large operators who do not have it installed in their 73 fleets. As far as domestic ATC, I'll often verbally communicate with ATC rather than push the buttons even while logged on, because it can be faster and easier on a non-crowded freq to just talk.

Regardless of the importance you place on the feature, the key point is that no one lied to you about anything. iFly told you several months ago that CPDLC was being moved down the priority list, in order to not hold up release of many other features and fixes that are much more "core" to the aircraft.

iFly is such a niche developer, they seem an odd target for this kind of clearly targeted troll account.

12 minutes ago, longhaul747 said:

It is my opinion something is still a bit haywire with the FS2024 install at least for some users. This has been reported by some others out there. I do know its an experimental build but not sure if this specific issue is related to that? Its possible this new build in SP1 is just very resource heavy and many mid level systems just give it up after a period of time. Hopefully

It sounds like they're chasing a memory leak / performance bug associated with the ifly app (orange icon in system tray) in 2024. The problem is, it only affects some users and didn't impact any of the dozens of people involved in testing, so they're having to chase it down now.

The recommendation for now is to not start the iFly application manually, but to use the iFly manager to set it to run automatically when the plane loads in the sim (and then it closes automatically when the sim closes). If you've been starting the app manually, that's worth a try, though I don't think that's the entirety of the solution. But it's being worked on.

4 hours ago, Ray Proudfoot said:

One reason I’ve remained with P3Dv5. Having bought the PMDG737 twice I wasn’t about to buy it a third time.

A third? I bought it 4 times. The 3rd Time however I could use the credit I had from the 2nd time. ;)

7 minutes ago, Stearmandriver said:

We don't even bother with it while training pilots in level D simulators, if that tells you anything (it probably should).

It tells me that the FAA is behind the times, as usual. ;)

20 minutes ago, longhaul747 said:

found a fix for it?

No promise but did you verify you don’t use an old pre-SP1 livery and did you manually delete the WASM folder of the iFly, too?

16 minutes ago, Farlis said:

A third? I bought it 4 times. The 3rd Time however I could use the credit I had from the 2nd time. ;)

When I calculated how much it would cost to buy 170 airports I have in P3D even assuming they were all available I suppose the cost of a 737 pales into insignificance. 😉

19 minutes ago, Farlis said:

It tells me that the FAA is behind the times, as usual. ;)

Speaking of the FAA, I believe the organization deserves closer scrutiny, and in some areas, significant changes may be warranted.

As for this particular topic, there simply isn't enough time during Level D simulator training to cover it adequately. The training syllabus is already packed with critical maneuvers, procedures, and evaluations that must be completed within a limited timeframe.

However, during Initial Operating Experience (IOE), the subject is typically addressed in greater detail, and practical demonstrations are conducted when appropriate. This approach is not unique; many regulatory authorities and aviation organizations, including the FAA, generally rely on a similar training philosophy by introducing certain concepts during line training rather than dedicating valuable simulator time to them.

1 hour ago, Farlis said:

A third? I bought it 4 times. The 3rd Time however I could use the credit I had from the 2nd time. ;)

I purchased the PMDG 737 every platform it was released on. It's been my stable go to 737. Now that Ifly has updated their 737, The competition is on for my wallet.

1 hour ago, Farlis said:

It tells me that the FAA is behind the times, as usual. ;)

The FAA? Are you familiar with AQP training (what all major airlines are using these days?). For the most part, the FAA doesn't tell us what we're training; we tell them. 😉

1 hour ago, Stearmandriver said:

It sounds like they're chasing a memory leak / performance bug associated with the ifly app (orange icon in system tray) in 2024. The problem is, it only affects some users and didn't impact any of the dozens of people involved in testing, so they're having to chase it down now.

The recommendation for now is to not start the iFly application manually, but to use the iFly manager to set it to run automatically when the plane loads in the sim (and then it closes automatically when the sim closes). If you've been starting the app manually, that's worth a try, though I don't think that's the entirety of the solution. But it's being worked on.

I did read this bit of info that iFly put out. Its currently set for auto and I don't launch it manually. It loads automatically when I load the aircraft as recommended. It seems at least on my system the memory issue is still present even when following iFly's recommendations.

1 hour ago, DAD said:

No promise but did you verify you don’t use an old pre-SP1 livery and did you manually delete the WASM folder of the iFly, too?

I did delete the old liveries and install the updated ones. So its likely not that I would think. Now the WASM folder is interesting and I have not deleted it but wanted to do that. This does feel similar to some types of WASM crashes I have seen. Now the irony is where is the iFly WASM folder? I found instructions for locating it but interestingly the iFly MAX was not listed in there. I believe it was in the past but I wonder if they somehow moved it?