Any suggestions for getting around a totally locked cockpit (no movable switches, buttons)-I’ve followed the complete install/reinstall method detailed on Discord-I’ve deleted the WASM directory in MSFS2020-Also I have auto-started the plugin, stopped it via the TM, and restarted it manually-still no joy-any help would be appreciated-thanks

rw

P.S. Only the default livery is used

51 minutes ago, Stearmandriver said:

Not really. NGs won't do this any more than Maxs will; the plane will pitch up to slow at a set schedule in VNAV speed but it won't actually level off. Maybe you mean the PMDG will do this; I don't remember. But actual NGs aren't any more aggressive than a Max in the decel. If the scratchpad is informing you that drag is required, that's not an invitation to put on a dress. 😉

The iFly box definitely builds decel points for speed restrictions on the legs page. Again, depending on the accuracy of your descent winds, it may need help from you. As long as you see the speed bug properly command a decel, the box is working correctly. I'll try a star with some intermediate restrictions tonight, but I haven't seen any of this work incorrectly since SP1 started testing.

Been a while since flying an NG, but, if i remember correctly, it will level off till 250 at 10 (specifically), then continue the descent, ignoring the path, potentially getting you high on path..that's the reason you'd want to slow down, as to no sacrifice the profile. One of the features of VNAV. Yes you'll need to help it out, but normally, it does prioritize the path and will not look at the speed because 'you can help it out' even though the 73's speedbrakes are effectively useless lol. The ol' drag required message simply means you've deviated 10 or more knots from the plane's desired speed and goes away once you get there, clear the message, or get below that speed. I know you know all this already. I think the confusion from my earlier statement was not saying that the level off only happens at 10,000...normal deceleration points will not level the plane, and it'll continue on path. What i did say before, which is true in the iFly is that at the deceleration points, the path angle doesn't change to help with that speed reduction like it does in the plane. If you're descending at, say 2200fpm on a normal path at 280, once there's a speed restriction on an arrival, say 250, the iFly won't slow the descent rate at the first doughnut, it'll stay at 2200fpm.

Can't say I've noticed this, but I will try it out specifically tonight.

2 hours ago, LRBS said:

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.

Was this in 2024? I suspect some of what you're describing is a function of the custom flight model not playing nicely with the different gust and turbulence physics in 2024 vs 2020. I've seen nothing but consistently perfect autoland performance, but I'm always testing it with my catIII weather preset which has near calm winds, as catIII conditions usually do.

I've also never tried a fail operational autoland since we use fail passive (no benefit to maintaining fail operational with the rollout guidance in the HGS), so I wouldn't know what I was evaluating anyway... But worth noting that the autoland crosswind limitation is 15kts.

36 minutes ago, Stearmandriver said:

Can't say I've noticed this, but I will try it out specifically tonight.

here ya go. PMDG models this correctly. Route KSJC-KSFO Boomerang departure, doesn't matter the runway, Surfer arrival D-> WAAVS when at FL250, ILS28L with the EDDYY transition...ended the flight before then, but loaded it for consistency. The PMDG was heavier so a shallower path, couldn't change the weight of the iFly in flight, so it was much lighter. PMDG weight was 142.0 freedom units. iFly was around 116.0. No winds loaded. Descent speed .70/290 in both.

Didn't get pics of the descent before 10k, but it did slow the descent rate from ~1800fpm to around 900FPM at the first round of doughnuts for a 280 speed restriction.
Levels off at 10 to get to 240.

Once within 10 knots, it starts down.

transitions to SPD when off the path.

Doughnuts came and went, but here's just after passing the first deceleration point.

Thru 10

Thru 10

No attempt to slow down.

2 hours ago, Stearmandriver said:

Was this in 2024? I suspect some of what you're describing is a function of the custom flight model not playing nicely with the different gust and turbulence physics in 2024 vs 2020. I've seen nothing but consistently perfect autoland performance, but I'm always testing it with my catIII weather preset which has near calm winds, as catIII conditions usually do.

I've also never tried a fail operational autoland since we use fail passive (no benefit to maintaining fail operational with the rollout guidance in the HGS), so I wouldn't know what I was evaluating anyway... But worth noting that the autoland crosswind limitation is 15kts.

It's 2024. 

I thought it was 20 KTS; however, the issue I had was that after disconnecting, landing, the rudder was less effective than it was during t.o. roll.  Anyhow, there is lots of positive work and effort on this release. Someone mentioned that the competition 737 flies much better. All I can say is, oh boy. 

12 hours ago, Stearmandriver said:

You seem to be saying it's related to the autopilot though? Firstly, that's not flight model; that would be an autoflight issue.

I think he meant autoflight, and I partly agree.

I only have logged two medium distance flights so far, but I instantly noted the twitchy LNAV turn behavior. It has made precise and continous turns (much better than PMDG, imho), but the start and end of the roll were very snappy/abrupt. It feels like it could use some kind of filtering and it will be good.

Overall, I had two very nice flights. This is the Boeing I was waiting for to complement my Fenix A320 flying.

Edited 15 hours ago15 hr by NovemberUniform

5 hours ago, V1ROTA7E said:

here ya go.

Well now this IS interesting. Thank you for the screenshots. I've created a bug and forwarded your screenshots in the report. I'll test the route myself tomorrow and get video for the team too. To verify, 2024, right?

I know I've seen correct behavior (shallowing the descent before 10k, reversion to VNAV spd when appropriate), so I'm not sure if there was an uncaught regression somewhere in the test builds or if this is something that only affects certain arrivals etc, but it definitely looks like you had a bug on that flight.

I made a flight in the iFly tonight to look at this and coincidentally (I did not see your post beforehand) I went to SFO and flew the SERFR. I did note that I needed speed brake on the descent, and it feels like I have been using the brake a lot on the plane lately, so I can't say what the plane would have done if I hadn't helped it. I'm wondering if it's possible that we're all so used to pulling the speed brake when necessary that this behavior snuck in without being noticed.

I DID test it in an early SP1 build though, as we were specifically asked to, so I can see how no one might have been looking for it subsequently. But yeah, I'm going to beat it to death tomorrow night, I'll get them all the video they need.

As far as banking behavior, I watched that closely at every enroute and terminal waypoint, and I still don't see a problem? Wondering if it depends on having a strong crosswind or something? The real plane will roll somewhat aggressively when necessary to stay on course; you see this most often during localizer intercept. But yeah, everything looked fine on my flight. I suspect whatever is being seen could be related to 2024's gust and turbulence modeling being different than 2020s. My flight tonight was pretty smooth.

Edited 14 hours ago14 hr by Stearmandriver

a couple of interesting observations about CpFlight MCP737EL driver and wintrl PFP3N .

I have troubleshoot 2 hours and found that seats 178 works with wintrl Simapp Pro software.

CpFlight MCP737EL rev 1.07 works BUT pay attention to the USB COM port that Windows is given you. Dont go above port 11 (at least)

Michael Moe

Question on the FMC Takeoff page. At that bottom, I see an option for "QRM" off / on. I don't recall seeing that before (could be wrong), what's that option about?

Edited 11 hours ago11 hr by 11bee

6 minutes ago, 11bee said:

Question on the FMC Takeoff page. At that bottom, I see an option for "QRH" off / on. I don't recall seeing that before (could be wrong), what's that option about?

Those are speeds that assume a balanced field, derived from the QRH/Performance Dispatch. Very basically, theyre conservative takeoff speeds.

I'm a graduate of the Trial & Error Flight School....and wonder if anyone here knows why when I took off on 36C at EHAM on a SID dictated by BATC, and decided to engage the autopilot at about 2000' AGL, with VNAV and LNAV enabled, the plane shot up severely, well over 20 degrees at which point I turned off the autopilot to regain control. I used to be able to do that and get away with it, right or wrong pre SP1 update.

Edited 10 hours ago10 hr by Noel

9 hours ago, LRBS said:

It's 2024. 

I thought it was 20 KTS; however, the issue I had was that after disconnecting, landing, the rudder was less effective than it was during t.o. roll.  Anyhow, there is lots of positive work and effort on this release. Someone mentioned that the competition 737 flies much better. All I can say is, oh boy. 

To be fair, the PMDG 737 flight dynamics have improved a lot in 2024. I hated the way it felt in 2020. iFly flew exceptionally well in 2020, but we will probably have to wait for the native 2024 version to get the best out of it.

1 hour ago, Noel said:

I'm a graduate of the Trial & Error Flight School....and wonder if anyone here knows why when I took off on 36C at EHAM on a SID dictated by BATC, and decided to engage the autopilot at about 2000' AGL, with VNAV and LNAV enabled, the plane shot up severely, well over 20 degrees at which point I turned off the autopilot to regain control. I used to be able to do that and get away with it, right or wrong pre SP1 update.

I think I saw another simmer in the iFly Discord channel mention he had this problem too. I couldn't find it for reference, but I'm sure it was in the chit-chat channel as I didn't see it in the "MRO" (bug reporting) section.
If you experience it again, can you gather as much info as you can and report it over there? That is the only way we can get a possible fix.

1 hour ago, RNAVV19R said:

To be fair, the PMDG 737 flight dynamics have improved a lot in 2024. I hated the way it felt in 2020. iFly flew exceptionally well in 2020, but we will probably have to wait for the native 2024 version to get the best out of it.

Yes...not that I can talk professionally on its flight dynamics (but we have someone here who can 😉), I know any ported models will suffer limitations when it comes to detailed CFD integration.

We can't wait to get our hands on the 2024 native model, and as soon as we do and can talk publically about it, you can bet we will. :)