46 minutes ago, rob0203 said:

Bought it after allways PMDG

Really like it!

A few notes:

Catching the glidescope at ENTC was a drama

The glidescope was allready active before it was visible on the PFD? And then it pitched up dramatically trying to catch the glidescope still a few dots above? How can there be GS in green on the PFD while the glidescope is not captured?

Really strange behaviour when finally catching the Glidescope the plane was going up and down and in overspeed. Had to land manually.

Is this BETA behaviour? Anybody else has this?

Will test again tomorrow

There is an option in the EFB to choose whether to allow glideslope capture before localizer capture.  I would recommend turning this off.  I don't know of an airline that does it and cannot imagine a scenario in which you would want to; there are several threats associated with this.

The iFly tracks an ILS and will autoland very nicely so can't say what happened to you, but I'd definitely try again with it set up to not capture GS until capturing localizer.

2 hours ago, Claudius_ said:

I'm not satisfied with your explanation because I think that you are not assuming the lack of power of the engines at higher altitudes, the mach number you are talking about is varying with the altitude: more altitude, more higher the mach number because the air density, temperature, etc. But this has nothing to do with the vertical speed, where you can see a very strange climbing jump where the engines are struggling to push the mass of a full loaded airplane when closing to the max planned altitude. Secondly, but not least important, this Ifly 737 is just the only one sim airplane behaving in this way, maybe the other devs are all wildly wrong on this aspect?

Well, I'm not "assuming" anything.  I've done this a few times 😉.

I did say that once latching onto the mach number and climbing that way for a while, climb rate will decrease as you get into the mid 30s (which I believe the iFly exhibits).  But certainly, when the transition occurs (which seems to be what you're talking about) climb rate will increase and the increase will be sustained for a while.  I just can't understand why this seems unusual to you; how could it not?  Let's say the transition occurs at 280.  The engines aren't making appreciably less thrust at 280 than they were at 275.  So of course climb rate will increase as you start trading IAS for climb. 

I mean, when climbing out really heavy on a warm day from somewhere, we all start looking forward to the transition for the climb rate boost if the jet is starting to struggle.  This is certainly a real world effect.

15 minutes ago, Stearmandriver said:

There is an option in the EFB to choose whether to allow glideslope capture before localizer capture.  I would recommend turning this off.  I don't know of an airline that does it and cannot imagine a scenario in which you would want to; there are several threats associated with this.

The iFly tracks an ILS and will autoland very nicely so can't say what happened to you, but I'd definitely try again with it set up to not capture GS until capturing localizer.

Thanks! I was already thinking about if there was such an option. Will turn it off!

I've done a few landings now and I have to say it is so much fun to handfly, especially the flare feels very intuitive.

Is it free for the 2020 version users ? Where can I download it  ?

22 minutes ago, solito said:

Is it free for the 2020 version users ? Where can I download it  ?

Yes, just update the ifly manager and you’ll have an option to install the 2024 version. 

Bought the ifly because it's on both sims now for $69.95 AUD it's a steal 

have installed it in 2024, i keep getting invalid route 1 uplink message all  the time have to enter  the flight plan manually. Have no issues with the 2020 version and yes i have entered my id in the acars options. So what steps am iam missing out on.

edit  i noted  that my malware has quarantined the simbrief new.exe  with  malware AI.3872421375 which most likely a false positive ?

Edited June 14, 2025Jun 14 by pete_auau

11 hours ago, Stearmandriver said:

Well, I'm not "assuming" anything.  I've done this a few times 😉.

I did say that once latching onto the mach number and climbing that way for a while, climb rate will decrease as you get into the mid 30s (which I believe the iFly exhibits).  But certainly, when the transition occurs (which seems to be what you're talking about) climb rate will increase and the increase will be sustained for a while.  I just can't understand why this seems unusual to you; how could it not?  Let's say the transition occurs at 280.  The engines aren't making appreciably less thrust at 280 than they were at 275.  So of course climb rate will increase as you start trading IAS for climb. 

I mean, when climbing out really heavy on a warm day from somewhere, we all start looking forward to the transition for the climb rate boost if the jet is starting to struggle.  This is certainly a real world effect.

Maybe we are talking about different things, fortunately the dev gave me less elusive answers than yours and they will give a look on this "strange" V/S behavior.

I have a question about IFly's cockpit interaction system:

How does one turn dials clockwise other than with the mousewheel? I figured out that if you hold the left mousebutton you can turn dials counterclockwise to decrease inputs faster. But I haven't figured out how to do it into the other direction and using the mousewheel takes ages.

 

I tried a search in the Manual but didn't find anything.

22 minutes ago, Farlis said:

I have a question about IFly's cockpit interaction system:

How does one turn dials clockwise other than with the mousewheel? I figured out that if you hold the left mousebutton you can turn dials counterclockwise to decrease inputs faster. But I haven't figured out how to do it into the other direction and using the mousewheel takes ages.

 

I tried a search in the Manual but didn't find anything.

Right click.  The problem may be that there is an action assigned to the right mouse button by default - a temporary free look tool.  De-bind anything else the right mouse button is doing.

34 minutes ago, Claudius_ said:

Maybe we are talking about different things, fortunately the dev gave me less elusive answers than yours and they will give a look on this "strange" V/S behavior.

What do you find "elusive" about my answers?  I'm trying to find the easiest way possible to explain this to you.

I remember when this was brought up in the dev forum.  The conclusion was that you were talking about the transition in the climb schedule from IAS to mach, and so therefore no bug, working as intended.  If that's not what you're talking about, what do you see as a problem? 

I do notice that you seem to have decided there's no longer a bug in the green banana behavior after seeing a real-world photo.  Would one help for the climb question too?  

Edited June 14, 2025Jun 14 by Stearmandriver

30 minutes ago, Stearmandriver said:

Right click.  The problem may be that there is an action assigned to the right mouse button by default - a temporary free look tool.  De-bind anything else the right mouse button is doing.

That was the solution. Thank you!

I had the same problem.  But I knew how it was supposed to work from 2020, so eventually figured it out.  Probably took me longer than it should have 😁.

Another issue I have is that this thing will not obey the FL100 speed restrictions in VNAV descent. If you are above profile it continues to stay in VNAV PATH instead of going into VNAV SPD and thus blows the restriction.

I don't remember the NG's doing that.