Good news: they just started testing SP1 in 2024

Bad news: they just started testing SP1 in 2024

Ifly posted this in discord

@everyone It's been a few months since our last report to you on the status of Service Pack 1 (SP1) for the iFly 737MAX, and we wanted you to know about the current status of this major (think huge) update.

First, we would like to dispel false information spread by a few on this server about the status of this complex process. We want to first reiterate that SP1 will not be released to the public until the team believes it is ready. After this update posts, we will not have any response to questions about a release date, etc. Such inquiries and anything related will be deleted without comment.

However, with the above said, SP1 is feature development complete and the beta team is very busy "shaking" the software to ensue there are no regressions or the introduction of new bugs. This is an extremely important, tedious process which is very near completion.

As of this writing, SP1 is now being finalized and we will soon draw a line under this process and prepare the software for release.

Our team, which is spread around the World in different time zones, is working hard to ensure that SP1 provides our users with a most enjoyable simulation of the MAX. Rest assured, we are not at the beach working on our collective tan!

3 days passed since they published "finalized etc etc" on their Discord channel and still nothing published. Ican understand how complex could be that development however I think iFly team is failed this time!

There is still no real Msfs2024 version and still no updates since almost a year or so in general.

I am posting it here because they only do deleting these kind posts and blocking people on their Discord!

These team was much better in the past during Prepar3D times but now,eeh.

Edited May 28May 28 by vortac

1 hour ago, vortac said:

3 days passed since they published "finalized etc etc" on their Discord channel and still nothing published. Ican understand how complex could be that development however I think iFly team is failed this time!

There is still no real Msfs2024 version and still no updates since almost a year or so in general.

I am posting it here because they only do deleting these kind posts and blocking people on their Discord!

These team was much better in the past during Prepar3D times but now,eeh.

You expected it to be released, 3 days after their last update about it? Why?

I get it, it has taken forever and iFly are slow, slow, slow. But it seems you set yourself up for disappointment in this case. There was no suggestion it was imminent.

1 hour ago, JYW said:

But it seems you set yourself up for disappointment in this case.

Simmers in a nutshell, they internally setup timeframes in their head and they get upset when devs don't meet them.

Ok, so you guys are happy to pay 70-80$ to the sim products and wait almost a year to receive promised update. In the mean time you enjoy devs/mods postings on the channels like to sweeten someone's words.

32 minutes ago, vortac said:

Ok, so you guys are happy to pay 70-80$ to the sim products and wait almost a year to receive promised update. In the mean time you enjoy devs/mods postings on the channels like to sweeten someone's words.

Yes. At least they've taken customer feedback onboard. Maybe go and be a developer and see how well you do. At least the aircraft is still flyable.

1 hour ago, vortac said:

Ok, so you guys are happy to pay 70-80$ to the sim products and wait almost a year to receive promised update. In the mean time you enjoy devs/mods postings on the channels like to sweeten someone's words.

That's besides the point, many are unhappy with how long iFly has taken (Though given their team size, I'm not personally bothered). However, iFly has never given strict deadlines so I would never beholden them to one.

Complaining that its been 3 days since their post is just yelling at the wind because iFly never told you that the update would be coming within 3 days, you set yourself up with that expectation.

3 hours ago, vortac said:

Ok, so you guys are happy to pay 70-80$ to the sim products and wait almost a year to receive promised update. In the mean time you enjoy devs/mods postings on the channels like to sweeten someone's words.

When I bought the iFly 737 (quite some time ago), I got what I paid for.

Any further update, especially a free update, is a bonus.

They never promised any timescale, so it's a little naive to be upset that it hasn't come out within 3 days of their last news update.

Even without the SP1 update the aircraft still flies extremely well and is a most enjoyable experience. Having been involved with the team in the past, in a minor consultancy role and beta tester, I can attest to their dedication and commitment to their products. As with all their past service packs it will be worth waiting for.

On 5/28/2026 at 11:51 AM, vortac said:

Ok, so you guys are happy to pay 70-80$ to the sim products and wait almost a year to receive promised update. In the mean time you enjoy devs/mods postings on the channels like to sweeten someone's words.

You paid $70-80 for the product you already own. When you purchased it, you never signed some kind of agreement that said "with this purchase I'm entitled to new updates on new platforms. There are DOZENS of planes to fly in MSFS2024, I suggest you spend less time complaining about a FREE update and go enjoy a wonderful sim that also took years and years to get right.

The problem with closed beta teams is the limited range of user experiences. I prefer the open beta concept, like what we’re seeing with MSFS 2024, because once the final version is released, it’s already about 95% bug-free. This Service Pack 1 is taking a long time, and I’m 90% sure something will go wrong, likely because someone on the closed beta team missed issues with the flight model, or with the flare/rollout phases during autoland, for example.

3 hours ago, Claudius_ said:

The problem with closed beta teams is the limited range of user experiences. I prefer the open beta concept, like what we’re seeing with MSFS 2024, because once the final version is released, it’s already about 95% bug-free. This Service Pack 1 is taking a long time, and I’m 90% sure something will go wrong, likely because someone on the closed beta team missed issues with the flight model, or with the flare/rollout phases during autoland, for example.

Both platforms have their strengths and shortcomings. In my view, one of the most critical factors in this hobby is maintaining a large, active pool of current, qualified beta testers—particularly real-world pilots who can provide operationally relevant feedback. Very few developers fully appreciate the importance of this, and those who do consistently deliver products that stand above the competition.

MSFS 2024 has highlighted numerous discrepancies that can emerge when this aspect of development is not given sufficient priority. It also demonstrates some of the challenges inherent in an open-beta approach when key validation, testing, and quality-control processes are not adequately addressed.

4 minutes ago, LRBS said:

Both platforms have their strengths and shortcomings. In my view, one of the most critical factors in this hobby is maintaining a large, active pool of current, qualified beta testers—particularly real-world pilots who can provide operationally relevant feedback. Very few developers fully appreciate the importance of this, and those who do consistently deliver products that stand above the competition.

MSFS 2024 has highlighted numerous discrepancies that can emerge when this aspect of development is not given sufficient priority. It also demonstrates some of the challenges inherent in an open-beta approach when key validation, testing, and quality-control processes are not adequately addressed.

As I have said many times, real pilots are not an absolute guarantee of "product" quality. While they are experts on real-life aircraft, which is a very good thing, they usually lack experience with home flight simulators, which are very different from professional flight sims.

Moreover, there is a real conflict of interest: real-world pilots sometimes pretend not to see certain issues affecting the product. Additionally, developers often advertise real-world pilot beta teams purely for marketing purposes.

The best compromise is to open the beta process, at least toward the end of the product's development.

We have seen these closed beta team problems time and again, which is why MSFS opened up its beta process. If you want to sell your product, listen to your customers, and don't treat them as if they're dumb.

On 3/16/2026 at 3:59 AM, LRBS said:

 

Thanks, I understand the developer's decision for "keep it simple." 

 

However, with all due respect, I strongly disagree with the statement that, when teaching even a standardized takeoff profile, ASDA, TODA, TORA, intersection departures, performance calculations, etc., are "kind of irrelevant."  

The problem is that data for ASDA, TODA and TORA for a given runway is not contained in any navigation or facility database that MSFS uses - either default or Navigraph. For US airports, that information is contained in the FAA AFD supplement for a specific airport. Obviously, airlines that have their own custom performance apps would have that information in their database, but that info is not contained in any standard MSFS database.