LineDX Posted Saturday at 05:34 PM Posted Saturday at 05:34 PM (edited) 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 Saturday at 05:36 PM by LineDX
Farlis Posted Saturday at 07:19 PM Posted Saturday at 07:19 PM (edited) 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 Saturday at 07:21 PM by Farlis 3
James42 Posted Saturday at 07:45 PM Posted Saturday at 07:45 PM 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. 1
hu hu Posted Sunday at 12:38 AM Posted Sunday at 12:38 AM 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.
Transair Posted Sunday at 05:13 AM Posted Sunday at 05:13 AM 11 hours ago, LineDX said: 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 yes...totally agree with this....happened to me on two successive flights today.
C. Schaffhausen Posted Sunday at 08:30 AM Posted Sunday at 08:30 AM Had the exact issue, come on Inibuilds, fly it at least once before an update. Hotfix needed. 13 hours 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. 1
LineDX Posted Sunday at 01:43 PM Author Posted Sunday at 01:43 PM I dont know how these type of basic point a-b flying bugs can be missed during testing before sending an update. Team ini you can do better than this. Thanks 1
C. Schaffhausen Posted Sunday at 01:43 PM Posted Sunday at 01:43 PM I've recorded a video showing the error, this also involves a premature rotation without any stick input during takeoff roll. 1
Transair Posted Monday at 01:56 AM Posted Monday at 01:56 AM (edited) 1. I've also noticed that on winding down the altimeter to set descent target level, the TOD indication vanishes from both the FMS and the ND 2. I also get a 'Speed limit' row in the FMS which commands a higher level (in this case 10,000) in the midst of a descent profile having lower levels, so the aircraft climbs during descent. 3. In the attached, the FMS shows very low levels inconsistent with the STAR, so had to set VNav manually. 4. Despite update 1.2.3., there still seem to be numerous problems with the V Nav. Hopefully this is getting extensive, urgent treatment!! Edited Monday at 02:03 AM by Transair 2
MartinS Posted Monday at 07:27 AM Posted Monday at 07:27 AM (edited) > About 25-50 miles or so before TOD on dialing the cdu alt to about 3000 feet, the TOD disappears from the ND Just tried version 1.2.3 with MSFS 2020 and BATC and I can confirm this behavior. Didn't happen before Edited Monday at 07:28 AM by MartinS 1
MartinS Posted Monday at 07:29 AM Posted Monday at 07:29 AM (edited) > upon climbout the aircraft deletes the cruise flightlevel and goes into descend mode I can confirm with v1.2.3, MSFS 2020 and BATC, climbing out of EDDK with a FPL to EDDH. Plane goes into DESC, speed limits and altitudes not honored. Goes into CRZ later (setting the CRZ flight level again in the init page might have helped), but BARO REF stays in local, does not start blinking to indicate STD should be set. Remains like this throughout the flight. Edited Monday at 07:30 AM by MartinS 1
IniJamir Posted 15 hours ago Posted 15 hours ago Hi, v1.2.4 is out which rectifies these issues, thank you for your patience 🙂 1
Recommended Posts