Hank Sullivan

That did it. Thank you!

Since working with P2ATC, I have been frustrated that I cannot get that word not allowed copilot to shut up or let me work the radio. And today I notice that those two buttons on the Configuration screen controlling the copilot toggle on and off each time I hit the PTT button on my yoke. How do I get the buttons to just stay one way or the other, but not toggle every time I go to use the radio?

I am using P2ATC to practice for a real world instrument rating, and am enjoying it. However I do wonder about this. The sequence involving a vectors-to-final approach clearance should follow the following PTAC pattern: POSITION- I am good with that part being left out of the approach controller's language. I'm sure it would be difficult to program. TURN- Approach controller gives final heading to intercept the approach course. ALTITUDE- Approach controller gives final altitude instructions to enter the approach. CLEARANCE- Approach controller clears pilot for the approach in question. But what happens in each Vectors-to-final approach I practice, is rather than spelling PTAC, the approach controller voice says it mixed up, sort of CTA without the P, "Cleared for the ___ approach, Turn heading ______, descend and maintain ____feet." Can that sequence be changed to reflect the real world approach controller sequence of instructions? The approach clearance is one of the harder instruction sets to master. So it would be great if what we practice reflects the correct sequence. Thanks much! Hank

That works! Much better. Thank you both.

Yes, I thought Windows voice recognition is what delivered the input for P2ATC. Not so?

I'm new to P2ATC. I think it's going to be a good training device for me. By following the experiences of others, I was finally able to get speech recognition working with the program. That's the good news. The bad news is that when I hold down the mapped PTT button to issue a command for ATC, within a couple of seconds, one of several other Windows or desktop apps popup on the screen trying to use the same information I am speaking to P2ATC in a search using the results of my spoken words in their input boxes. Needless to say, it is disconcerting to have windows popping up in front of you when you are flying an airplane! The only command mapped to the PTT on the Elite sidestick yoke is to call ATC as per P2ATC instructions. What can I do to stop other windows from popping up while I am speaking a command to P2ATC? Thanks very much!

Yes, it works now. Will be buying the program. I used it all weekend. Thanks very much.

Dave, I am having the same problem. Cannot connect trial version of Pilot2ATC to X-Plane. Here's what it says: Sim connection failed Connection open failed. FSUIPC.FSUIPCException: FSUIPC Error #2: FSUIPC_ERR_NOFS. Cannot find FSUIPC or WideFS running on this machine. at FSUIPC. FSUIPCConnection.Open (byte Classinstance, Int32 RequiredFlightSimVersion) at P2A_2020.P2ASimulatorFSUIPC.OpenFSUIPC

RXP, the really important issues with the Avidyne Entegra product in the Torquesim Cirrus SR aircraft appear to be remedied. Now I wonder if I might have you take a look at the workings of the STEC55X autopilot, specifically as it relates to ILS and RNAV WAAS approaches. Essentially, there are additional steps involved in the model which do not exist in the real airplane using this equipment. Anyone using this sim as a trainer would find it confusing noting the differences. And so, I would like to steer you and your people to the following link, which discusses in detail exactly how the STEC55X should work during these approaches. Hopefully someone will be able to create time to look at this. Thanks very much. Love your product! https://genesys-aerosystems.com/sites/default/files/files/Fifty Five X for SR20-22 Avidyne.pdf

Jean-Luc, has Torquesim contacted you about the problem with the last RXP update? The Cirrus Entegra, which prior to the update would intercept and follow a vertical glide path, no longer intercepts it. Flies right by the point of interception.

That's awesome. Thank you!

RXP, has Torquesim gotten back with you about the remaining problems involving inability of using the GNS430 CDI button?

By, "they," do you mean Torquesim? Also, what is 'TG?'

When do you think we can expect an update with this fix?

Here's some more information. After booting up the SR20 Avidyne on the runway at KGVL, set to fly direct to KAND, and after manipulating the data flow settings on GPS1 which orients the bearing pointer to align with the HSI, the result is what you see here: That looks fine. But as I take off and fly according to the heading bug setting, both the HSI and Bearing pointer ought to follow each other, always pointing at KAND. The HSI works just fine, but as you can see the bearing pointer, once set, does not move. The result after a few minutes flying, and after performing a "direct-to" on the 430, you can see the bearing pointer is not seeking the bearing to the KAND waypoint. I had a couple of minutes this morning and thought I would give you some more information on the problem. Thanks very much for looking at this.