chkl

Cruise levels in meters go west bound FL301, FL321, FL341,FL361,FL381,FL401,FL430. To start you may have FL256 or FL276 until atc will clear you higher due to crossing traffic. Regularly see traffic stuck at FL276 for an hour northwest out of HKG. Set RVSM in the FMC VNAV cruise page to the number 0.

The speed is not saved any flight. I have to be doing something wrong?

Cleared the suggested speed changes and entered manually but the changes do not save. 747 profiles at the download library. first oceanic entry set .84 and altitude. It sets altitude and ignores speed.

Affirmative I have that setting and it loads the plan by itself.

Not liking yellow exclamation marks because the route restriction messages

One route it says invalid for my arrival airport but this is not correct. And if ELLX is my arrival airport the other route restriction messages shouldnt display. A preference for me is not to see the yellow exclamation marks on this routing.

Who is the developer at fault, Activesky, pmdg? Thanks!

Understand that it passes validation my question is why the yellow message prompts and warning about the router restriction, 2 telling me that route is only for ELLX (my destination, so why a warning?) and 1 says not for ELLX but that is a real route.

But why the route restriction error messages?

Flight today. 0730z departure FPL-CLX8512-IS -B744/H-SDE2E3FGHIJ3J7M3RWXYZ/LB1D1 HECA0730 N0481F360 DCT CVO A727 NOZ UL607 GESAD L551 ANTAR/N0469F360 UN133 KOROS/N0470F380 UN133 PEREN/N0481F400 UN128 RUGAS DCT RAXAD DCT VAL DCT DIMSI DCT OBUTI DCT RENKA UL610 UPALA Z744 LEPSA Z104 AGBUL T894 BITBU Z110 BETEX ELLX0405 EBLG PBN/A1B1C1D1L1O1S2 NAV/RNVD1E2A1 DAT/1FANS DOF/190212 REG/LXSCV EET/LGGG0044 LWSS0151 LYBA0159 LQSB0224 LDZO0230 LJLA0246 LOVV0249 EDUU0310 EBBU0358 SEL/HQBC OPR/CARGOLUX ITALIA RMK/TCAS ADSB

This is a real plan HECA to ELLX. PFPX says Route restriction errors CVO A727 NOZ UL607 GESAD L551 ANTAR/N0469F360 UN133 KOROS/N0470F380 UN133 PEREN/N0481F400 UN128 RUGAS DCT RAXAD DCT VAL DCT DIMSI DCT OBUTI DCT RENKA UL610 UPALA Z744 LEPSA Z104 AGBUL T894 BITBU Z110 BETEX

Forgot to explain that this is through the PMDG fmc. Loading in the legs page the wind data there is not an entry for the NBD every other line (fixes, vors) on the legs page has the wind data loaded in.

NDB names after exporting to the PMDG FMC are given the letters NB after the name of the navigation beacon. Example my flight plan has an NDB named SQ, loading the exported plan into PMDG's FMC, the name is SQNB Activesky does not recognize any of those points when loading wind data. Can you work with them to fix this or make the exported NDB just the name of the beacon without NB at the end?

I did on 3rd, Jan.