• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
gamesyns

Event IDs/L:Vars Master List

Recommended Posts

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

Local Variable (lvar) List for use with hardware assignment (FSUIPC, SPAD.neXt. etc.) or custom code.

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 5

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now