53 minutes ago, RobJC said:

Just to clarify, this is what I am seeing when it does not work. Note that the TOD (in Active VNV Profile section - right side lower) is 1+58. Usually it would be mins:secs to TOD. When I see this generally it means VNV is not going to work correctly. 

Yeah, something is wrong there, I don't see it like that. Mine shows mins:secs and it always works.

Edited August 17, 20214 yr by Alvega

1 hour ago, RobJC said:

Just to clarify, this is what I am seeing when it does not work. Note that the TOD (in Active VNV Profile section - right side lower) is 1+58. Usually it would be mins:secs to TOD. When I see this generally it means VNV is not going to work correctly.

I get those kind of readouts when I am sitting still, on the ground..

Here is your flight plan minus the Airway.. looking OK..

Edited August 18, 20214 yr by Bert Pieke

Made around 10 flights with RNAV approaches and all of them worked as they should. Good job, WT team.

Sure this is going to be an irritatingly basic question but when an approach is activated the flight plan shows the correct altitude for each waypoint and it's also shown in magenta next to the autopilot altitude on the PFD, but I can't get the autopilot to automatically follow the FPL altitude.

Shouldn't activating VNV get it to follow the right altitudes for each waypoint?

10 minutes ago, scotchegg said:

Sure this is going to be an irritatingly basic question but when an approach is activated the flight plan shows the correct altitude for each waypoint and it's also shown in magenta next to the autopilot altitude on the PFD, but I can't get the autopilot to automatically follow the FPL altitude.

Shouldn't activating VNV get it to follow the right altitudes for each waypoint?

I got it to work 3-4 flights but some flights just don’t work.

16 minutes ago, RobJC said:

I got it to work 3-4 flights but some flights just don’t work.

That’s interesting as I’m sure I remember it working properly on one flight but then I wondered if it was just an rnav approach.

1 hour ago, scotchegg said:

Sure this is going to be an irritatingly basic question but when an approach is activated the flight plan shows the correct altitude for each waypoint and it's also shown in magenta next to the autopilot altitude on the PFD, but I can't get the autopilot to automatically follow the FPL altitude.

Shouldn't activating VNV get it to follow the right altitudes for each waypoint?

Did you reduce your selected altitude? If you are flying at 10.000ft and leave the selected altitude at 10.000ft even if you activate VNAV nothing happens. I usually set the altitude to the FAF when I engage VNAV and it always follows the descent profile.

Edited August 18, 20214 yr by Alvega

1 hour ago, Alvega said:

Did you reduce your selected altitude? If you are flying at 10.000ft and leave the selected altitude at 10.000ft even if you activate VNAV nothing happens. I usually set the altitude to the FAF when I engage VNAV and it always follows the descent profile.

That’ll be it, thanks. Will test later.

This is making the sim so much more enjoyable. HILPT entries on a few approaches bugged out. I'll have to grab a screen shot and put if over in the WT discord. And anyone getting missed approaches to work? Maybe not implemented yet? I noticed the OBS button is inop. on the 172 anyway.

Correct, missed approaches are not yet implemented. 

10 hours ago, RobJC said:

Just to clarify, this is what I am seeing when it does not work. Note that the TOD (in Active VNV Profile section - right side lower) is 1+58. Usually it would be mins:secs to TOD. When I see this generally it means VNV is not going to work correctly. 

This format means 1hour and 58minutes. Looking at the Flight Plan I can see on your screenshot it all looks a bit weird. It goes Dubin - Strum - Dubin - Strum etc. and your Airways are also shot up. It either bugged out for you or there have been mistakes made when setting up the flight plan.

2 hours ago, dga711 said:

This format means 1hour and 58minutes. Looking at the Flight Plan I can see on your screenshot it all looks a bit weird. It goes Dubin - Strum - Dubin - Strum etc. and your Airways are also shot up. It either bugged out for you or there have been mistakes made when setting up the flight plan.

Thanks Dominik. I guess something got messed up setting up the flight.

Going to delete this mod for now. Planned a flight from KDEN to KCOS, IFR. The map and G1000 did not even agree, as one wanted me to turn north and one south. Ultimately the plane went straight. The VFR map was correct. Bummer.

 

 

Edited August 18, 20214 yr by RobJC

4 minutes ago, RobJC said:

Going to delete this mod for now. Planned a flight from KDEN to KCOS, IFR. The map and G1000 did not even agree, as one wanted me to turn north and one south. Ultimately the plane went straight. The VFR map was correct. Bummer.

 

 

I think it was mentioned somewhere - the VFR Map does not  sync with MFD. [for now].

I don't use VFR map - don't think I ever used it.

The current state of the NXi is just too good - I would not let a map stop me from using it. 

Just now, SAPilot said:

I think it was mentioned somewhere - the VFR Map does not  sync with MFD. [for now].

I don't use VFR map - don't think I ever used it.

The current state of the NXi is just too good - I would not let a map stop me from using it. 

It actually wasn't the map, but that was just another quirk. The NXi map showed going the wrong way (north instead of south) and the AP would not make the turn (either way). It just kept pushing straight and the lines and curve/turn kept moving forward as i flew. This after the other flight would not engage VNAV.