HK - VHHH(ex) KAI TAK AIRPORT online

  • ...Is there anyway to add SID's / STAR's etc so we can navigate to/from Kai Tak or is this imbedded in the AFS4 core navigation files?

    At this point I'm still not sure how to solve this.:/

    - I can imagine that Jet-Pack (IPACS) can help here?
    - Maybe a mission would also be helpful?
    - And I want to see whether a fictitious runway as an extension of the checkerboard is helpful as an approach aid.

    And I'm also missing the approach lighting RW13 in the curve, so maybe I can use some navigation signals there.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • ...
    And I'm also missing the approach lighting RW13 in the curve, so maybe I can use some navigation signals there.

    The first test shows: This should work.😆

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The reason is relatively simple:
    In the original, VHHH KAI TAK INTL AIRPORT was decommissioned in 1998 and VHHH CHEK LAP KOK AIRPORT was put into operation instead.
    In the simulation, IPACS therefore also saved the correct data from today under VHHH.

    In contrast to reality, IPACS would now have to record the data from KAI TAK AIRPORT under a different ICAO code such as VHHX. The highlight would be if the IGS were programmed for RW13 instead of ILS. In my opinion, it would be enough to set up a fictitious ILS on the CheckerBoard.

    However, I understand if IPACS does not want to make this effort at the moment because other points are more important.

    I'm currently successfully working on at least supporting the approach with an optical light guide like the one in reality.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The reason is relatively simple:
    In the original, VHHH KAI TAK INTL AIRPORT was decommissioned in 1998 and VHHH CHEK LAP KOK AIRPORT was put into operation instead.
    In the simulation, IPACS therefore also saved the correct data from today under VHHH.

    In contrast to reality, IPACS would now have to record the data from KAI TAK AIRPORT under a different ICAO code such as VHHX. The highlight would be if the IGS were programmed for RW13 instead of ILS. In my opinion, it would be enough to set up a fictitious ILS on the CheckerBoard.

    However, I understand if IPACS does not want to make this effort at the moment because other points are more important.

    I'm currently successfully working on at least supporting the approach with an optical light guide like the one in reality.

    I understand now, thanks. It will certainly be great to have a proper Kai Tak airport in the sim. Thank you for your mod, it is really fun to do the approaches!

  • Non-standard buildings are stored in the "poi" directory in FS 4, as is the case with "toulouse_city", for example:


    But I haven't yet looked into how this works for us users.

    So far I have inserted buildings from FS 2 as part of airport files.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • Non-standard buildings are stored in the "poi" directory in FS 4, as is the case with "toulouse_city", for example:


    But I haven't yet looked into how this works for us users.

    So far I have inserted buildings from FS 2 as part of airport files.

    Do I need to change the name when I join a building? (I can't use it after pouring it directly)

    Love comes from the country in the middle, the vast east:P

  • I have uploaded a new version of VHHH(ex) KAI TAK INTL AIRPORT:

    This contains the tower beacon light as well as the approach lighting of the RW13 located in the curve.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

    Edited once, last by ApfelFlieger (January 29, 2024 at 9:20 PM).

  • I have also uploaded a new version of Hong Kong-AddOn:

    The EDITION 2024-01-09 unfortunately led to many error entries in the tm.log file.:( The revised EDITION 2024-01-09 only has 2 errors caused by the building "city_intl_trade_exhibition_centre"; the 3D container ships in the harbor were left out and the harbor cranes were converted to XREF (and their number was almost doubled).:)

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • And last but not least, I uploaded 1 airport and 26 heliports for Hong Kong:


    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • Perhaps an expert in elevation mesh can help better map the topography of Hong Kong.:/

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The lighting effects can be freely programmed in all respects.

    I'll write later how it works.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • Here is an example of how lights in FS4 can be called up via the TAP file:

    A call via a TOC file is also possible, although the TOC files usual in FS2 have to be integrated differently in FS4.

    Some notes on the individual lines:

    165:
    - the RGB values can also be entered between 0 and 1 with decimal places

    166:
    - the intensity goes from 0-♾️

    167:
    - this is the most complex setting because three different parameters are entered here

    168:
    - unfortunately, so far I have only found the difference between the values 0 and 1
    => I'm missing a value for a glow during the day

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The TAP and TSC files as well as uncompiled TOC files can be opened and modified with a text editor. I started years ago with small steps and gradually moved towards my current knowledge.

    The TAP file must then be compiled into the 4 files TMB, TOC, TSC and WAD, as I write in the accompanying text. This is quick and easy.

    The additional TSC file (with a different name than the TAP file) with data from FS2, if present, does not need to be further compiled.

    I consciously always publish the TAP files for my airports in the spirit of an open source concept. So everyone can see how something is programmed by me in detail. And I'm happy about everyone who does the same. This way you can easily see how others do something - and you can also build on what already exists and easily adapt and further develop it for yourself. My wish for IPACS is that IPACS also publishes the TAP files.😀

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The light settings for the buoys are in the directory "as_hk_hk0000_hong_kong_addon/water_buoys" in the file "lighthuse_light_cultivation.toc", which I am attaching as a ZIP file.

    Files

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+