Klegran

I believe the tread is about BeyondATC; the title is quoting the end of the BATC trailer in which it said "BeyondATC is a new ATC coming to MSFS 2020 + 2024"

Good to know. Thanks.

Can you elaborate?

But FS Hud doesn't actually do a good job controlling the traffic does it? It's using the same broken API as all other traffic injectors use so you still get planes that teleport around, spin in place, and all other sorts of wacky behavior. Based on the other response it would appear this is an Asobo issue and no 3rd party tool can truly control the traffic even if they claim to. Have you had a different experience with FS Hud?

Also posted in the discord: And as for FS Hud, it controls it to an extent, it still has to use the injection API which has all sorts of bugs. FSLTL has posted about this many times, that you can only control the traffic up to a point, but once you hand it off to MSFS, it will do very silly things. I hope they improve this in 2024. If they do we would highly consider controlling it directly, but in my extended play with FS Hud, the traffic injection suffers the same issues as all the other traffic injectors. My experience is that no traffic injector works well because of the myriad of AI Traffic bugs that exist in the sim that cannot be overcome without core changes to the traffic API. Here's hoping that 2024 allows finer control over AI traffic

From the Pilot2Atc manual: It would seem this information is wildly out of date, as this only pertains to FSX and P3D which does not apply to MSFS. As well, FSAeroData no longer offers this service. So this entry in the user guide seems to be years old at this point. What is the best way to update Pilot2Atc with current ARTCC data? As far as I can tell Navigraph doesn't provide frequency information, only the fir-uir boundary data. So this will need to come from another external source. Thoughts? Thanks for the help!

That's good to hear there's some plans for "pseudo-controlling" of AI planes. Even if they made some rough calls about what to do and where to go it would be 100x more immersive than a ghost town over the radio! (Even with ATC chatter). I'm curious, I was flying some flights using FSLTL and Pilot2Atc is supposed to have me respond to traffic, correct? The taxi way was quite full and I did not get any hold instructions or anything acknowledgment of the other airplanes on the taxiway. This functionality is currently supported, right?

With the release of FSLTL, which in my opinion, is the new standard for offline flying with traffic, I'm wondering how Pilot2Atc can position itself to be the de facto software for offline ATC. The main issue I see is the glaring disconnect between the planes being added to the sim by FSLTL and P2Atc. You see traffic all around you, yet none of them interact with the ATC. You feel completely alone, dispite being surrounded by other planes. FSHud is able to have the other planes communicate with the controller, but FSHud is no where near the level that P2Atc is at. I realize that the main difference here is that FSHud is a traffic injector itself, and thus can manage the outside traffic and including this type of functionality within P2Atc would probably be outside the scope of the software. However, maybe there is a middle ground? If P2Atc can knows about the traffic in the sim at any moment, and knows about their intentions, is it possible to have them make and receive calls to the controller? Even if they are not directly controlled by P2Atc, having the other airplanes within the sim communicating to the controller would completely round out the experience and set P2Atc as the best offline ATC software available on the market. Would love to hear thoughts from Dave, and the community about using FSLTL and P2Atc together to create the ultimate experience. 🙂

Ah of course! Using it in that way had not occurred to me because of the presence of blindable hotkey to that function so I figured I needed to preemtively tell the co-pilot to react instead of reactively doing so. That way makes far more sense, so thank you for the idea! I do still see value in being able to just hand over complete control to the co-pilot if the workload is high, allowing you to have one less thing to do by using SayIt. But I think by in large, your solution will work for most use cases. Thanks so much for the quick reply and great tool! It's been a real joy to fly with.

Hi there. Just got Pilot2Atc and am absolutely loving it. First question: I see you can bind a hotkey/joystick input/button to the functionality to turn on/off the your automatic co-pilot handling the responses. But this also turns off them handing the switching of the radio, which most of the time I wish to keep one but not the other. Is there a way to decouple this functionality or perhaps even have two different inputs, one for each? Second question: There is no feedback given to see which state the co-pilot is in, auto respond or ignore. You have to manually keep track of when you hit the button, which of course is double as hard if you hit the button by mistake and then become unaware of which response state the co-pilot is in. Would it be possible to get a que, a sound or some sort of visual indicator as to which state the toggle input changes the co-pilot to? I notice this audio acknowledgment pattern is utilize in other places within the tool, such as when you speak a recognized phrase. I believe this functionality would as well benefit from that same style acknowledgment (unless I've missed something that already exists to fill this role). Thanks so much for the consideration!