Joel S

That's the issue and solution...Cost Index missing!

I just tried this RNP 27 approach. It does NOT work for me (I can not arm P. DESC. in blue when pressing PROFILE). Just to confirm, I'm using the latest v1.1.0. v1.0.9 was working fine

I know how to perform the RNAV approach from INIBUILDS YT vids. I reconfirmed that it works with the A310. Can you please provide your RNAV approach so I can attempt to duplicate your results? Thanks!

Greetings: I just tried fly RNAV Z 31L at KJFK. I'm unable to arm the P. DESC. I'm using v1.1.0. This issue was fixed in v1.0.9. Thank you

I did more testing and I believe the DIRECT TO issue I'm having is related to FSIPANEL 2020. I'll contact the owner,JP, and inquire. So the only issue (if you want to call it that) is to have "3.00" appear on the FAF of RNAV approaches.

I've tried so far with some waypoints leading to RNAV approaches for KJFK. I just hit DIR, select the waypoint, select *INSERT and I get what you see in the screenshot above. That example is the RNAV Z 31L approach. I use FSIPANEL 2020 to quickly place the A300 into position at RISSY. I then set a Direct To I never had an issue setting a Direct To ZACHS and you can see how the flightpath is drawn. The plane is facing ZACHS and should be a straight line. Instead there's a curve arc followed by a straight line.

Looks like v1.0.9 fixed the RNAV issue. I can arm P.DES. in blue by clicking PROFILE. However, the MDCU still does not show the 3.00 in the flightplan. The DIRECT TO function is still buggy. It still creates an arc path to the waypoint even when the plane is pointed directly at it (see screenshot).

While everything you say is true, those are not the reasons for this issue. I'm at platform altitude in ALT HOLD mode. I'm in NAV mode. I entered a MDA. I pressed FINAL 3.0. I saw the VDEV value indicating how much above or below profile the plane is. At that point I should be able to press PROFILE and P.DES. should arm in blue. It does not and I believe it's because the FMC doesn't have a -3.00 degree FPA programmed. I've now tried a dozen RNAV approaches at a few different airports and NONE of them have it programmed into the FMC. However, using the A310, ALL of these same RNAV approaches have 3.00 programmed into the FMC. I wish I kept a copy of v1.0.6 to rollback and confirm that it used to work.

Here is a screenshot from INIBUILDS YT video - EFB & Approaches - A310 | Part 2. I circled the "3.00" on both waypoints after the FAF. If this is missing from the flightplan, then I believe that's why the A300 will not arm P. DES. in blue.

Did you verify that the FAF had a "3.00" above it in the flight plan (same as my pic above)?

RNAV was fixed in an earlier version. I wanted to test it with the new 1.08. RNAV works the same way in both A310 and A300 and INIBUILDS has a YT tutorial on it.

I'm testing RNAV functionality using RNAV Z 31L for KJFK (inibuilds). I set a direct to ZACHS instead of creating a direct path, it added a curved path (attached image). Secondly, the "3.0" descent angle at the FAF is missing from the flight plan. I believe that is the cause of P. DES. not arming. I duplicated the exact same approach on the A310 and the 3.0 appears and P. DES. arms as expected (see 2 attached images).

Same extact thing happened to me. Look at the Flight Director when you lost control. Notice how the lateral line moved all way to the right and the Autopilot followed it. I'm also getting various controls stop responding visually during flight.

I used ILS-Z 22R at KDTW and according to the Jeppesen chart I have, it's 111.95 and 216 degrees.

I just tested with 1.0.3 update. Same result...the Localizer slides off to the right just prior to landing when attempting an Autoland (pulling the plane to the right. Have to disconnect AP quickly to correct and land on runway).