Elevation issues | Martinique

  • When the global scenery is engaged the airport and trees of my scenery starts to float.



    Is it possible to make an area around the airport completely level, or can this elevation data be redone?

    These are probably the files which causes these problems. Especailly "maph_10_5480_8a80"


    Changing the height where the buildings are placed is not the problem. But the trees can't be changed.

    And changing and updating the airport everytime the elevation data gets updated is painful.

  • I copy my post from Flight-sim.org:

    Zitat

    Your suggestion is a possibility, but in my view, disabling global elevation is not a solution for a single airport.

    I copied your TFFF.tap in the AirportCreationTool (ACT) and imported it back into the ACT as TFFF99.tap. In this copy I then created a TARMAC below the terminal to correct the elevation. This has worked successfully. Please take a look at it in the ACT.

    Two more information:
    - In the meantime, JETWAYS, FOOTWAYS, GROUNDTEXT and TAXISIGNS can also be added via the TAP file, this would upgrade TFFF.
    - If the TOC, TSC and WAD files are converted from a TAP file to a text file, then tfff00.tsc can also be integrated.


    Tschüss, Michael

    Tschüss, Michael (🍎🚁)

    Configurations:

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

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

  • Mhm, which objects are hovering in LSZB and LSZR? With my FS 4 (STEAM-beta 4.07.01.08 (20250505)) on the Mac everything is on both airports OK.

    Tschüss, Michael (🍎🚁)

    Configurations:

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

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

  • OK, now I have also found such positions.:)

    I currently have no idea how these problems as in the examples TFFF, LSZB and LSZR can be solved constructively?:/ Because the cause is easy to explain:
    (1 ) Each object has exactly 1 coordinate, regardless of its size and complexity, and this 1 coordinate also determines the altitude.
    (2) For the altitude, the default setting is the automatic height at exactly this coordinate mentioned under (1) and exactly at this point the object touches the landscape.

    At airfields, the general elevation of the airfield is usually leveled by the coordinate system "[flat]", which is not always perfect. Outside the airfields, the heights of the coordinates often change only slightly, but for larger objects it is noticeable. With individual objects (individual cars, individual houses, etc.) this is often not very noticeable, because they are relatively well suited to the height. In the case of larger objects (large hangars, several combined buildings, several combined cars) there are then the observed effects.

    The terminal in TFFF has, for example, aligned itself with a virtual hill in the parking lot, which can be equalised by a TARMAC placed under the terminal. However, in the cases observed in LSZB and LSZR, no TARMAC can be established that is not visible.

    The only solution I can think of for surfaces with height differences is to use only individual objects if possible.

    Tschüss, Michael (🍎🚁)

    Configurations:

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

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

  • Besides, as LSZB and LSZR have been implemented since FS2, only IPACS could find a solution and fix this.

    This is also true for the ALSTOM factory in Birrfeld LSZF where the same phenomenon is found.

    "For better or for worse" ;)

    Regards

  • ...

    This is also true for the ALSTOM factory in Birrfeld LSZF where the same phenomenon is found.

    In this case, in my opinion, it is about 1 building on a flat surface and therefore this height error would have to be corrected here:

    • '/Users/01user/Library/Application Support/Steam/steamapps/common/Aerofly FS 4 Flight Simulator/scenery/airports/ch/lszf/lszf.toc'

    Unfortunately, this file is compiled and can therefore only be corrected by IPACS.

    Tschüss, Michael (🍎🚁)

    Configurations:

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

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