lonewolf

With the evidence I have, I do agree that the initial cause is outside addons, but I don't see how the TCAS warning staying on after those addons are closed could still be from the addons. Like I stated before, I'm no dev. So if I am wrong, I'd be interested in learning how the addon is causing the TCAS warning to be persistant. Could you point me to another forum thread if it's already been explained?

I obviously did look at the forums. That's how I ended up here. So sorry I didn't dig deap enough to satisy your expectations. You too have a bad tendency of being rude to other users on here. Not a good look, especially when the other people are trying to fix a problem or help the devs with more info regarding a problem. Hope your day gets better too.

Providing bug information for the devs is always helpful, regardless of whether or not it's a known issue. What's not helpful is someone constantly being rude and belittling others on a forum for trying to solve problems. You have a bad habbit of doing that. Hope your day gets better.

I've been having this same issue. For context if the devs look at this, I'm on MSFS 2024. I don't have native MSFS traffic on. I use traffic injection from either SayIntentions or BeyondATC. I have this issue using either SI or BATC. I have let SI know with a bug report, but it seems this may be a bug on the inibuilds side(I'm not a dev so this is just my assumption based off the evidence I have). If I change TCAS to TA only, the alert goes away, but I can change back to TA/RA and it's immediately back. It stays for the remainder of the flight even if I close SI or BATC. I too am getting the warnings even when there is no possible way any conflict could exist(i.e. other aircraft is 35-40nm in front of me heading either left or right of me and my direction of travel with a 2K+ feet difference in altitude.

Update on this. I just finished a flight and hand flew the landing. I ended up floating long but did retard the throttles before touchdown. I had the same issue with the command not stopping. So now I'm thinking that maybe this is possibly tied to a percentage of the runway?

My attention was taken away right at landing and I did not pull the throttles back to idle until a couple seconds after touchdown. The "Retard" command did not stop even after getting to the gate and completely shutting down. Retard.mp4