How the further plans for the iFLY MAX8 are goeing on: ( From there discord page )

 

**PLAN FOR THE iFly Jets MAX8**

As we all know, MSFS 2024 is expected to be released by Microsoft on November 19, 2024. We certainly want to be compatible with that new flight simulator as soon as possible. So here is our roadmap:

1.    After release of MAX8 v. 0.2.6 for MSFS 2020 (0.2.5 is the current pre-release), we will work as quickly as possible to make the official release v. 1.0.0 available.
2.    Following the release of v. 1.0.0, and MSFS 2024, we plan to re-focus development on MSFS 2024 compatibility.
3.    As part of the compatibility process, existing bugs will be fixed to the extent possible, which will be part of both MSFS 2020 and 2024 (with differences that may be defined by the simulator).
4.    Following the release of the iFly Jets MAX8 for MSFS 2024, work will resume on the MSFS 2020 version, which will lead to Service Pack 1 (SP1).
5.    The changes/updates made for the MSFS 2020 version will be incorporated in the MSFS 2024 version. As before, simulator specific items may result in differences.

When we have the time to completely examine the MSFS 2024 SDK, we will know what needs to be done to ensure compatibility for the current MAX8. Please bear with us as we unpack that process. All initial purchasers (which means you 😀 ) of the MSFS 2020 edition of the MAX8 will get a free upgrade to the MSFS 2024 edition.

Thanks to all for your support of the iFly Development Team and the iFly Jets MAX8 for MSFS!

Please note that plans are subject to change, but the above is where we are currently at. We’ll have further announcements when significant information becomes available.

 

cheers 😉

complete mess on my current flight .. nonsense ETA and drawings, T/D appearing out of nowhere (i'm no where close to my destination)

58 minutes ago, cepact said:

complete mess on my current flight .. nonsense ETA and drawings, T/D appearing out of nowhere (i'm no where close to my destination)

That's because you have a disconnection. Fix the gap and it should all be normal again (not saying this is what is supposed to happen with a disco, but at least it's an easy fix)

8 hours ago, cepact said:

complete mess on my current flight .. nonsense ETA and drawings, T/D appearing out of nowhere (i'm no where close to my destination)

Also it’s SOP to blank the expanded engine displays after engine start - the idea being that any anomalies will cause the expanded display to pop up and catch your attention. Yes, I am fun at parties 😂 

8 hours ago, Fiorentoni said:

That's because you have a disconnection. Fix the gap and it should all be normal again (not saying this is what is supposed to happen with a disco, but at least it's an easy fix)

There was no disconnection.

It's actually a reproducible bug

Load flight at CYYC and enter/load the following flight plan (I load from simbrief)

CYYC/29 N0454F350 DCT LOMLO Q961 TULOV DCT IMOTA DCT KAIIN DCT 52N090W/N0450F370 DCT YKQ DCT VANSI DCT 50N065W DCT MIVAD AVALN5 CYYT/28

After you enter your perfs for takeoff you should have "insufficient fuel" message appear, along with the drawing & ETA bugs between 52N090W and YKQ

18 minutes ago, cepact said:

There was no disconnection.

It's actually a reproducible bug

Load flight at CYYC and enter/load the following flight plan (I load from simbrief)

CYYC/29 N0454F350 DCT LOMLO Q961 TULOV DCT IMOTA DCT KAIIN DCT 52N090W/N0450F370 DCT YKQ DCT VANSI DCT 50N065W DCT MIVAD AVALN5 CYYT/28

After you enter your perfs for takeoff you should have "insufficient fuel" message appear, along with the drawing & ETA bugs between 52N090W and YKQ

But you do have a disconnect because you are not connecting from the 52N090W point to YKQ. Do the Legs pages show correctly?
 

Try inputting the flight plan without the additional "/N0450F370" speed and altitude. See if it connects to YKQ.

13 minutes ago, mmcmah said:

But you do have a disconnect because you are connecting from the 52N090W point and YKQ. Do the Legs pages show correctly?
 

Try inputting the flight plan without the additional "/N0450F370" speed and altitude. See if it connects to YKQ.

The issue appears after entering the perfs, the legs pages are fine (no "discontinuity") and the drawing is fine also before entering the perfs.

1 hour ago, cepact said:

There was no disconnection.

It's actually a reproducible bug

Load flight at CYYC and enter/load the following flight plan (I load from simbrief)

CYYC/29 N0454F350 DCT LOMLO Q961 TULOV DCT IMOTA DCT KAIIN DCT 52N090W/N0450F370 DCT YKQ DCT VANSI DCT 50N065W DCT MIVAD AVALN5 CYYT/28

After you enter your perfs for takeoff you should have "insufficient fuel" message appear, along with the drawing & ETA bugs between 52N090W and YKQ

I had this issue last night.  I had to manually enter some coordinates.  Between two of them, no magenta line was drawn.  As a test, I just the airplane go.  It stayed in LNAV but just started making 360s.  I had to re-program the FMS to go direct to the waypoint I wanted.  Also, with the LAT/LONG I had to manually enter, it never filled in the speed and ALT (Mach 79/FL350).  I had to manually enter that too.  When I did that, for some reason the airplane went into DES mode and wanted to descend.  I had to go into the VNAV page and re enter my cruise ALT and the airplane went back to normal cruise.  I had pause at TOD armed and when it went into VNAV DES it also paused the sim. 

Wasn't the best crossing.

Question.  I was flying EWR-OPO.  I build a route on simbrief and exported the route via the simbrief exporter (Route A).  After exporting, I realized I wanted a different route (Route B) so I regenerated the route and again exported.  The route displayed fine on Navigraph and Little Nav Map (Route B) but when I pulled the route on the FMS it loaded route A.  Any ideas?

I'm also having issues with VNAV.  When I get to TOD, I reset MCP to lower ALT and hit ALT INTV.  For some reason, the airplane pitches down and over speeds.  I get like a 6,000' per min. descent and the engines spool up.  I gave up and have just been manually descending.  

 

On 10/26/2024 at 4:38 PM, MT70 said:

Did you have the issue the one I am experiencing where the EFB is stuck on "Loading Chart". Your help will be appreciated as I have tried numerous times to clip the needed charts and then open.

I did not, I just didn’t understand how to obtain the rest of the charts. 

8 hours ago, bennyboy75 said:

Also it’s SOP to blank the expanded engine displays after engine start - the idea being that any anomalies will cause the expanded display to pop up and catch your attention. Yes, I am fun at parties 😂 

It's not SOP to blank the engine display. 

7 hours ago, Dreamflight767 said:

I had this issue last night.  I had to manually enter some coordinates.  Between two of them, no magenta line was drawn.  As a test, I just the airplane go.  It stayed in LNAV but just started making 360s.  I had to re-program the FMS to go direct to the waypoint I wanted.  Also, with the LAT/LONG I had to manually enter, it never filled in the speed and ALT (Mach 79/FL350).  I had to manually enter that too.  When I did that, for some reason the airplane went into DES mode and wanted to descend.  I had to go into the VNAV page and re enter my cruise ALT and the airplane went back to normal cruise.  I had pause at TOD armed and when it went into VNAV DES it also paused the sim. 

 

I did not edit the flight path, same as you I let the airplane go, it started doing a 360° turn, I reinserted the next waypoint and everything got fixed, no issue for the rest of the flight.

7 hours ago, Dreamflight767 said:

Question.  I was flying EWR-OPO.  I build a route on simbrief and exported the route via the simbrief exporter (Route A).  After exporting, I realized I wanted a different route (Route B) so I regenerated the route and again exported.  The route displayed fine on Navigraph and Little Nav Map (Route B) but when I pulled the route on the FMS it loaded route A.  Any ideas?

 

Change your destination to the destination of route B before requesting again

Edited October 28, 20241 yr by cepact

3 hours ago, T_Bone said:

It's not SOP to blank the engine display. 

It is at some carriers.  It actually was for us when we first took delivery of Maxs, but they backed it off to optional pretty quick after we pointed out that it removes the ability to note things like decreasing oil quantity or increasing vibes during a routine scan.  But it actually is a Boeing recommendation.

10 hours ago, cepact said:

There was no disconnection.

It's actually a reproducible bug

Load flight at CYYC and enter/load the following flight plan (I load from simbrief)

CYYC/29 N0454F350 DCT LOMLO Q961 TULOV DCT IMOTA DCT KAIIN DCT 52N090W/N0450F370 DCT YKQ DCT VANSI DCT 50N065W DCT MIVAD AVALN5 CYYT/28

After you enter your perfs for takeoff you should have "insufficient fuel" message appear, along with the drawing & ETA bugs between 52N090W and YKQ

Put a landing runway in next time and see what you get.  I know that it shouldn't be required, but it's an already identified bug that not having a landing runway will break time and landing fuel calculations, and will cause the "insufficient fuel" message.  It's being fixed.  (it's ok if there's a disco between arrival and runway, you just need to have a runway loaded.)

As far as the missing segments, I don't do long sim flights so I haven't run into it, but I think I read on their discord that there is also a known issue about segments drawing correctly if they exceed a certain distance, or are a certain distance away etc.  Can't remember the specifics, but if that's the issue you saw, it should also be getting fixed.

Not sure if it's already been mentioned in this thread. On several occasions during the takeoff roll, I've had engine 2 just spooling up to 60% or so, requiring me to abort the takeoff. Has anyone else experienced this? On the 2nd attempt it's been fine. 

1 hour ago, Stearmandriver said:

It is at some carriers.  It actually was for us when we first took delivery of Maxs, but they backed it off to optional pretty quick after we pointed out that it removes the ability to note things like decreasing oil quantity or increasing vibes during a routine scan.  But it actually is a Boeing recommendation.

At first you couldn't monitor the engine display on takeoff? I could understanding PM not having engine displays, but the PF should at least, unless I'm confused at what the other guy was getting at.