Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FSX WBKK AFCAD

Featured Replies

Hello,I am using the wbkk_mw.zip (http://library.avsim.net/zipdiver.php?DLID=117076) AFCAD file, and am finding my aircraft does not descend lower than 80 feet on the ILS 02 runway approach. Consequently, the aircraft overshoots the runway unless I set the engines to idle at 80 instead of 50 feet.Do you know why is this, and how can it be fixed with Airport Design Editor X?

Harry Sung

I think the glideslope antenna is misplaced, but there are so many problems with the default WBKK which this file only begins to deal with that it needs to be redone from scratch. I've found numerous problems with navaids in Sarawak and I imagine Sabah is in the same situation.scott s..

  • Author

Actually, I landed perfectly using the default FSX AFCAD :( Today, I found the WBKK_MW.ZIP file doesn't have any approaches - using Airport Design Editor X. So, I imported the approaches the default AFCAD, but I have yet to try another landing at the airport ...

Harry Sung

  • 2 weeks later...
  • Author

Just tried another landing at WBKK, and my aircraft still doesn't descend to 50 feet on the ILS 02 approach, but descended a further 10 feet from 80 with the addition of the stock approaches. What is strange is ADEX did not compile the stock Route Waypoints. They are in the .ade file, but not the compiled .bgl file.Does anyone know what is the cause?I have compared the location of the ILS DME, and it appears to be the same as the stock AFCAD.

Harry Sung

Just tried another landing at WBKK, and my aircraft still doesn't descend to 50 feet on the ILS 02 approach, but descended a further 10 feet from 80 with the addition of the stock approaches. What is strange is ADEX did not compile the stock Route Waypoints. They are in the .ade file, but not the compiled .bgl file.Does anyone know what is the cause?I have compared the location of the ILS DME, and it appears to be the same as the stock AFCAD.
Yes. They are not compiled because there is no point. Stock waypoints in FSX cannot be moved or edited so the default ones will be used in FSX. ADEX includes them in the project so that they can be seen in the approach editor.

Jon

-------

Microsoft Flight Sim MVP

Airport Design Editor FSDeveloper.com

  • Author

Thanks Jon for clarifying why I can't see the Route Waypoints in my .bgl file.Rather than start another thread, I have another question about ADEX. I imported a couple of auto generated building (ZPPP terminals) from a stock AFCAD into my project airport. When I compiled them, I cannot see them in the .bgl or in FSX.What is the reason behind this?Cheers, Harry

Harry Sung

Thanks Jon for clarifying why I can't see the Route Waypoints in my .bgl file.Rather than start another thread, I have another question about ADEX. I imported a couple of auto generated building (ZPPP terminals) from a stock AFCAD into my project airport. When I compiled them, I cannot see them in the .bgl or in FSX.What is the reason behind this?Cheers, Harry
Are they geo locked?

Jon

-------

Microsoft Flight Sim MVP

Airport Design Editor FSDeveloper.com

  • Author

I managed to save/transfer the stock ZLXY's generic flat roof building (blue rectangle) to my AFCAD, but what I cannot save/transfer is the autogenerated stock library object (yellow rectangle).The first pic shows the stock ZLXY AFCAD has 2-3 storeys, but the second pic of my AFCAD only has one storey. Why is this and how do I tell if it's geo locked?Cheers, Harry

Harry Sung

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.