VHHH Hong Kong SIDs/Stars Failures

[WatkinTench]

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

2 tags are required - add them in the tag section next to the title above:

• One for iteration (msfs-2020 or msfs-2024)
• One for platform (ms-store, steam, xbox, or xcloud)

Feel free to delete this quote section after adding your appropriate tags.

---

ISSUE DESCRIPTION

Description of the issue:
Sids and Stars for Hong Kong are unusable with incorrect waypoints selected (6000NM away)

If applicable, which aircraft is experiencing this issue:
Have tried both the Inibuilds A330 and 321

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

FREQUENCY OF ISSUE

Everytime
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1. Free Flight from VHHH or to VHHH select SID or STAR e.g Dalo1A SID
2. Notice waypoints HH301 and HH311

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?
3080 10GB

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

---

For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

[Itamem0no]

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes. Same happens with almost all other STARS, transitions etc. HH312, HH411, TUTBA, VH701, VH702 are all not defined in the current navdata pack, which gives them a latlong of 0000.0N/00000.0E, however they are in the approach which causes either 6700nm legs, or 0nm legs in the MCDU.

Provide extra information to complete the original description of the issue:
• Nil.

If relevant, provide additional screenshots/video:
•

[Norman999933]

Hong Kong completely redesigned the departures and arrivals with the opening of the 3rd runway. These procedures became active 28th November. Unfortunately whilst this is currently causing errors, hopefully we’re coming close to the end of runway/navdata issues at this airport.

[Super6u0]

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes

Provide extra information to complete the original description of the issue:
• I have noticed the same porblem only if you have 3rd party VHHH scenery installed. However, I have contacted WF Scenery about this issue and they said their scenery does not contain files that interfere with the navdata, so most likely it is a MSFS bug.

If relevant, provide additional screenshots/video:
•

[aiLLuSion8592]

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes

Provide extra information to complete the original description of the issue:
• [PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes, and tested with only will WF Scenery, the problem exist

If relevant, provide additional screenshots/video:
•

[ThirteenPine543]

Not only VHHH but ZGGG also have this issue. And I also suffered a huge fps drops when set STAR for VHHH or ZGGG in my fmc for ini A321neo and A330

[kusahara7]

Yes , the same case here , using WF VHHH scenery
unflyable , back to the msfs 2020

[AhwaJay]

Same issue with the WF VHHH. back to 2020 for Hong Kong

[ITF52O]

Hello, I also have the same issue. Current workaround for me is to create custom waypoints with coordinates found in OFP.

[morganthomas757]

+1 on the issue. Also happening to me at WF ZGGG. SamScene3D ZUCK shows my ZUCK03R waypoint as 6000nm away too. Very strange bug.

[Speedmarque1]

This is very strange. The bug seem to only happen when there’s an addon scenery (in this case, WFScenery’s VHHH) enabled.

Here’s the inibuilds A330, SIERA7C - ILS 07L with no addon scenery for VHHH:

Here’s the same approach, with the WFScenery VHHH enabled:

Since other airports also have this problem when addon sceneries are enabled, I’m suggesting that the addons may have inadvertently modified something that corrupted the navdata, even though they say they didn’t. But I haven’t seen issues with airports in other parts of the world, so it might be something to do with the China region only.

[kusahara7]

Yes, the happen is when using addon scenery !

[PlatonicHades3]

I am having the same issue in MSFS 2024 with VHHH (WF Scenery).