The aircraft should not accelerate above 250kts below 10000' in VNAV if you have that speed restriction entered on the Climb page. (SPD Trans/SPD Restr).   
The FMC Legs page should not show a speed higher than 250/10000'.
The speeds on the legs page are wrong below 10000'.
One waypoint has a speed restriction on the arrival of 210/5000. The next waypoint is showing 307 kts etc.

Secondly when going direct to a waypoint with a speed restriction on the FMC Legs page,  the Captain Sim 757/767 immediately decelerates/accelerate to that speed irrespective of the distance to that waypoint. Also not correct.

I also notice when selecting an STAR on the arrival page on the FMC the first waypoint seems to missing from the STAR.
Tried a few airports and several different STARS, first waypoint was always missing on my system. Newest Airac installed from Navigraph.

LNAV is also a bit inaccurate. Has a tendency to turn early and undershoot the turn on an SID etc. Resulting in left and right turn oscillations.

I see the 757 got the same speed issues etc. Been reported numerous times. Bit surprised this had not been addressed. 

Offset capability?
FMC ALTN page?
FMC COMM page?
RNP Entry?
EICARS, for weather/atis uplinks etc?

Would be nice if Captain sim also incorporated an IPAD/TABLET on the window bracket for performance calculations and charts etc.
Most serious developers seems to be adding this feature nowdays .

Chris

They clearly know what is not correct with this airplane. Lots of reports relating to the Vnav speed management etc.
I see the same issues on the 757 and that aircraft have been on the market for a while without any attempts to fix this basic Boeing FMS management.
I like realism and the simulation should get the basics correct as a minimum. 
It has potential, but it is far behind when it comes to correct speed management and accurate and precise flight path management.

Alex T wrote on Apr 29^th, 2020 at 4:05am:


Alright, I had a chance to load this up and try it out.  Granted both of these pictures were taken while on the ground, both times the FMC defaulted to a speed of 250 for the cruise.  I didn't get a chance to see what would actually happen in cruise flight, so unfortunately this was as good as I could get.

I loaded the same scenario in the FMC on the ground and I get a speed above 250 as well.  A quick edit of the ECON speed on VNAV CRZ fixes it to the way it should be.  The real FMC will perform this edit on it's own. 

I know that it goes back to my original post for a work around, but as far as I can tell this is indeed a bug.  Hope this info helps!

RW FMC 8000' cruise: https://imgur.com/a/1joQKRk
RW FMC 5000' cruise: https://imgur.com/a/MCAPD8Y
P3D FMC 5000' cruise no edit: https://imgur.com/a/bofbopL
P3D FMC 5000' cruise speed edit:https://imgur.com/a/hTHb4px

The speed restriction of 250/10000ft is only set during climb, it is on VNAV CLB page. When the plane reaches the desired cruice altitude, preselected on PERF or VNAV CRZ page, it changes his performance to the one entered on that page. It is part of the preflight to analyze and set the speed that you want to be set on cruise.

Michel wrote on May 1^st, 2020 at 8:25pm:


Or is this from real qorld experience? I know the 737 doesn't do that and the FMSs are somewhat similar.