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.
See more
See less

Event Codes for Taxi Lights

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Event Codes for Taxi Lights

    I was helping a friend set up the 747 (while I am waiting for the 777 for v5 to drop 😏) and, more specifically, was trying to map the taxi light control through FSUIPC6 for him.
    Have the codes changed for the v5 version? When I look at the SDK file, I see the entry for THIRD_PARTY_EVENT_ID_MIN = 69632 and the entry for EVT_OH_LIGHT_TAXI=288 (for a combined code of 69860). When I map this through FSUIPC, I can move the switch in one direction but not the other (i.e. it does not toggle). I also notice that there are codes that end in _TOGGLE (e.g. EVT_LDG_LIGHTS_TOGGLE). This seems to imply that taxi lights have different codes for ON vs OFF.
    So, how to I get the taxi light switch to work in both directions?

    Thanks
    David Haynes
    Last edited by cnc3; 29Jul2020, 15:31. Reason: Added full name. Thought it was an attached signature.

    #2
    Answering my own questions for anyone who is interested.
    The codes in the SDK are still valid.
    The trick is that the taxi light needs to have the custom control value (69860) set but *also* the parameter set ('0' for off, and '1' for on)
    I suspect that other lights like 'strobe' and 'wing' will follow this pattern.

    David Haynes

    Comment


      #3
      Originally posted by cnc3 View Post
      Answering my own questions for anyone who is interested.
      The codes in the SDK are still valid.
      The trick is that the taxi light needs to have the custom control value (69860) set but *also* the parameter set ('0' for off, and '1' for on)
      I suspect that other lights like 'strobe' and 'wing' will follow this pattern.

      David Haynes
      Have a look at LINDA. It makes exactly this very easy
      i7-6700k, GTX 1080TI, 32GB DDR4 RAM @2666MHz, 4k
      Marc Ehnle

      Comment

      Working...
      X