mcpiloto

The decrease throttle is the command to trigger the reverses in the sim. That’s why I was assigning this command in the axis and ohs!

What I don’t understand is why the axis and ohs is interfering in the command applied in the sim?

I don’t know if I’m doing something wrong. I just have followed the sequence, clicking on the button adding an axis, find the axis that I want to use, mapping a hardware axis to apply the command, and saving. After I have assigned all the commands that I wanted I create a template for them!

I have created the template mapping the buttons and assigning commands to then! The command decrease throttle, doesn’t work on the axis and ohs, that’s why I’m using the sim for this command!

Template! Other thing, I have mapped a button for the command decrease throttle in the sim, not in the axis and ohs. When the axis and ohs is connected to the sim, this button does not work as well!

For example, if the heading mode is on, the aircraft does not follow the head select, but as soon as I disconnect axis and ohs, the aircraft starts turning to follow the head selected!

When the axis and Ohs is connected to the sim, the autopilot and the reverse throttle, decrease throttle command in the sim, stop working. The FD stop following the magenta line, and the command decrease throttle does not work. Some help would really be appreciated.

Sometimes the axis and ohs is interrupting the functionalities of the autopilot, for example, the FD stop following the magenta line. When it happens, I need to disconnect the axis and ohs and then connect it again. Other issue is happening with the command decrease throttle. This command is located in the MSFS, but when the software axis and ohs is connected to the sim, the decrease throttle command doesn’t work, it works only with the program disconnected. Some help would really be appreciated!

I wrote in call sign: Airline/Manufacturer - Papa Tango Flight/ Tail Number - Charlie Hotel Delta But the pilot2atc said Papa Tango Lima Tango Alpha when I did the firt call. Why did this happen? My flight plan: SBSP SPO IG BCG SBBP Flight Level: 070 When I was going up the ATC center asked me to go down three thousand five hundred feet. After that, no message was transmitted, so I arrived at SBBP and landed without air traffic control. Why did the Center ask me to go down if I was going up passing five thousand feet for altitude seven thousand feet?

I have a AIRAC subscription, but I don't know to upgrade the P2A! Can you help me, please?

When I was doing a flight from SBCF to SBRJ SID UGRA1A transition DEJAN star UGRA1C transition TOKIM, at the approach fase the ATC said: TAM 3084 climb to flight level 160. I was at six thousand feet and the next waypoint was to three thousand one hundred feet. After it, the ATC said: TAM 3084 mantain six thousand feet and I had to get off to three thousand one hundred feet. The program also crashed a few times. Other times, the active runway does not the same as the program Pilot2atc. Also needs upgrade the airac! And finally, at the TOD point the ATC did not say to go down. It happened only few moments after to pass the TOD point.

Doing a flight from SBSP (São Paulo) to SBCF (Belo Horizonte) the Pilot2atc stoped work when I was at the approach fase, appeared the message: Minimum Atitude set to MInimum SID altitude at SCP. The program didn't give descend instructions and this message appeared some times. The options ATC Assigns Sid, Stars and Approaches was selected. There was some altitudes wrongs; waypoint OPKES FL190, and the next waypoint TOD FL250. How can the TOD stay bigger then the waypoint previous. The flight plan was: SBSP SID PUKR1C RW 17R, STAR ISVA1A RW16, APPR ILS RW16 I16X CF009 SBCF

Hi Dave, Yesterday I was doing a flight (SBSP Sid PUKR1A RW 17R transition DORLU STAR UGRA1B RW 20L Approach NDB N20LY RW20L Transition GELUT Arrival SBRJ) and happened some bugs with the version 2.0.1.16. 1) There was that bug with the squawk, the clearance delivery asked me set squawk 6120 and a few moments before take off, the tower asked me set squawk 2000, and after of take off, the center asked me set squawk 5252. 2) The atc ground was repeating the instructions for the taxi after I did the read back. 3) The approach vectors was wrong again. So, I did standard arrival ignoring the atc instructions.

Dave, I'm keeping all options deselected! [ ] ATC Assigns SID [ ] ATC Assigns STARS [ ] ATC Assigns Approaches [ ] ATC Gives vectors to IF [ ] ATC Ignores published speeds [ ] ATC Ignores Below 10000ft Speed [ ] Force pilot runway selection [ ] Auto Load recommended Procedures I was keeping only the option ([ ] ATC Gives vectors to IF) marked, but the landing vectors provided ATC wasn't correct. So, I disable it.

Sorry, I'm Brasiliam. I'm learning how to speak English. I wasn't doing a flight VFR, I was doing a IFR flight. The ATC Clearance delivery gave-me the squawk 3435. Then, the ATC Tower gave-me other transponder number before take off, 2000. I know it's standard VFR squawk, but I don't change the flight rules. After take off the ATC Center gave-me other squawk 6402. I think this isn't correct. When I was at 3 NM from arrival airport, I asked to Tower authorization for landing, I said: Tower, GLO 1719 request full stop landing runway 20L, and I didn't get answer.