EICK Cork Issue

Navigation Data General MSFS Data
1

Hi,

There is an issue with EICK Cork in the latest AIRAC version. It’s not possible to select an approach. See the video link below for more details.

https://youtu.be/tTQh0UbsIl8

2

Hi,
It seems any issue is with your system or with the PMS, because when I try this with the default stock G1000, I see all approaches as expected:

MSFS2020, no 3rd party scenery, AIRAC 2511 rev. 3, stock G1000:

image
image1738×1131 293 KB

Cheers
Richard

3

It’s not the fault of the PMS or the system. I even reinstalled the AIRAC. There’s clearly some problem with the RNAV procedures. Check the link below. Oh, and the simulator is MSFS 2024.

https://youtu.be/WRGgUiPIuNc

4

Ok, but why does it work on my system than and why do you mean it is an AIRAC issue?

MSFS 2024, no 3rd party scenery, AIRAC 2511 rev. 3, stock G1000:

image
image1857×1223 387 KB

  • So, you can confirm, that you don´t see any approaches in the stock G1000 (not with any 3rd party aircrafts)? Correct?
  • Have you installed any 3rd party scenery? When yes which one? Have you reset the content-file?
  • I assume you are using not the beta? Correct?

Cheers,
Richard

5
  1. no. Did you see my latest video? Check from 1:06. You can see that the problem is only with the RNAV procedures whether I’m using PMS50 or not.
  2. Yes.MKstudio EICK.
  3. I’m not using beta

Thanks

6

Can´t reproduce it … but I don´t use the 3rd party scenery.

image
image1920×1239 333 KB

For testing, try removing the third-party scenery and see if it works with the stock G1000.

Cheers,
Richard

7

You’re right — after uninstalling EICK from MKstudio, everything went back to normal.

Thanks for your time!

8

Just as info about the reason:
With SU3, the package loading order was significantly changed, and many third-party sceneries are not 100% SU3 compatible, which can result in such issues. ASOBO/MS has done a fantastic job of rewriting the logic for package loading orders. This great feature works only when the third-party scenery includes the necessary features.

A second (but less common) reason is that the scenery deletes the terminal procedures, resulting in no procedures being visible (everywhere).

In your case, I assume it´s the 3rd party scenery that is not fully SU3 compatible.

Thanks for your feedback,
Richard