Have just updated to 0.94.

Imported a flight plan via the correct method, added SIDs/STARs pressed EXEC and the information has gone into the FMC but the EXEC light stays illuminated. Have cross referenced with the CAPT FMC and cannot replicate the issue.

Also getting an issue in the FMC where it keeps changing the charectoristics of the next waypoint e.g speed/alt, this is not an issue i've had in the previous builds. I've attached the screenshots that were taken within 5 seconds of each other, can also see the EXEC light illuminted on FMC2.

https://ibb.co/mq5BjgP
https://ibb.co/4jFjxtt
https://ibb.co/8MsRBRV

Finally, are the engines supposed to automatically change for each phase of flight such as T/O - CLB - CRZ?

Weird altitude? Common in Asia/Russia where they fly in Meters as apposed to Feet, that should not be an issue. The issue was the ALT adjusting in the FMC nothing to do with the MCP ALT window.

Must be an issue then as i arm LNAV/VNAV prior to to departure and the change to does occur at the acceleration altitude.

Also, at the companies I work with on the 757/767, they’re told not to arm VNAV on the ground because it can cause issues. It doesn’t work like the 73 74 777 where that’s standard practice. Maybe do it the way they recommend and engage your vertical mode at your thrust reduction altitude? On the CS it definitely works fine if you do it like that. Only thing that still doesn’t work is the fact that the THR button doesn’t stay illuminated like it’s supposed to.

Alex T wrote on May 24^th, 2020 at 7:15pm:

In the first image, the speed/altitude is set to 250/FL321 for waypoint NTG, but all the waypoints after that are showing .801/FL321

In the second image, it's similar, but with the first speed/alitude (NTG) being 250/FL302, with the following waypoints showing .801/FL321

In the third image, the first speed/alitude (NTG) is 250/FL297, the next is 321/FL297 (PIKAS), and the following waypoints show different speeds at FL321