4 hours ago, somiller said:

Is it possible this memory leak is also causing the EFB to be heavy on cpu use. I have a measly 6700K but the EFB app uses 6%-12% cpu cycles - it's killing performance for me. I had pretty good performance with the previous Max ver., I would say on-par with the PMDG 737's.

I am having the same simular CPU usage with an even older one I7-4770K

Michael Moe

6 hours ago, somiller said:

Is it possible this memory leak is also causing the EFB to be heavy on cpu use. I

I have no idea about that. I guess all we can do is see what changes once the patch is released.

I'm not satisfied of this "new" B38m post patch, it's heavy on resources, but most important I don't like the flight model, I find that now the PMDG 738 is better than this one in this aspect. The devs asked me a video to show the banking problem, but you can easily verify it if you are a good sim pilot. Also, the ILS autoland "fail operational" seems to be a "passive operational". The external lights are too heavy, but this is a FS24 porting problem, but they were heavy in FS20 too, we'll wait for another year or two and the problem will be fixed. At the moment the Ifly B38m is letting me down.

11 hours ago, Claudius_ said:

but most important I don't like the flight model, I find that now the PMDG 738 is better than this one in this aspect.

Oh. My, no. Flight models are not even in the same city, much less ballpark.

I asked before, for clarification on the banking problem, but you didn't explain or show a video of it. You seem to be saying it's related to the autopilot though? Firstly, that's not flight model; that would be an autoflight issue. Secondly though, can you be specific about it? If it's not something unique to your computer and we're all seeing the same thing but you're the only one seeing something wrong...

Edited 4 hours ago4 hr by Stearmandriver

51 minutes ago, Stearmandriver said:

Oh. My, no. Flight models are not even in the same city, much less ballpark.

Seriously. The flight model is one of the best aspects of this plane. I have no idea what they're talking about.

1 hour ago, Stearmandriver said:

Oh. My, no. Flight models are not even in the same city, much less ballpark.

I asked before, for clarification on the banking problem, but you didn't explain or show a video of it. You seem to be saying it's related to the autopilot though? Firstly, that's not flight model; that would be an autoflight issue. Secondly though, can you be specific about it? If it's not something unique to your computer and we're all seeing the same thing but you're the only one seeing something wrong...

I think he's trolling you.

Oh, I don't know. I kind of see what you're saying, but Claudius has been around for a long time; troll posts don't seem his style. I'm willing to believe he's seeing some kind of behavior that's bothering him, I'd just like to understand what it is.

I'm going to do some testing tonight, to verify that engine in-flight start behavior works correctly with respect to pack switch position - which I'm sure it does, but apparently a YouTuber claimed otherwise and now THAT'S being repeated as gospel lol. So many of these things are the result of people misunderstanding general 737 systems, or the differences between NGs and Maxs.

But anyway, I'll pay attention to autopilot banking behavior and see if I can notice anything I have not yet noticed. 🤷‍♂️

Edited 3 hours ago3 hr by Stearmandriver

noticed something with VNAV, it won't respect 250 below 10,000. Never flew the MAX, but a boeing's a boeing. It won't pitch up while in vnav to protect you from the speed limit.

21 minutes ago, V1ROTA7E said:

noticed something with VNAV, it won't respect 250 below 10,000. Never flew the MAX, but a boeing's a boeing. It won't pitch up while in vnav to protect you from the speed limit.

I've seen one or two other reports of this; could you share the conditions it happened under? Were you in VNAV Spd or VNAV PTH approaching 10k? Was there an in-close waypoint with a faster speed restriction etc?

In general, VNAV definitely does respect 250 at 10k (or whatever restriction you put in the VNAV descent page). I've never personally seen it not. But if there's an edge case problem, they'll want to fix it.

During my recent flight which ended up CTD iFly plugin was shown on windows crash report. Too bad I can't send report directly to developers as it automatically sent to Microsoft .

1 hour ago, Stearmandriver said:

I've seen one or two other reports of this; could you share the conditions it happened under? Were you in VNAV Spd or VNAV PTH approaching 10k? Was there an in-close waypoint with a faster speed restriction etc?

In general, VNAV definitely does respect 250 at 10k (or whatever restriction you put in the VNAV descent page). I've never personally seen it not. But if there's an edge case problem, they'll want to fix it.

Nope, it’s happened each flight pretty consistently. I’ll deliberately stay fast with the speed window closed and it’ll blow right through 10 doing 280 kts.

I’ve not tried to descend in ECON since it’s slow with the low simbrief cost indexes. If I remember correctly CI of 35 gave around 280 in the descent. But, I’ve always changed the speed to .xx/280 or 300

Edited 40 minutes ago40 min by V1ROTA7E

Just now, V1ROTA7E said:

Nope, it’s happened each flight pretty consistently. I’ll deliberately stay fast with the speed window closed and it’ll blow right through 10 doing 280 kts.

Well, is it a matter of the VNAV speed not commanding 250kts (actually 240kts below 10k is the default), or is it a matter of the speed being commanded but the plane not doing it?

That's not unusual; the autothrottle mode is Arm during a VNAV descent so that the autothrottles are unclutched and the pilot can be a pilot. VNAV isn't magic; it expects you to add thrust when necessary, and also to add drag when necessary. So, if you're descending in VNAV path, and the speed has gotten fast approaching 10k and remains fast below 10k even though the speed bug is correctly commanding a decel, it's not the plane that isn't doing its job, it's you. 😉. The VNAV path will be built with a decel point to 250kt at 10k, and the plane will pitch up to follow the pre-built decel, but if you start that decel 20kts fast, you're probably going to finish it 20kts fast.

The plane will eventually transition to VNAV Spd and pitch up to chase the commanded speed below 10k, but it won't happen immediately and it won't happen at 251kts. It happens a certain amount of time after exceeding commanded speed by a certain value - could be 10, 15, or 20kts fast depending on operator option. I forget which the iFly has modeled.

But if you correctly use drag as necessary, just like in the actual plane, this won't be an issue.

The earlier version felt smoother and slightly less twitchy in terms of flight control response. The difference is not dramatic, but it is noticeable. Since I am using the same hardware and control setup, I was expecting very similar handling characteristics. It is possible that some additional adjustments are needed on my end.

During takeoff, control authority was good in gusty winds up to 22 knots, and the aircraft remained stable throughout the initial climb in turbulent conditions.

At 1:25, I noticed some wing rocking. With only about a 2-knot wind variation, I would not normally expect that level of response.

While entering a speed restriction of 200/4000A for the DPK hold, I copied it to the scratchpad and then attempted to copy the hold information, but it would not accept it. This may be an FMS limitation. However, when I entered 200/4000A at the first DPK waypoint at 2:14, the CRZ ALT automatically changed to 4,000 feet. This is the first time I have observed this behavior. It may be aircraft-specific, as I never encountered it in the 737-400.

I also observed another instance of wing rocking between the user waypoint CRI01 and ZETAL, resulting in a less-than-smooth transition.

The capture and transition onto the localizer were very good.

On final approach, there were noticeable deviations above and below the glideslope, and on short final the aircraft was significantly above the GS. The autoland touchdown occurred well down the runway, close to the 2,800-foot marker.

This may also be specific to this aircraft model, but after touchdown it did not properly follow the ROLLOUT mode. The autopilot had to be disconnected, which resulted in a lateral deviation that could not be corrected effectively in the 20-knot crosswind. Interestingly, this issue was not present during takeoff, where directional control was very good.

Overall, some areas show improvement, while others may still require refinement.

25 minutes ago, Stearmandriver said:

Well, is it a matter of the VNAV speed not commanding 250kts (actually 240kts below 10k is the default), or is it a matter of the speed being commanded but the plane not doing it?

That's not unusual; the autothrottle mode is Arm during a VNAV descent so that the autothrottles are unclutched and the pilot can be a pilot. VNAV isn't magic; it expects you to add thrust when necessary, and also to add drag when necessary. So, if you're descending in VNAV path, and the speed has gotten fast approaching 10k and remains fast below 10k even though the speed bug is correctly commanding a decel, it's not the plane that isn't doing its job, it's you. 😉. The VNAV path will be built with a decel point to 250kt at 10k, and the plane will pitch up to follow the pre-built decel, but if you start that decel 20kts fast, you're probably going to finish it 20kts fast.

The plane will eventually transition to VNAV Spd and pitch up to chase the commanded speed below 10k, but it won't happen immediately and it won't happen at 251kts. It happens a certain amount of time after exceeding commanded speed by a certain value - could be 10, 15, or 20kts fast depending on operator option. I forget which the iFly has modeled.

But if you correctly use drag as necessary, just like in the actual plane, this won't be an issue.

Oh no, it’ll bug 240, but it won’t go into VNAV SPD* at 10 till it gets to the 10 knot threshold to continue descent. It’ll stay in PTH and keep on trucking down.

Edited 5 minutes ago5 min by V1ROTA7E