A380 Touchdown customized sound effects successfully, but GPWS sound effects encountered difficulties

1st Official Post

    I have been studying for a while to create sound addon for AeroflyFS, and fortunately, just yesterday I added touchdown and groundroll sound effects to the A380:D, just like this

    External Content youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    However, today I tried to add AltitudeCallout sound effects for 80ft and 90ft, but I could only hear a very weak "eighty" and couldn't hear the "ninety", and I tried to copy the AltitudeCallout code from the A380. tmd, just like the txt file I attached below. If I don't make any changes and add it to the game, I won't be able to hear any AltitudeAllocate sound effects. If I add a 90ft and add the code to the game, my A380 became a Stop Block. This problem is indeed beyond my ability, so I sincerely request that all the experts can answer it;(;(;( This is my callout90ft code between the callout80ft and callout100ft

    system.txt

    system.txt ← This is the GPWS 80,90ft callout sound of my addon

    Code
                    <[float64][DurationCallout80]                [0.8]>
                                <[float64][DurationCallout90]                [0.8]>
                                                <[float64][DurationCallout100]               [1.4]>

    （This is my first time using this feature↑, so the layout may be a bit strange:(）

    I recommend this procedure when the STOP-cube appears:

    • Close FS 4 so that the tm.log resets.
    • Open and start FS4 again so that the STOP-Cube reappears.
    • Close FS 4 again.
    • Open tm.log and filter for "error". Now the error should be easy to find in the tm.log.
    • Change the error in the code.
    • Start FS 4 again.

    The whole thing only takes a few seconds for me.

    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+

    In my opinion, there is an error:

    Code
    			<[soundinput][AltitudeCallout90][]
                <[uint32][InputID][AltitudeCallouts.Output80]>
            >

    Shouldn't it be AltitudeCallout80?

    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+

    • Official Post

    The callouts for 90ft are probably not implemented in the callout object class. The actual callouts used are set by the airline, most only seem to have 70, 60, 50, 40, 30, 20 and 5. Some only from 50 down.

    When the red box appears check your tm.log file.

    You don't need to close the sim. Just let your favorite text editor reload the tm.log.

    You can then make changes to the file and simply reload the aircraft without having to restart the sim. This works reliably and I do that countless of times per day.

    Works even better if you have multiple monitors and can adjust the tmd on one monitor whilst keeping Aerofly running on the other monitor. The switching the repaint mkd flight can be used to reload the tmd entirely. Or with developer option enabled you can assign a key to reload the aircraft and reset it to the nearest runway, ready for takeoff.

    Quote from Jet-Pack (IPACS)

    ...

    You don't need to close the sim. Just let your favorite text editor reload the tm.log.

    ...

    This note is correct and important:). But when reloading, at least on my Mac, the tm.log is not reset, but only updated, which means that the list of ERROR is getting longer and longer. If I am developing and, for example, had STOP 5x due to transience errors, then I prefer to restart briefly for a search for an inexplicable error for me and then only have the current error.

    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+

    • Official Post
    Quote from ApfelFlieger

    This note is correct and important:). But when reloading, at least on my Mac, the tm.log is not reset, but only updated, which means that the list of ERROR is getting longer and longer. If I am developing and, for example, had STOP 5x due to transience errors, then I prefer to restart briefly for a search for an inexplicable error for me and then only have the current error.

    The file is getting longer, so the latest error messages are at the bottom. But you can select all text, remove it and save the file to clear the log, even when the sim is running. Any new error message in the sim means the sim has to open the file, append the message and close the file right after.