Jump to content
The simFlight Network Forums

ShahafR

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by ShahafR

  1. On 1/31/2022 at 4:59 PM, John Dowson said:

    Once you have one assignment to the buttons - all three (left rotate to decrease, right rotate to increase, push to select), you comment-out those assignment lines in your FSUIPC6.ini file. You do this by inserting a semi-colon (;) after the index number of the assignment. After doing this, reload your assignments for this to take affect. This will then allow you to assign for the second function, HDG/TRK. Once you have assigned for that, again comment out those assignment lines in your ini file, reload your assignments, and assign the third function, ALTITUDE. Once all are assigned, go back to editing your ini and uncomment the previous assignments (i.e. remove the semi-colons you previously added). Your buttons are then programmed for all three functions.

    However, as you have multiple assignments on the same buttons, all will be sent at the same time. You then need to add a compound button condition, so that only the correct control is sent depending on the position of the selector switch.
    This is what is described in the Advanced User manual under Compound Button Conditions. Basically you add a C to the beginning of the assignment (to indicate that it is a compound assignment), then you need to add details of which button the assignment depends on, in the format (+j2,b2) which means that button b2 on joystick j2 must be "on" for the assignment to take effect. Your selector knob will have three buttons associated to it, with only one being active/on at any time.

    John

    Can you give me an example how it should look?

  2. I cannot seee any control like AP_ALT_VAR_INC here: 

    // MCP
    //
    #define    EVT_MCP_COURSE_SELECTOR_L                (THIRD_PARTY_EVENT_ID_MIN + 376)    
    #define    EVT_MCP_FD_SWITCH_L                        (THIRD_PARTY_EVENT_ID_MIN + 378)    
    #define    EVT_MCP_AT_ARM_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 380)    
    #define    EVT_MCP_N1_SWITCH                        (THIRD_PARTY_EVENT_ID_MIN + 381)    
    #define    EVT_MCP_SPEED_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 382)    
    #define    EVT_MCP_CO_SWITCH                        (THIRD_PARTY_EVENT_ID_MIN + 383)    
    #define    EVT_MCP_SPEED_SELECTOR                    (THIRD_PARTY_EVENT_ID_MIN + 384)    
    #define    EVT_MCP_VNAV_SWITCH                        (THIRD_PARTY_EVENT_ID_MIN + 386)    
    #define    EVT_MCP_SPD_INTV_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 387)
    #define    EVT_MCP_BANK_ANGLE_SELECTOR                (THIRD_PARTY_EVENT_ID_MIN + 389)    
    #define    EVT_MCP_HEADING_SELECTOR                (THIRD_PARTY_EVENT_ID_MIN + 390)
    #define    EVT_MCP_LVL_CHG_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 391)    
    #define    EVT_MCP_HDG_SEL_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 392)    
    #define    EVT_MCP_APP_SWITCH                        (THIRD_PARTY_EVENT_ID_MIN + 393)    
    #define    EVT_MCP_ALT_HOLD_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 394)    
    #define    EVT_MCP_VS_SWITCH                        (THIRD_PARTY_EVENT_ID_MIN + 395)    
    #define    EVT_MCP_VOR_LOC_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 396)    
    #define    EVT_MCP_LNAV_SWITCH                        (THIRD_PARTY_EVENT_ID_MIN + 397)
    #define    EVT_MCP_ALTITUDE_SELECTOR                (THIRD_PARTY_EVENT_ID_MIN + 400)    
    #define    EVT_MCP_VS_SELECTOR                        (THIRD_PARTY_EVENT_ID_MIN + 401)
    #define    EVT_MCP_CMD_A_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 402)
    #define    EVT_MCP_CMD_B_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 403)
    #define    EVT_MCP_CWS_A_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 404)
    #define    EVT_MCP_CWS_B_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 405)
    #define    EVT_MCP_DISENGAGE_BAR                    (THIRD_PARTY_EVENT_ID_MIN + 406)
    #define    EVT_MCP_FD_SWITCH_R                        (THIRD_PARTY_EVENT_ID_MIN + 407)    
    #define    EVT_MCP_COURSE_SELECTOR_R                (THIRD_PARTY_EVENT_ID_MIN + 409)    
    #define    EVT_MCP_ALT_INTV_SWITCH                    (THIRD_PARTY_EVENT_ID_MIN + 885)    

     

  3. 4 minutes ago, John Dowson said:

    Sorry but I have no idea what you mean... and DONT attach screenshots - explain what you are trying to do, what your issue is, an attach your FSUIPC log and ini files.

    If using the PMDG 737, be aware that many of the standard controls do not work. You need to use the custom controls provided by the PMDG SDK. See 

     

    John

    Thank you for the replay. I cannot understand from this toppic how to set my SEL bottom. my FSUIPC.ini controls are like this:

    [Buttons.PMDG737]
    0=R1,4,C65966,0     -{THROTTLE1_DECR}-
    1=U1,4,C65967,0     -{THROTTLE1_CUT}-
    2=R1,5,C65971,0     -{THROTTLE2_DECR}-
    3=U1,5,C65972,0     -{THROTTLE2_CUT}-
    34=P2,0,C65792,1     -{AUTOPILOT_ON}-
    35=U2,0,C65791,0     -{AUTOPILOT_OFF}-
    36=P2,17,C66079,0     -{GEAR_UP}-
    37=U2,17,C66080,0     -{GEAR_DOWN}-
    38=P1,15,C65892,0     -{AP_ALT_VAR_INC}-
    41=R1,14,C65893,0     -{AP_ALT_VAR_DEC}-
     

  4. On 1/30/2022 at 2:21 PM, John Dowson said:

    So, the 3-position button should indicate what the middle SEL button does. So, you should program the SEL button for one function, eg. for altitude you would assign the left/right buttons to Ap Alt Var Inc/Dec. Then, comment out these assignments, and then assign to the second function, HDG/TRK, by assigning to the Heading Bug Inc/Dec controls. Again, comment out these assignments when done, and then assign to the third function, IAS/Mach, by assigning to Ap Spd Var Inc/Dec. Once you have assigned all three, you can edit your FSUIPC ini file to add a Compound Button Condition on those assignments to the state/position of the 3-position button. See the Advanced User Guide on how to do this.

    The controls I mentioned in the above are the default P3D controls for these functions. These may not work in all aircraft or the aircraft that you are using (you do not say!). It is up to you to determine what controls should be used for each function. If you are not sure, you can operate each function in the aircraft UI and see what events are logged - turn on logging for Events in FSUIPC and open the logging console and you can see what events are used when you activate these functions.

    John

    Hay John,

    When i try to assign seperatly like you wrote, it makes nothing in the sim. Do you have any idia why?

    WhatsApp Image 2022-05-12 at 19.56.54.jpeg

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