Yes, I tried to go 4x, and it had a hard time following the route. Unlike the Fenix A3xx line, you aren’t locked to 2x max. Would be nice to get 4x capability like the PMDG for those California to Hawaii Southwest routes, but not a deal breaker by any stretch.
Yeah, this is a good plane, have done four flights with it. I’ll echo the other complaints: taxi steering is a bit too “easy”, the EFB is non-intuitive (but simple enough once you get the hang of it). Other nit is that the Cockpit Quickview Left moves you to a passenger window (which had its shade often shut, but I found an EFB setting to prevent that), and QuickView Right shows you the cabin. Would strongly prefer that they simply show out the left and right of the cockpit. There’s a thread on that in their Discord.
Besides the above,this plane is excellent, and a very easy transition from the NG as several have said.
I’ll next be busy mapping my StreamDecks etc. to the various buttons, using my PMDG 737 Spad.Next profile as a template.
Thanks. Seeing so many mixed reactions about this plane, I think I’ll hold off on buying it at least until the initial bugs are ironed out.
I’m really curious to know what this WT 737 MAX that will come with MSFS 2024 is like. I don’t expect it to have advanced systems like the Ifly, but I hope they’re at least decent. A/P, VNAV and TOD working well, decent systems, acceptable textures and modelling. If it has all of that, I might even settle for it until PMDG launches its 737 MAX and then we’ll have direct comparisons of the two and see which one is better.
Well there is no such call-out from the plane’s side. It’s the pilot who is saying “rotate” in reality which is also simulated in the PMDG. The iFly just doesn’t include any pilot voices.
That is correct. In the real airplane you must wait until 20% N2 or maximum motoring (or was it 25%?, I don’t know, haven’t flown the 737 in a while). It’s all written in the FCOM. This is because the 737 does not have autostart, or at least the ones I flew didn’t.
In MSFS there are no engine start abnormals simulated so, just like in a full size simulator, you can set the engine start levers to idle as early as you wish. The engines will start and nothing bad will happen.
I guess I’ve never tried adding fuel early to see what happens in the NG. I know if you do this with any Black Square turboprop (King Air, Turbine Duke), you’ll have a virtual near-seven-figure USD repair bill per engine. This isn’t modeled in the PMDG, I guess?
I doubt it. The plane requires a separate plug-in app to be running on the simmer’s PC. It’s unlikely something like that can work on the locked-down environment of the XBox.
So, several flights in this weekend (my 8th ongoing now) and, more familiar with the quirks, I’m really liking it. Some observations:
Currently, performance for me is less than PMDG and Fenix by a bit. I’d put it at the same level as the V2 Ini A320. Flyable, absolutely, but not a wide FPS window for traffic injection, add ons, etc. Oddly, performance at cruise isn’t that much (a few FPS, if that) higher than on the ground.
VNAV and LNAV have been much, much more solid for me on repeat flights. The reason, I believe, is that the AP really, really doesn’t handle wind gusts well, and I’ve posted that as a bug for them. If there aren’t big gusts, it’s fine.
Finally have the knobs turning in both directions on clicking (rather than scroll-wheel only). It’s in their user guide and it’s a bit of a pain, copying a file, changing some settings.
And that’s it. Definitely enjoyable, definitely flyable, definitely fun. Terrific sounds, great model, and wonderful hand-flying. Just know the current issues and whether they’re acceptable for you.
I have noticed that VNAV has a hard time keeping speed at or below 250 Knots below 10,000 feet. Eventually it slows, but was just departing KMIA and was at 270 knots until it corrected.
Currently a bit over 4-1/2 hours into a flight between Keflavik and Nashville, a few hours left to go. I’ve been really enjoying this plane this week, despite the quirks.
No. In a real Boeing, it’s always possible to override the AT by manually moving the levers without tripping off the AT entirely. The issue is, in the sim, absent some really expensive hardware, your physical throttles do not move in response to the AT commends. But if your throttle controller is moved inadvertently or if it’s noisy and sends spurious signals, it will override what the AT is commanding. In the iFly, there is currently no way to lock-out your physical throttles from overriding the AT, which would prevent this problem. We believe there is a fix coming in a future patch but no word on timing.
Regarding the jittery Throttle when Autothrottle is enabled:
This not exclusicly a iFly 737 MAX issue, espacially if you use external scripting like Axis And Ohs or Spadnext.
Solution / Work Around:
After activating TOGA at the Runway → move your hardware throttle VERY fast to FULL POWER and leave it there until after touchdown.
After Touchdown → move your throttle VERY fast back to idle
This should avoid 99,9% of any jitter in the autothrottle and allow the autothrottle to stay in IDLE in descent or whenever it wants to be.
