I've tried multiple sim events, LVARs HVARs, etc. in Axis and Ohs, but I can't seem to get the flippin' thing mapped to anything. I have the HC Alpha and Bravo, as well as the Thrustmaster TCA Airbus throttle (that I just use for extra buttons on the 737). Thanks.
Announcement
Collapse
PMDG Forum Rules
1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.
2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.
3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.
4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.
5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.
6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.
7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.
8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.
9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.
10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com
11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator
12) HAVE FUN: This is the whole point of it all.
2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.
3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.
4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.
5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.
6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.
7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.
8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.
9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.
10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com
11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator
12) HAVE FUN: This is the whole point of it all.
See more
See less
Has anyone been able to map the autopilot disengage lever to a button or switch?
Collapse
X
-
Did you already reach out to the AAO dev for the beta version of it that exposes PMDG events? https://www.avsim.com/forums/topic/6...7-msfs-in-aao/Alex Pugh
Comment
-
The more fundamental question might be, what exactly are you trying to accomplish? If you just want to disconnect everything, can't you just use the standard AP Master On/Off toggle function?Herb Schaltegger - Father, husband, lawyer, engineer & getting too old for this $#!t. Do Not Taunt Happy Fun Ball!TM.
Comment
-
Originally posted by DrVenkman View PostThe more fundamental question might be, what exactly are you trying to accomplish? If you just want to disconnect everything, can't you just use the standard AP Master On/Off toggle function?Alex Pugh
Comment
-
Originally posted by AirBadger View Post
The default MSFS function for AP master will just re-engage AP, which is kind of annoying if you click one too many times to cancel the AP alarm.
This has worked for me in my 4-5 flights so far. It's also the standard MSFS default for AP Master On/Off. I have it mapped to a button on my throttle quadrant currently.Attached FilesHerb Schaltegger - Father, husband, lawyer, engineer & getting too old for this $#!t. Do Not Taunt Happy Fun Ball!TM.
Comment
-
Originally posted by DrVenkman View Post
Right from the Introduction document:
This has worked for me in my 4-5 flights so far. It's also the standard MSFS default for AP Master On/Off. I have it mapped to a button on my throttle quadrant currently.Alex Pugh
Comment
-
Originally posted by AirBadger View Post
I have no idea what you're trying to prove to me. It re-engages the autopilot if you click it a third time. I'm simply stating that one reason to map a button to the AP discon on the yoke is to avoid that. Sorry you went and grabbed that screenshot for no reason.Herb Schaltegger - Father, husband, lawyer, engineer & getting too old for this $#!t. Do Not Taunt Happy Fun Ball!TM.
Comment
-
Originally posted by AirBadger View Post
The default MSFS function for AP master will just re-engage AP, which is kind of annoying if you click one too many times to cancel the AP alarm.Greg N.
Avionics Systems Software Engineer
Comment
-
Originally posted by Schmegg View Post
Well - that's EXACTLY what would happen on the real aircraft too. It can't read your mind and determine what state you want it in, then disregard the number of presses you made and do what you were thinking. Like the real aircraft, you need to press the buttons the correct number of times.Alex Pugh
Comment
-
I have the disc button mapped to my throttle and I just press it once. It will disengage the autopilot and I get about 3 whoops of alarm and then it silences it.
It probably should be two presses but I think a 2nd press re engages the AP.
So not entirely realistic but it gets the job doneAndy White
i910850
RTX3090
Empty wallet
Comment
-
I use the payware version of FSUIPC and map it to my throttle quadrant button this way: in Button & switch Assignments (profile specific if you have on) press the button you wish to map, then click Select for Fs control, then in Control sent when button pressed, search for Rotor Brake and finally in the Parameter windows type 68201, finally, OK. There you go, when pressing the mapped button you'll see the autopilot disengage button moving in the VC's yoke.Sergio Naiberg
- 1 like
Comment
-
Originally posted by AirBadger View Post
I have no idea what you're trying to prove to me. It re-engages the autopilot if you click it a third time. I'm simply stating that one reason to map a button to the AP discon on the yoke is to avoid that. Sorry you went and grabbed that screenshot for no reason.Mark Adeane
- 1 like
Comment
-
We may be overthinking this. My configuration doesn't require FSUIPC (or AAO, etc.), just two joystick button assignments via the existing MSFS control options:
AUTOPILOT ON (ALT-Z)
AUTOPILOT OFF (SHIFT-ALT-Z)
The keyboard assignments are included inside the parentheses to help clarify that neither of these two commands are the traditional TOGGLE AUTOPILOT MASTER (Z) command.
So far, at least, these two command assignments seem to work fine.
Hope this helps.
John Wiesenfeld - KPBI
PPL/IFR, VATSIM C1 (ZNY)
Comment
-
Originally posted by 737NG4EVER View PostI use the payware version of FSUIPC and map it to my throttle quadrant button this way: in Button & switch Assignments (profile specific if you have on) press the button you wish to map, then click Select for Fs control, then in Control sent when button pressed, search for Rotor Brake and finally in the Parameter windows type 68201, finally, OK. There you go, when pressing the mapped button you'll see the autopilot disengage button moving in the VC's yoke.Steve Giblin
Comment
-
Originally posted by StewCal View Post
Wow, that worked! How did you ever figure that one out?Sergio Naiberg
Comment
Comment