I see another issue in the ADE screenshots. The runways do not have a designator: number=“1” designator=“NONE” primaryLanding=“TRUE” primaryTakeoff=“TRUE” primaryPattern=“RIGHT” second
No that is an issue, as far as I know there should be either left or right as a designator! Try that out and see if it solves anything, there are no issues with AIG or FSHUD and runways being either take off or landing oriented.
On further inspection, there are more errors, there are only 3 designated runways, but there are 4(we count each end of the runway, as a runway).
the other two are called runways 2left and right… I am pretty sure that its 01L and 01R and then its 19L and 19R 
Check out the code:
So this must be why VTBS doesn’t load SID and STAR data with MSFS’ default database! Thanks for clearing that up @HipPencil580862, now I hope SiamFlight can fix that. I would love to visit Thailand more often!
Hiya Thank you for helping me! HipPencil580862
I am a one-man Dev, start making airport not long ago, so I still learning till this day. 
Here’s the AIRAC of 28NOV24 when I started update the 3rd runway, Yes VTBS still have just 3 runways.
The runway on the east side is renamed to 01/19 without any designation until the 4th runway opens in the future.
I have tried what you are pointing out many times over 
without success. it always conflicts with many NAVAIDs databases version that is available for many aircraft, Asobo or the others.
I am really appreciated for you guy helping me. VTBS is my first huge airport, I don’t want to abandon it, including every customer that it’s has.
SiamFlight
When an update is needed, do it! I love this huge airport! 
Fshud has provided an update and VTBS is now visible.
Whether Sid and Star work I still have to find out. I’m working with navigraph and hope it works.
I just call my friend who use FSHud regularly, and will have speedy course learning FSHud tonight.
Got your airport and some payware. I’ll try my best to understand this.
Also thanks to you fshud3909 
SiamFlight
So Sid and Star don’t work for me.
I’m using navigraph and can’t explain this to me.
Will come back to you soon.
Hiya olli7352
Here is what I have found so far.
- I’m not much of a tech savvy but a dev tries to make sceneries/airports that I really love -
I might be right or wrong, please help me understand this. I am open to discussion.
Start with this. Here was the VTBS v1.0.11 that I test.
With SiamFlight VTBS without NaviGraph - No SIDs STARs
Here’s MSFS2020 generic without NaviGraph - No SIDs STARs
I have tried to compare NAVAIDs file of MSFS some cycle ago with older and outdate file, and it seems missing all of VTBS NAVAIDs data. So even if you use its generic airport, No SIDs STARs
Now let’s try generic VTBS with NaviGraph - No SIDs STARs
NAVAIDs data is missing, just like that, with generic airport that should be or with data from MSFS itself, No SIDs STARs
Now I bring back my VTBS with NaviGraph - SIDs STARs is here Yay!
Now let’s try this with FSHud. (will discuss about FSHud more below)
I try start from VTSM (SiamFlight)
Searching for VTBS (SiamFlight).
Getting a SID out of Samui VTSM.
Zoom out a bit.
Now focus on VTBS. (SiamFlight)
Zoom and checking the STAR.
Now let’s checking some of the setting I have.
VTBS (SiamFlight)
I hope this help, both me and everyone else. Especially my customers, thank you for your support!
Now about FSHud, olli7352 that you replies “Fshud has provided an update and VTBS is now visible”.
Is it an update? can you explain it a bit more?
From my interactions, what I am thinking is a programmer of FSHud might get the wrong idea about “PrimaryClosed/SecondaryClosed” and just thrown some BS to FSHud admin, so he/she doesn’t need to do any investigate the cause.
They said VTBS runways is flagged as closed. If that is true every runway of VTBS should have a big yellow X at the runways end.
And I think use these parameters to read the airports might not be the good idea. something is not right.
Sorry to say this but please don’t tell your customers it’s sad, it’s shame that VTBS developer, he doesn’t fix or doesn’t know how to fix his airport. It’s not nice man. 
I can be wrong still, but please.
Talk to me, and I really appreciated your help and reply.
PS. sorry for my English.
Bests.
SiamFlight
Is there any solution for the ILS in VTBS not captured by MSFS2024?
I’m on Navigraph and ILS Freq il correctly autoselected bit no signal is picked up. I tried with the ini A350 and also PMDG 772. Thanks
Matteo
Hiya.
Thanks for the report. Will checking it and come back to you soon.
Hi,
I’m experiencing an issue with the scenery: Taxiway Y-E10, which crosses Runway 02L/20R, appears closed in the scenery, but it still exists and is used by traffic according to BATC.
Worse, it seems there is no defined intersection point between the taxiway and the runway. BATC instructed me to taxi via this taxiway but didn’t give any clearance to hold short or cross the runway.
Here is a screenshot of the taxiway in FS2024:
And here is the same area in BATC—you can see traffic using the taxiway:
According to the eAIP, this taxiway is currently open. However, if it’s intentional that it should be removed to ensure consistency with the scenery, that would also be acceptable.
Best regards,
Hiya. HarGn Thanks for the report!
According to latest eAIP, TWY Y is opened.
From the older eAIP, TWY is close, but I have connected it for the convenient sake of the landing aircraft from 02L that might use fast exit TWY F4, Y, E10, E9 to E.
That’s why I don’t put any hold short there, sorry for the inconvenience. (TWY cannot specific one-way in SDK, only hold-short can)
Now the 3rd RWY is update, I might need a bit of time to update the TWY and its texture.
v1.0.11
Yes it’s update now from Google Map
NaviGraph
I might be wrong here but here is the fast exit TWY F4 in use.
Please wait a bit, for the next update.
Edited. AIRAC → eAIP.
Bests.
SiamFlight
@SiamFlight … Hi, I own the MS Store Version, and my Simulator CTD’s at VTBS either upon loading, or when I want to use the drone camera. The airport is streamed and I’m on SU2 with a completely freshly installed Win11 and MSFS2024… It’s vanilla…
So I wanted to see this beautiful airport and loaded in with the Standard Cessna, the first time it crashed once it wanted to get to the ready to fly screen, the second time I could load in but once I sat in the Cessna, and wanted to go to the drone camera it CTD’d.
Please help.
Faulting application name: FlightSimulator2024.exe, version: 1.4.20.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.4.20.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002bb7d03
Faulting process id: 0x2D80
Faulting application start time: 0x1DBC8FFFF4ACA6B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: a0cb93c1-c7b2-4c32-a4ef-0cd4fb90dfda
Faulting package full name: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Thanks for the report!
I’ll try to reproduce and research on this and come back to you soon.
Bests.
SiamFlight.
PS. for now VTBS is 2024 compatible but not really native. So, when the new SU drop it might be something wacky sometime. Appreciated the info!
When you activate the drone mode, it goes crazy. This might be the problem, I wouldn’t suspect a 3rd-party airport unless I had tried using an empty Community folder and the problem went away.
@SiamFlight Thanks for looking into that. I already encountered this mysterious behavior in SU1 but never reported it. No problems with my other sceneries from the Marketplace. If I can assist you with any logs you’d need, please contact me…
@ davegranstrom16 as I mentioned in the Report, its a vanilla install meaning NOTING is in the Community folder, and even Windows is freshly installed.
@liketofly7266 in my mind, because it’s Marketplace version. it’s still had WASM code for VDGS.
If there anything can CTD, it’s WASM and likely the code for 2020 and might not 100% compatible with 2024. and need a bit of time to test it.
