Flypops

Hey Dave, looking forward to the new version. Will give it a try soon. Thanks!

I just want to say that P2ATC is definitely a Love-Hate relationship. When it works it is fan-fkin-tastic and IMO and for the money is all I could ask for. I fly mostly commercial airliners and rely a lot on the vectoring capabiltiy of ATC. But there are so many broken parts to it that it can, at times, literally make me crazy. Since moving BACK to 0.2.7A things for the most part have gotten a bit better but it amazes me how often it can't recognize what it is clearly showing on the flight plan/waypoints/altitudes/couse correction/............you name it, it can't understand it. But every now and then it will fly me from portal to portal with excelllent execution..........and that is why I still use it. I don't have any other add-on that I scream at so much, have to restart so often and lose my hair over than P2ATC, but when it all comes together (along with Stick and Rudder Chatter in the background and all the SAPI voices (that I can stand)) it is a beautiful thing. Thanks Dave, don't abandon us. Not yet.

Just as this problem appeared out of nowhere, it has resolved itself the same way. I have no idea what the cause was but likely hardware issue as I've been adding some peripherals such as the Buttkicker and also some software that interfaces with the PC sound system so that was likely the cause.

This is a new to me problem never experienced before with several years of use. Mic is no longer recognized and a Sounds Refresh brings up an error message. Well apparently I can't post a screenshot directly from my PC and I don't use any online services for images but it is a long error message starting with "Error in RefreshSoundinputDevices:" and ending with "DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout) at System.Windows,Threadin,Dispatcher,Invoke(Action callback) at P2ADataLinq.AppSettings.RefreshSoundInputDevices()" Any help appreciated.

Yeah, it's pretty much un-usable for me lately. I've yet to have a flight where I haven't had to shutdown and restart at least a couple of times. Lately it's been trying to clear me for landing before I'm even halfway through my SID procedure. Sometimes I just shut it down during the major part of my flight and re-start it before descent. But that doesn't always work either. Maybe it's time to re-look at BATC.

I can't imagine this doesn't exist but I've scoured the manual and can't find any mention of it and neither can I find it in the Settings Menu. I'm pretty sure I used it in v2.

Ok, Great, thank you.

So in order to perform the proper step climbs I suppose I just need to request the climb altitudes as I get to the specific waypoints? Otherwise I will constantly be pestered to descend back to FL 300.

Thanks Dave, I missed that check box. Will try again.

I'm trying to setup a long haul in the PMDG 777-300ER and I keep getting this error message which is preventing me from Validating and Filing a FP. Due to the necessary Step Climb procedure (P2A does not seem to be able to discern this) the FL alt. is coming in at FL300 when in fact the FP clearly shows step climbs up to FL 360. When I try and change the Cruise Alt. in P2A it appears to accept it at FL 360 and the altitudes in the Trgt Alt column confirm that but the message persists and I'm unable to fly. I have already checked all possible "Ignore" boxes in the ATC Settings tab so I'm at a loss.

Okay disregard, sorry. Found the problem and should have looked through some of the other posts before posting myself. It was the same problem as described in those posts. Once I uninstalled the MS Natural Voices it seems fine.

I'm a long time P2ATC user from MSFS 2020 and recently built a new PC and installed 2024 and I'm still on the long upward learning curve trying to get everything working. I am currently on the trial period for P2ATC V3 and fully intend to purchase as soon as my trial ends. For the most part I've been able to overcome most of the minor issues I've run into so far however I'm having a recurring problem with COM 1 voice replies when making any request whether from myself or using the "speak" request through my co-pilot. This happened shortly after first installing and then magically the problem resolved itself, at least for that first flight. However now the problem persists and I've tried various things but unable to resolve. Everything seems to work fine with speech, sounds and voices with the exception of hearing the COM 1 response to any inquiry. I can see the reply in the text window and my co-pilot replies are audible but nothing from the COM 1 frequency is heard through my headset. If I switch to COM 2, I can hear and see audio and text perfectly fine. For example I'm right now sitting at LAX and can hear ATIS on COM 1 perfectly fine but CL/DEL or GRND or any other frequency when asking for a "Radio Check" for example I only get the text to show and nothing audibly. Switching to COM 2 and tuning the BUR (Burbank airport is close by) the controller is audible (and visual text appears) and tells me that I'm "perhaps on the wrong frequency". I hope this is clearly explained. Thanks for any help.

I have followed your process exactly and nothing I do within AAO will get the tiller to work. Applying "Axis_Steering_Set" only interferes with and overides the rudder pedals. I believe you when you say it is working fine for you but there's something in my setup that is causing a conflict. I will continue to pursue it and maybe I need to uninstall and reinstall the A/C. Again I appreciate your support greatly!

So I am finally able to get the two axis to work independently but not through AAO. I can only do it using the in sim bindings using rudder axis for the pedals and nose steering axis for the joystick. Anything attempted in AAO simply puts the rudder pedals in play with both devices. I dunno why but at least it is working. Thank you for your efforts however, very much appreciate your responsiveness.

Thank you again. I'm away from the SIM but will try this later today and let you know how it goes. Best regards, Dan