gamesyns

Event IDs/L:Vars Master List

Recommended Posts

Event IDs and Local Variable Master List for use with hardware assignments (FSUIPC, SPAD.neXt. etc.), the key_event functions, or our SimConnect trigger event API.

SimConnect API Events (Currently applies to Community Opt-in Beta versions only) for use with custom code: 

Quote

TD717.TRIGGEREVENT

Usage: To allow external applications to trigger custom events from SimConnect without the use of a gauge/bridge. Trigger with dwData set to the event ID to trigger.

Quote

TD717.ATTNDCALL, TD717.MECHCALL, TD717.PA
Usage: Subscribe to (but not mask) these events to be notified when these events happen.

 

  • Like 6

Share this post


Link to post
Share on other sites

Im sorry, but can anyone explain what this is exactly?  Is this id something for us to include when reporting a problem or is this list all the things they're fixing?

Share this post


Link to post
Share on other sites
3 hours ago, Novej said:

Im sorry, but can anyone explain what this is exactly?  Is this id something for us to include when reporting a problem or is this list all the things they're fixing?

They are for mapping cockpit controls to hardware switches and buttons via fsuipc etc.

Dave

  • Like 1

Share this post


Link to post
Share on other sites
5 minutes ago, DaveDewhurst said:

They are for mapping cockpit controls to hardware switches and buttons via fsuipc etc.

Dave

Ahhhh thank you good sir!

Share this post


Link to post
Share on other sites

THANK YOU Joshua, by mapping a keyboard button to the AFS control knobs I could finally get them to turn at a good speed!

Share this post


Link to post
Share on other sites

But the remaining question is the variables needed to drive physical MCP hardware displays such as IAS , Heading, VS & Altitude. Default FSX and P3D simconnect variables don't work.

Edit: there's at least 4 hardware vendors that need this to make their MCP's work with this aircraft. Even if you could create a new variable as a read only so we could display it, would be nice. Thanks.

 

 

Edited by Slayer

Share this post


Link to post
Share on other sites
33 minutes ago, Slayer said:

But the remaining question is the variables needed to drive physical MCP hardware displays such as IAS , Heading, VS & Altitude. Default FSX and P3D simconnect variables don't work.

Edit: there's at least 4 hardware vendors that need this to make their MCP's work with this aircraft. Even if you could create a new variable as a read only so we could display it, would be nice. Thanks.

 

 

 

We're working on a formal SDK at the moment that will allow access to those variables, currently, there are no variables for those numbers.

Share this post


Link to post
Share on other sites

How can I set buttons for raising/lowering gear? I can see a Gear Release command on the main instrument panel list, but this sounds more like alternate gear extension - is this a gear cycle command?

Share this post


Link to post
Share on other sites
13 minutes ago, Blythy said:

How can I set buttons for raising/lowering gear? I can see a Gear Release command on the main instrument panel list, but this sounds more like alternate gear extension - is this a gear cycle command?

 

The gear cycle is the same as default, it reads that event. Gear Release is for when you hit G on the ground, the gear lever gets unlocked, then a little button on the lever panel becomes clickable to release to the full upright position. Hopefully that makes sense.

Share this post


Link to post
Share on other sites

Is there someone here who can clearly explain how to use these to setup controls using FSUIPC registered? I'm trying to get the Yoke AP Disco, the throttle ATS disco and the throttle go around buttons to be bound to my HOTAS.

Share this post


Link to post
Share on other sites

I have to admit, I do not know how to use this although i program a lot in registered FSUIPC.    Any help appreciated to instruct/example of how to use these.  I can't seem to get the to take  in FSUIPC . . . 

 

Thanks in advance, Joe Porter

 

Share this post


Link to post
Share on other sites

Hello, I am using the Honeycomb Yoke and it comes with an app that allows the assignment of keyboard events or lvar events to the switches and buttons.  I've been successful in mapping this with many of my other aircraft, including the Majestic Q400, FSW Learjet, Falcon, Mu-2, the Coolsky DC-9, Carenado C-185, and a few others.  However, for the life of me, I can't seem to do this with the 717.

An example would be for the Majestic Q400, I have a switch configured for a switch on the panel to turn on/off nose wheel steering:

Spoiler

    {
      "ButtonNumber": 12,
      "PressEvent": [
        {
          "Variable": ">L:SIDE_PNL_STEERING",
          "Value": "1",
          "Condition": "",
          "ConditionValue": "",
          "Repeat": false,
          "DE": null,
          "EN": null,
          "FR": null,
          "ES": null
        }
      ],
      "ReleaseEvent": [
        {
          "Variable": "",
          "Value": "",
          "DE": null,
          "EN": null,
          "FR": null,
          "ES": null
        }
      ]
    },

Basically it is just specifying the name of an LVAR and then setting a value, or if is a toggle, then no value is required.

However, I can't seem to understand the analogy for the event list for the 717.  I see the list and select, for example B717_ovhd_lights_bcn but I seem to need to specify an integer value, which isn't provided on the linked list.  I've used Doug Dawson's p3_xml_vars_x64 gauge to monitor the LVARs as well and despite matching the integer values for on and off, it doesn't seem to have an impact.  I see that when the lights are on the LVAR DEC value is 35 and then off it is 0.  However, when I specify those I can see the variable change in the xml vars gauge, and I see the button move on the overhead, but the condition of the lights doesn't change.

I also tried the simple approach of mapping to the built-in beacon light command in P3D and that doesn't work either.

Has anyone had luck or can someone point me in the right direction with respect to mapping any of these events to buttons?

 

Share this post


Link to post
Share on other sites

You'll want to map events, not variable control - i.e. make pressing your switch trigger the button press event. Most of our code is built with that idea in mind.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.