I'll have a look and also reinstall it, see if i can get rid of this (this is the error i mentioned earlier):

Thanks for the inputs!

18 minutes ago, Nuno Pinto said:

I'll have a look and also reinstall it, see if i can get rid of this (this is the error i mentioned earlier):

Thanks for the inputs!

Fixed this, apparently i had to install VC++ 2022 redist. Such a high price addon and such laziness when testing. Oh well.

FYI, in case someone faces the same problem. the flap 40 setting on startup was an axis MSFS2024 assigned automatically to my TCA throttle quadrant. Removing the assignment fixed the issue.

11 hours ago, Noel said:

, whereas I think iFly's was maybe subbed out to Asobo's UI team

It's the same UI they used in P3D. It's inspired by Boeing's built in EFB UI in the 777/787

  

4 hours ago, Nuno Pinto said:

and such laziness when testing

laziness??

Edited June 19, 2025Jun 19 by Tuskin38

3 hours ago, Nuno Pinto said:

FYI, in case someone faces the same problem. the flap 40 setting on startup was an axis MSFS2024 assigned automatically to my TCA throttle quadrant. Removing the assignment fixed the issue.

Hey Nuno, purchased it early this week but haven't had much time to test it yet, but in a small circuit around LPPT I found it really nice !

I had the P3D version, purchased in one of my step backs from Xp12 and MSFS 2020 🙂

The logic is not the same we're accustomed to with PMDG, that's for sure, but after a while it gets... absorbed :-)

I remember there was some weirdness with the ALT Intv logic. I posted about it back then, but meanwhile gave up on P3D and returned to FS 2020 and Xp12, so, I look fwd to remember what it was, and see how it works now...

This is being a "tough" month for me 🙂 1st the FSLabs 321, then the iFly, today I just found about the FSlabs NEO, and right this week that I had to make a EASA prof check for my SPL in order to get my privileges back .... I'm ruined .... and I don't have a youtube channel 😆

2 hours ago, Tuskin38 said:

laziness??

Well, i am a developer and i make sure all dependencies my applications require are met for whoever uses them. I don't let users deal with errors and "what do i need to make this work". I check if a dependency is met, and if not, automatically point the user to the download or have the application download and install it automatically.

If that's not laziness it's at least lack of attention.

5 minutes ago, jcomm said:

This is being a "tough" month for me 🙂 1st the FSLabs 321, then the iFly, today I just found about the FSlabs NEO, and right this week that I had to make a EASA prof check for my SPL in order to get my privileges back .... I'm ruined .... and I don't have a youtube channel 😆

It's a great time to make decisions. I already have a mid-size airbus fleet and given the high prices FSL practices and given my skill flying these models is far below professional (i'm not trained), Fenix is perfect for me. If FSL has "this and that" over Fenix, i would never notice it, easy to skip. As for iFly, after watching so many videos and tutorials this time around i decided for it. Back in P3D days PMDG was just better but something has changed and the iFly model although different (being a MAX) behaves better so i decided for it.

I don't need a NEO, it's just another Mid Airbus and when i have a MAX, i don't really need a NG - Same thing, different displays 

This is partly joking but i guess you know my meaning haha :)

6 hours ago, Nuno Pinto said:

I check if a dependency is met, and if not, automatically point the user to the download or have the application download and install it automatically.

It does install seamlessly without any need to download additional dependencies - I've had it since they released on 2020, and have installed it at least 5-6 times (including once after a brand new Windows install), and never had this issue.

So it's not broken from the get go, but of course it's possible that it glitched out while you installed and didn't recover - they should make it so that it detects the lack and puts up a more informational message instead of what you saw, which makes no sense till you google it or whatever. 

Is GLS currently functional in MS2024 with the Ifly and a Navigraph Subscription?

When I enter the channel number from the chart into the box and try to swap that over to active I get an error message.

 

And I also don't get the VSD to work. So I guess these are the parts that have not been ported over succesfully into MS2024 from the MS2020 version?

Edited June 20, 2025Jun 20 by Farlis

20 hours ago, Nuno Pinto said:

It's a great time to make decisions. I already have a mid-size airbus fleet and given the high prices FSL practices and given my skill flying these models is far below professional (i'm not trained), Fenix is perfect for me. If FSL has "this and that" over Fenix, i would never notice it, easy to skip. As for iFly, after watching so many videos and tutorials this time around i decided for it. Back in P3D days PMDG was just better but something has changed and the iFly model although different (being a MAX) behaves better so i decided for it.

Yea, I feel the similarly on both points. I will wait to see what Fenix comes up with at release and then decide if I want a NEO and which one to get, there is no rush here. If I want to get a NEO I am far more inclined to the Fenix given their history of engagement with the community and their dedication to their products. FS Labs will need to be head and shoulders above the Fenix in every way for me to go down that road. Given that I just got the 777s and the iFly I am in no rush for another airliner, this will be an autumn decision at the earliest. 

I spent a lot of time researching the iFly and then got it last week and I could not be more happy with the purchase. In my opinion, perhaps naive, it is a better product than the 737NGs from PMDG. Its model, texturing and sounds are head and shoulders above PMDG, its autopilot/navigation certainly appear to me to operate in a more accurate or faithful manner than the VNAV and LNAV simulation in the PMDG, and its systems appear to be well modeled and deep enough for me. Really it is a joy to fly and while I have never flown a 737 it comes across as an authentic experience, which is what I am looking for in a high fidelity aircraft. 

On 6/16/2025 at 3:59 PM, rob0203 said:

Thank you for the detailed explanation, I understand the function of Level Change and what it does in flight.

In different planes it has a different name.

Still is the question is it correct that the Ifly 737 MAX selects a speed on the MCP which is under the minimum selectable speed of 100 kts on the MCP? You can normally not dial a speed lower then 100 on the MCP.

The PMDG I tried it adds +15 knots to the displayed speed

Maybe a but nerdy discussion but what is right?

 

 

 

To follow up... It does this 😁.  So yes it definitely resets your speed to as slow as it can, which you correctly surmised would be 100kts.  So the iFly is correct to be resetting speed to something very slow, but it shouldn't be slower than 100.  PMDG is in error if it doesn't do this.

The "A", btw, indicates that it knows the speed is too slow and the AFDS will enter alpha floor reversion before attaining that speed.

 

Sweet, just got an email that ROAR is updating OI4FS24 so the Opencockpit modules will work with iFly!

Now I just need to get a hold of the SDK so I can program my VRi Overhead to work with the Max via Spad as well.  

MMM...  A fully compatible Max8 with all of my HW modules sounds sublime...  

I realize this only impacts a handful of people but if you are one of them it's pretty exciting! 

5 hours ago, Stearmandriver said:

To follow up... It does this 😁.  So yes it definitely resets your speed to as slow as it can, which you correctly surmised would be 100kts.  So the iFly is correct to be resetting speed to something very slow, but it shouldn't be slower than 100.  PMDG is in error if it doesn't do this.

The "A", btw, indicates that it knows the speed is too slow and the AFDS will enter alpha floor reversion before attaining that speed.

 

Great to see it live in action! Thank you!

hmm normally from memory i use MCP speed window identical to V2 on a take off and in the 737 NG you will get an automatic V2+20 update on your MCP speed for climb out speed.

In the Max it  remains at V2 speed in the MCP . I did not recall the white bug.

Otherwise a blast to fly in MSFS2024

Michael Moe

Edited June 20, 2025Jun 20 by Michael Moe

1 hour ago, Michael Moe said:

hmm normally from memory i use MCP speed window identical to V2 on a take off and in the 737 NG you will get an automatic V2+20 update on your MCP speed for climb out speed.

In the Max it  remains at V2 speed in the MCP . I did not recall the white bug.

Otherwise a blast to fly in MSFS2024

Michael Moe

This is dependent on whether VNAV is armed off the ground.  If VNAV is not armed, the bugged speed will remain at V2 even though the TOGA flight guidance will command a climb at V2+20 (assuming you haven't lost an engine).

If VNAV is armed for takeoff, it becomes the active pitch mode at 400ft and you will see the speed bug jump to V2+20, but you will also see the MCP speed window close (go blank).

Reviewing one of my recent takeoffs in the iFly, I can verify that behavior in VNAV is correct.  I'm not sure I've ever done a takeoff in it without having VNAV armed so I can't say offhand if that's correct.  But in either case, you should not be seeing the bugged speed in your MCP change to V2+20.  It should either remain bugged at V2 (even though the guidance will be commanding V2+20), or it'll blank at 400ft when VNAV becomes active.

The white V2+15 bug is definitely present for takeoff in my setup; I believe it is a panel option though, so you might have to make sure it's selected in the tablet.