Of course, to disprove my point, I got a 1 degree flaps recommendation, the day after I wrote this…
1 Like
One issue I’m finding - and I’m sure it’s happens with the real aircraft - the engines are so quiet, I find it harder to control speed on approach since I can’t hear the pitch changes!
Do many (or any) operators hand fly with A/T engaged? I know it’s rare with NG operators (I believe AAL does). Curious if the MAX has brought new SOPs…
1 Like
No changes on anyone’s Standards from NG to Max regarding manual flight w/autothrottles engaged as far as I know. No one really uses sound as an indication of engine power; in even light to moderate rain, you can’t hear anything else anyway. Even in calm conditions, you can’t hear small to medium thrust changes. Remember, the sim sound set was recorded open mic, and everyone flying these airplanes is wearing noise cancelling headsets.
So even in the real plane, thrust references are purely visual (unless you’re talking about the tactile feel of a significant change in energy state but that shouldn’t be happening on approach). Primarily, they’re the N1 gauges, but the HUD can help here - the energy state carat is MUCH more accurately modeled than on previous 737s in the sim… It’s nice and sensitive and very usable for precise speed control. I think this thing, more than any other aspect, is what makes you a HUD cripple in reality 
.
4 Likes
Every time I’m baffled by the block fuel amount when planning long flights. The difference with the NG on long routes (like Denver/Fairbanks) is more than 18%… definitely something i have to get used to 
Yes… Actual fuel capacity is meaningfully LESS than the NG, while range is significantly MORE. Kinda cool ;).
2 Likes
Has anyone had any issues with the flap and speed brake lever on the Honeycomb Bravo? When I arm the speed brake the handle moves back and forth with no input. When I raise my flaps even with my Bravo lever all the way up the flaps stay in 1 until I jiggle the lever. When lowering the flaps when I get to 30 position my flaps raise up all the way. This only happens with the Max out of all the Boeings I fly. Any feedback is appreciated.
Is the HUD standard on the MAX or is an option like on the NG?
If you search the discord, you’ll find a number of solutions for the flaps. If you are using MSFS binds, it sounds like setting a curve can help. If you are using AAO, you can find the solution here: AXIS_FLAP_SET bind isn’t working properly with iFly 737 MAX8 - AxisAndOhs Support - The AVSIM Community.
I haven’t had any issues with the speed brake handle, but it sounds like you may just need to set a deadspot.
As far as i know not. The United and Ryanair MAX’es dont have them.
Yup, still an option.
Hello
I can’t get the sound of the RAAS, yet it is well selected in the menu and validated at the bottom of the efb!
Do you have the same problem?
Thank you.
Have you run the airport maps utility yet? If not, you won’t get RAAS warnings. Launch the iFly plug-in without the simulator running and you should see the option to generate maps.
I was busy the last few days but finally got to look into the Discord. Thanks for pointing me in the right direction.
1 Like
Thank you, it worked!
Big thanks for your help!
1 Like
I’m following this sim from afar, thinking about purchasing it but I know when it was released, it did have a few significant bugs. Thought I read somewhere that iFly was going to be releasing an update that would address many of the issues. Did this come out or it not, has there been any news on it’s ETA?
No, it’s not out yet and no ETA but I would guess it will be very soon. Looking forward to the update but plane flies great as it is…
1 Like
Nope, no patches since release. The iFly team posted a change list for the next planned version (0.26) on the Discord but that was probably 2 weeks ago and still no patch. It’s unclear what the delay may be related to, or why they may be holding it back.
The most significant bug I have personally encountered isn’t so much a “bug” as a user-interface / quality of life thing: the fact that there is no setting to ignore physical control inputs while on AP and Autothrottle. So people with noisy controllers or who inadvertently move their controls will override the automation.The solution for now it to set control extremity deadzones, and for throttles, push them to full power on TOGA and climb, then reduce them to full idle when you start your descent.
It’s a good plane and I have enjoyed flying it but I do admit to being a bit frustrated at the pace since release. The impression I had at the time was that there would be regular periodic updates, as there apparently were in the weeks leading up to early access release. But so far still nothing.
As a fix for that issue, could you not just unplug your controllers while on AP? Not close to optimum but seems easier than the above?
I can’t speak for anyone else, but my controllers are all plugged into powered USB3 hubs tucked away under/behind my monitor and out of sight. I’m certainly not going to go unplugging controllers mid-flight and then reconnecting them at 1,000’ AGL when I take over to land manually. Far easier for people to just make a custom controller profile with deadzones for the plane, which resolves the problems for nearly everyone who has encountered it.
As for me personally, I don’t have any noise in my controllers so I just firewall the throttles when I hit TOGA, then pull them back to idle once VNAV starts descent. I move them to about 35% or so right as I turn off AT.
You are no fun 
. “Ladies and gentlemen, we will touchdown as soon as the captain plugs in his yoke and throttle. Until then, please pray he orients the connector on the first try”
4 Likes