Jump to content
The simFlight Network Forums

Recommended Posts

Posted (edited)

*** Moved from main support forum to FSUIPC7 / MSFS support sub-forum ***

Hello,

I am referencing TFDi's website TFDi Design MD-11 Integration Guide | Invernyx Docs where it documents eventID's for most buttons in the cockpit. (Click on EventID's on the left to slew the page to the list). With these it was a breeze to program all EFIS SD system page buttons on my joystick. However now I am trying some oth buttons but have hit a wall. The procedure does not work. I have attached the log file. The event between 32906 and 33422 is a successful programming and implementation of selecting a button in the cockpit. (SD ENG page). The events between 37812 and 38047 show how even though I programmed the button exactly the same way as the previous one. It does not work.

Any ideas?

 

FSUIPC7_prev.log

Edited by John Dowson
Moved to FSUIPC7 support sub-forum
Posted
30 minutes ago, xkoote said:

The event between 32906 and 33422 is a successful programming and implementation of selecting a button in the cockpit. (SD ENG page). The events between 37812 and 38047 show how even though I programmed the button exactly the same way as the previous one. It does not work.

What event/control numbers are those? Third-party events start at number 69632, and the first/lowest custom event number shown in that web page is this one:
    EVT_MD11_PED_CPT_RADIO_PNL_XFER_BT_LEFT_BUTTON_DOWN            69644
i.e. event 69664.

If you look at the log file you posted, you will see this:

Quote

     4140 Mapping custom control numbers 69632 - 84232

So this is the range you can use for third-party events (also known as custom controls). Looks like the TFI Design MD-11 uses third-party control numbers from 69644 to 96323, so you currently won't be able to use those above 84232. This is currently a hard-coded maximum. For the next release I will add an additional ini parameter so that the max custom control/event number can be specified. I will release the next version shortly after SU15 is released, which should be any day now. Once I have made this change, I will also post details in this topic and can maybe supply you a beta version to test (if not released yet).

Your log file shows errors when using custom events above 84232:

Quote

    37812 Button changed: bRef=0, Joy=2 (L), Btn=11, Pressed
    37812 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 70=PL,11,C86094,0
    37812 FS Control Sent: Ctrl=86094, Param=0  <86094>
    37812 Exception 1 "ERROR", Ref 19655, Index param 2 on TransmitClientEvent, object=1, id=86094 (????), data=0
    38031 Button changed: bRef=0, Joy=2 (L), Btn=11, Released
    38031 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 71=UL,11,C86095,0
    38031 FS Control Sent: Ctrl=86095, Param=0  <86095>
    38047 Exception 1 "ERROR", Ref 19656, Index param 2 on TransmitClientEvent, object=1, id=86095 (????), data=0

These other errors in your log file:

Quote

     5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 17=PJ,31,CPMD11 AutoBrake OFF,0
     5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:md11_ctr_autobrake_sw,number)'
     5109 Button changed: bRef=0, Joy=1 (J), Btn=16, Pressed
     5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 31=PJ,16,CPMD11 No Smoking AUTO,0
     5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:md11_ovhd_lts_no_smoke_sw,number)'
     5109 Button changed: bRef=0, Joy=1 (J), Btn=18, Pressed
     5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 32=PJ,18,CPMD11 Seatbelt AUTO,0
     5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:md11_ovhd_lts_seat_belts_sw,number)'
     5109 Button changed: bRef=0, Joy=1 (J), Btn=24, Pressed
     5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 34=PJ,24,CPMD11 Landing Light Left OFF,0
     5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:md11_ovhd_lts_ldg_l_sw,number)'
     5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 35=PJ,24,CPMD11 Landing Light Right OFF,0
     5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:md11_ovhd_lts_ldg_r_sw,number)'
     5109 [Buttons.TFDi Design MD-11 GE Factory Rollout N111MD] 36=PJ,24,CPMD11 Taxi Light OFF,0
     5109  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:md11_ovhd_lts_nose_sw,number)'
...etc

are because you are trying to use  buttons assigned to presets before everything is loaded. You cannot use presets/lvars/hvars until the WAPI has established a connection and the initial set of lvars have been received, which is logged here:

Quote

    12047 -------------------- Starting everything now ----------------------
    12047 Starting WideServer now ...
    12047 Starting WAPI....
    12047   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.3) using connection -1
    12047   [INFO]: Connected to MSFS
    12109 Lvars received: 1584 L:vars & 0 H:vars now available

So you need to wait a short while (an additional 7 seconds or so) after the aircraft is loaded before you try and operate it via FSUIPC7 assignments to presets.

John

Posted

Try the attached version, 7.4.12d. Add the following to the [General] section of your FSUIPC7.ini file:
     MaxCustomControlNumber=96323

John

FSUIPC7.exe

P.S. As your question/issue is with FSUIPC7, please use the sub-forum dedicated to FSUIPC7 / MSFS for such posts. I will move your post.

Posted

Hello John,

The numbers I posted were for the log file lines.

thanks for the post. yes sorry wrong forum. I will check it out tomorrow. 

Cheers,

 

Xander

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
×
×
  • 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.