I currently have latest version of the Phenom 300 with Navigraph extension and shooting ILS approach is still problematic.

The autopilot nicely captures the localizer but then the aircraft start descending before capturing the glideslope. Approaching

the final fix, I use to position the aircraft approx. 30° off the final course and slightly below the glideslope altitude.

I am wondering if I have a corrupted installation or if this is still a bug which needs to be fixed by carenado.

Help would be appreciated

Thanks

Jean Pierre

 

Hi Jean-Pierre,

 

I got a similar problem and was able to cure it. So maybe this will help you.

 

Aircraft with non integrated GPS have a switch NAV-GPS which allows to send to the CDI either the signal from the GPS or from the VOR1.

 

On the true G1000 this is normally done by clicking the button called CDI under the PFD. The CDI will then switch to NAV1, then NAV2, then GPS. However it seems that Carenado could not do this probably because they adopted the original FSX autopilot.

 

As you can see when you start the aircraft, on the line of buttons below the PFD, there is one marked "OBS" between "CDI" and "PFD".

 

When you type a flight plan on the MFD and push NAV on the autopilot, this button under the PFD will change from OBS to GPS, meaning that the GPS is steeriing the aircraft.

 

The problem is that you cannot switch back to NAV. Even when the CDI is switched to NAV1, the GPS continues to interfere !

 

I solved the problem by assigning the original FSX NAV-GPS function to one of the buttons on my yoke (you may also assign it to one key of your keyboard) and pressing it to to disengage the GPS and ... it worked.

 

The Phenom 300 is a very nice simulation and I like it. Sad that Carenado is lagging in the conception of aircraft systems.

One would have liket this plane to be developed by Realair or PMDG.

 

Good luck with your Phenom !

 

 

 

 

 

 

Thanks for your help. I have installed the latest version of the Navigraph extension and seems to me that this has cured the problem. I will test it again

today and if the problem still exist I will assign the original FSX NAV-GPS function as suggested.

jean-pierre