Coming to land into RW03R at FAOR, aircraft started descending way below the glide. I let it happen all the way until the point it was no longer safe for the flight, but just to illustrate that the autopilot would have sent the plane into the ground without any intervention.

On my flight to FAOR, somehow the CAB ALT had an altitude lower than the LDG ALT.

Evidence: Check out any stream or video of the 777v2 on takeoff on YouTube.

Hope this can be fixed!

Thanks.

I have recently noticed that the brightness of the MCP digits is tied to the Glareshield dimmer knob on the overhead panel in the newest update. I was wondering if this was an error made by accident while updating other features, as pilots cannot manually control MCP digit brightness on the B777. It is to my knowledge that the brightness is automatically controlled based on ambient cockpit lighting conditions. It is sometimes the case that increasing the flood brightness on the panel can cause light to leak into the sensors causing the green LED to lighten up a little. Increasing master brightness can cause the MCP digit brightness to adjust slightly to remain legible, but the "turn knob --> digits brighten" logic that is currently implemented isn't accurate. The MCP digits always self-regulate on the 777 to reduce pilot workload, as is the case on the 737 and other Boeing aircraft. The brightness being controlled by the glareshield knob would make it impossible to turn off the panel lights while keeping the numbers visible, which obviously makes no sense.

Here is a CBT video I found on the B777. 4:25 clearly explains and shows that the glareshield knob controls the panel lights, not the MCP values.

If this is an error, please fix it. And if it is an intentional change, I would appreciate any response on why the change has been made.

-Thank you!

the yoke in the cockpit doesn't allow me to watch the ND, although it can be popped up.

There is no mention in the manuals about this feature if it is as such.

First of all I want to say I love flying your 777 v2, flight model feels great, the preflight interactions add to the realism, and we can absolutely flight from A to B following realistic procedures.

But we still miss some important 777 features, while the aircraft is not considered in beta anymore, for some time now. I'm just worried not hearing about development of these missing features.

Here is a list of what would be some welcome additions:

• No RTA

• No lateral offset

• No pred ETA/ALT in the FIX pages

• No ALTN page

• Missing two PROG pages

• The POST REPORT page doesn't display the ATA and waypoint fuel

• No FMC COMM (especially for WINDS Uplink, but this one we can still put them manually for every few waypoints there is a significant change, so it wouldn't be the top most priority)

Just hearing from you about these subjects would be reassuring.

Thanks for your dedication.

Best regards

I would like the cabin ready chime to be implemented in the 777? I know Air France has it and probably other airlines as well. It’s a chime that sounds during taxi to notify the pilots that the cabin is prepared for takeoff.
I think it would add to the immersion to have such a sound in the sim. Maybe you could even trigger it at a random time after pushback so that it’s not always a the same time each flight.
Just a suggestion 🙂

Log.txt

Just wanted to point out another small detail I've noticed : the heading reading at the top of the PFD is a little too big.

In real life, the font is a little smaller creating a margin between the number and the surrounding box. I've attached a comparison to make it clear.

Tanks for your attention to this matter !

Log.txt changelog.txt

I’m having repeatable issues when loading saved situations with the FlightFactor 777-200ER Extended in X-Plane 12.

Setup
X-Plane: 12.4.2-r2, build 124201, Vulkan
Aircraft: FlightFactor777_200ER_EE / 777-200ER_xp12.acf
SASL: v3.22.3+11eeb8d
Aircraft path: Aircraft/FlightFactor777_200ER_EE

What happened
After saving a situation during descent, X-Plane crashed later that evening. Since then, trying to reload that situation, or nearby older saved FF777 situations, either crashes X-Plane or triggers X-System assertions.

Affected saved states include:
LFPG-LPPT-Descente1 / LFPG-LPPT-DESCENTE1
LFPG-LPPT-ToD / LFPG-LPPT-TOD1

Observed errors
When loading LFPG-LPPT-Descente1, the log shows:

onSaveState [LFPG-LPPT-Descente1]
LOADING SITUATION - FULL SETUP (WITH X-PLANE .sit file)
Init modules with the state: LFPG-LPPT-Descente1
[SBParser] Failed to parse Takeoff Data. Reason: [json.exception.type_error.303] incompatible ReferenceType for get_ref, actual type is object
--=={This application has crashed!}==--

Another load attempt produced this X-Plane assertion:

Assertion failed
fltrange(wind_x_wrl,-200.0,200.0)
fm_wind_acf.cpp:718

A newer attempt loading LFPG-LPPT-TOD1 produced:

Init modules with the state: LFPG-LPPT-TOD1
"engines" loaded with a new engine - nice and fresh
[SBParser] Failed to parse Takeoff Data
Flight model error for aircraft: Aircraft/FlightFactor777_200ER_EE/777-200ER_xp12.acf
engine_sigma with speed
value is nan or inf
fm_engine_jet_Nspool.cpp, line 103

I also previously saw repeated B777 Lua errors:

[B777 ERROR]: __mul : [string "dynamics"]:593: attempt to perform arithmetic on a nil value
[B777 ERROR]: [string "dynamics"]:593 in function <getEngThrust>

It looks like the saved FF777 situation may be restoring invalid weather/wind and/or engine state values, causing X-Plane flight model assertions after the FF777 situation load. Any guidance on recovering the state or preventing this would be appreciated







.Log.txtSASLLog.txtLog-2026-06-03-2225.txt

Log-2026-06-03-2225.txt Log-2026-06-04-2145.txt Log-2026-06-04-2153.txt

I'm using Meta Quest 3 w/ link. others planes are normal, just FF777

I have noticed that during startup on the 777v2 (300ER and 200ER) the N1 needle does not position itself at the required stabilized N1 value but instead remains at 0. I have attached a picture of how it should look like when the engine autostart sequence is initiated. Notice the commanded N1 needle goes to around 20% N1 idle power as the actual N1 rises. Would be nice to correct it !

Thanks

Again, not reporting a bug, just asking a question if this is correct.

-Many thanks to the devs for creating an amazing aircraft!!!

2:48:34 - ENG SHUTDOWN comments

27:20 - ADIRU status message comment

38:35 - FMS Programming (watch for specific comments)

Hope this can help the aircraft grow!