VNAV serious Bug V1. 2.3

[LineDX]

Hi team @iniBuilds I did a couple of test flights on the V1. 2.3. In the new update VNAV has some serious issue. About 25-50 miles or so before TOD on dialing the cdu alt to about 3000 feet, the TOD disappears from the ND as well as from the OFP on the FMS without pressing the ALT knob button(activating the Des). This is a serious VNAV issue requiring an immediate hotfix to make the plans fly able. 

 

Regards 

Edited 11 hours ago by LineDX

[Farlis]

Another thing I noticed now twice is that upon climbout the aircraft deletes the cruise flightlevel and goes into descend mode. As a result you end up in open climb and have a green dot with the number 99 at the top of the altitude band indicating the flightpath vector.

This was on the TULNA8C SID out of VOBL. Later in the climb it returned to normal. Very odd.

Edited 9 hours ago by Farlis

[James42]

23 minutes ago, Farlis said:

Another thing I noticed now twice is that upon climbout the aircraft deletes the cruise flightlevel and goes into descend mode. As a result you end up in open climb and have a green dot with the number 99 at the top of the altitude band indicating the flightpath vector.

This was on the TULNA8C SID out of VOBL. Later in the climb it returned to normal. Very odd.

This is exactly what just happened to me climbing out of WSSS on the TOMAN3A. The aircraft went into descent mode after setting climb thrust. Even had Cabin Ready pop up. 

[hu hu]

The VNAV and speed calculation are crazy.
I am trying to land at CYVR 26L RNP AR (Tried other runways and other airports at different continental)

As the picture shows, the auto-calculated path is 5000 feet higher than restriction and 5000 feet higher than the runway height. I checked all the pathway point limitations, and the information is all correct. Only the calculated height is far higher than the CSTR.
And also for the incorrect speed, e.g., CSTR is 250 or below, but the calculated and actual flying speed is 350. 
Tried to clear SWAP, but there is no difference. 
This kind of problem appeared after 1.0.7 and has never been fixed.