I’ve been flying the 777 since the PC release and never had the EFB and FMC difference be greater than 1 knot, and most of the time they are completely the same.
As others said, check to be absolutely sure the aircraft weights are the same in the EFB and the FMC, that you have the same flaps set for both calculations, that the weather is the same, and that you have the correct runway set in both.
If you enter runway wind, runway slope and ground temperature (OAT) into FMC you will get similar or the same takeoff speeds. EFB takes this data from Metar when you import it, in FMC you need to enter these values manually.
Thanks - I saw the yt vid by 330driver and he put the temp suggested by EFB which in turn led to appropriate TO and CLB derates being selected automatically. This is the step I was doing incorrectly.
And the sequence is non-trivial which I learned the hard way, and Ffortuna posted above. When I was entering the temp first, top down as displayed on the CDU, then the derate, I got weird results. When I started selecting the derate first, then entering the temp, it all came together correctly. Was not a big difference really, but it’s nice to see it all hang together correctly!
Thanks all, the pointers really helped and now I am very well placed with V speeds on CDU and EFB being very close and matching in some cases.
I did my first intercontinental flight from EGLL to VIDP and with 4X feature being a great boon completed it in a lot shorter than predicted 8+ hours. When I finally landed, instead of the airport bustling with traffic, was empty as it seems I hit the sim object limit while flying across continents - which is a pity and something that must be addressed in 2024.
Did anyone see this strange value for trim before? I couldn’t import weather data, EFB was giving me errors about weather not available. I entered it manually based on ATIS. Wind was calm so I entered 000/00. I tried also 000/0 but the result was the same.
IIRC, there were erroneous readings about wheel status and the latest update was the to fix them. Maybe it “fixed” them by taking the simulation of brake temp away. I thought the real fix would follow soon (“soon” perhaps?).
Didn’t notice it works at the beginning of flight. I’ll try braking hard while taxing.
When under radar vectors, it’s common to remove waypoints on the STAR or earlier part of the approach, making the FAF waypoint the active waypoint. This function completes this with one press, and extends the inbound course to the FAF so it can be intercepted in LNAV if required.
Wow looking at the various yt videos on msfs 2024…
I learnt something new today… Wire detail or something like that
There is like 4000 times more wiredetail in this sim which somehow means more texture in the ground…
When you put that into “my brain” terms…that must means I’m going to be changing those rear tyers alot more often…
Especially when I’m going 15knts around those corners and dragging those boggies over the dirt
In terms of wear and tear, I’m fairly certain PMDG’s 777 tire wear is all custom code, and won’t be affected by the new increased level of surface detail available in FS2024. The primary drivers of tire wear in my experience have been landing rate and then braking intensity.