Jump to content
The simFlight Network Forums
Sign in to follow this  
sisoffi

Fsuipc offset from event id

Recommended Posts

Hi Pete,

is possible to to trace an offset starting from the event id or from the hexadecimal?

having a pushbutton to be commanded as on press ON and again status OFF on second click

I need to use offsets instead of the event ID in order to be able to put the condition ($ = 1,0,1).

Thank you 

Simone

 

 

Share this post


Link to post
Share on other sites
35 minutes ago, sisoffi said:

is possible to to trace an offset starting from the event id or from the hexadecimal?

There is not always a direct relationship between the data values provided in offsets to the events or controls used to handle the aircraft. You need to search by function and be ready to interpret alternative terms for the same things.

38 minutes ago, sisoffi said:

I need to use offsets instead of the event ID in order to be able to put the condition ($ = 1,0,1).

For a toggle condiition (i.e. one which is either on or off), it might be based on some value, or it may only be represented by a single bit in an array of bits. If you can't locate the values you need, ask specifically and i'll see if I can help. There's no general method.

Pete

 

Share this post


Link to post
Share on other sites

thank you pete.

I monitored via fsuipc logging and the parameters affecting the event ID (in my case maddogX 69929 efis control the airports button show in ND) are as follows:
at the first press (ON state) 16777217
at the second press (OFF state) 16777216

but in mobiflight cannot assign on press and on release because if i press ON is correct show APTS but when i instantly released the button give me state OFF.

Share this post


Link to post
Share on other sites

I think you’d better show the Log itself, please, so I can make sense of this.

   You really need to test with a default aircraft because many addons do their own thing but the offset data is sim data, not addon (except for the special cases of the three PMDG Boeing’s)

Pete

 

Share this post


Link to post
Share on other sites

That log unfortunately doesn't show some vital details, such as the version of P3D4 or 5 you are running or the precise Identity of the aircraft. You pressed the "New Log" button, so starting a new log and leaving the old one renamed in the folder.  Please don't do that unless asked to.

Anyway, let's see:

Quote

(in my case maddogX 69929 efis control the airports button show in ND) are as follows:
at the first press (ON state) 16777217
at the second press (OFF state) 16777216

Event 69929 is not a default event or control. The highest number used even by the latest P3D5 is 68120. You appear to be using custom controls specific to the aircraft, much like those provided by the PMDG Boeings.

Furthermore, though the Log was intended to show me this, there is no occurrence of control number 69929 in the log!! There are 66917's, with parameters 16777217 (0x01000001) and 16777216 (0x01000000). Not how simple the numbers are in hexadecimal. They appear to be flags so I suspect these are mouse codes.

I'm afraid that unless the makers of your aircraft have provided some indication for you to use, or a separate control to simply toggle the switch, you will probably have to find a different way, such as perhaps using two buttons or a latching switch.

Pete

 

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.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.