Two unstable outputs of ROPS-RUNWAY TOO SHORT ?

  • Hi everyone, recently I found two outputs related to ROPS-RUNWAY TOO SHORT in A380.tmd, one is RunwayWarningTooShort.Output and the other is RunwayIsTooShortOutput . I used them as inputs for a few sounds, but didn't pay attention to them. Later, when I approached LOWW, I triggered the Runway Too Short warning that I had written before, after RA 400ft. After porting it to my A350 mod, I also triggered the warning. Today, when I tried to trigger it again, there seemed to be no response. My output as a sound input is not stable? Or perhaps for some reason? Here is the screen recording that triggered the alert I added yesterday

    External Content youtu.be
    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.

    I currently don't have much experience in dynamic object programming, and I hope some masters who are proficient in it can help me take a look

  • Shiroko-CA738 April 11, 2026 at 5:46 AM

    Changed the title of the thread from “Two unstable outputs of ROPS RUNWAY TOO SHORT ?” to “Two unstable outputs of ROPS-RUNWAY TOO SHORT ?”.
  • Can you please post the code section that you added to the sound and dynamics section of the tmd? (Use the forum code block so that is displays correctly here)

    RunwayWarningTooShort.Output is the warning status based on current speed and runway length. RunwayIsTooShort is the state of the runway length check, this turns the runway length on the ND amber of too short way before the landing is attempted.

  • Can you please post the code section that you added to the sound and dynamics section of the tmd? (Use the forum code block so that is displays correctly here)

    RunwayWarningTooShort.Output is the warning status based on current speed and runway length. RunwayIsTooShort is the state of the runway length check, this turns the runway length on the ND amber of too short way before the landing is attempted.

    I don't know why using this feature makes the code I write become like a staircase (although it seems fine this time, it does look like a staircase at other times), even though it looks normal in my text editor

  • Btw, I've been looking through that code since you sent it to me, there are a few errors.

    Do the stall and bank sounds work for you? I was planning to work on it tonight, only part that worked on my system was the 80ft altitude callout

    Of course, I tested them on FSG on multiple devices and there were no issues. I also had my friends test it and they could hear the sound(FS4 is also fine, there's no problem)

  • I don't know why using this feature makes the code I write become like a staircase (although it seems fine this time, it does look like a staircase at other times), even though it looks normal in my text editor

    The RunwayIsTooShort is not useful to trigger the sound. It only indicates that the selected runway for landing is currently too short and changes when BTV runway exit selected or when runway condition changed. So this would just trigger when the ND runway indication at the top of the screen switches from white/green to amber. It does not change on final approach and therefor does not trigger the sound at the right moment.

    Instead modify the RunwayWarningTooShort output so that it uses your own logic to trigger the warning sound and then feed that to the sound section to trigger an aural sound. RunwayWarning.OutputRunwayTooShort currently only returns zero and the functionality is not yet implemented.

  • Just the A350

    The RunwayIsTooShort is not useful to trigger the sound. It only indicates that the selected runway for landing is currently too short and changes when BTV runway exit selected or when runway condition changed. So this would just trigger when the ND runway indication at the top of the screen switches from white/green to amber. It does not change on final approach and therefor does not trigger the sound at the right moment.

    Instead modify the RunwayWarningTooShort output so that it uses your own logic to trigger the warning sound and then feed that to the sound section to trigger an aural sound. RunwayWarning.OutputRunwayTooShort currently only returns zero and the functionality is not yet implemented.

    Apparently row/rop is on your Wishlist is that true?