Jump to content

ccb777

Members
 View Profile  See their activity

  • Content Count

    104

  • Donations

    $10.00 

  • Joined

  • Last visited

Posts posted by ccb777

  10. Posted

    Thanks for the reply.I seem to somehow have everything working.The throttle quadrants were reversed.Would this have anything to do with which USB ports I plugged them into?Just curious.I just switched them physically on my real desktop.Thanks for the info which I will save for future reference.Ron

    Don't know. I tried to recreate this myself with two controllers of the same type. Didn't bother them.

     

    Anyway, I'm pleased you're up and running.

     

    Regards,

    Chris.

  11. Posted

    Vic is correct.

    I just recently did this and and it worked a treat.

    If you have

    [JoyNames]
    AutoAssignLetters=Yes

    It should be pretty stright forward.

    As Vic mentioned, there is now way the the system assingned GUID's will be the same.

    Briefley what I did was copy all the sections from my old FSUIPC4.INI file EXCEPT the [JoyNames] section, we need the new GUID's, into the new FSUIPC4.INI file.

    Then I had to adjust the letters to match the rest of the file.

    For example:

    This is from the .ini file from the new install of FSUIPC4
    [JoyNames]
    AutoAssignLetters=Yes
    0=Saitek Pro Flight Rudder Pedals
    0.GUID={56D2A0C0-3781-11E3-8002-444553540000}
    1=Saitek Pro Flight Yoke
    1.GUID={56D2A0C0-3781-11E3-8003-444553540000}
    2=BU0836X Interface
    2.GUID={8C0259C0-3781-11E3-8001-444553540000}
    3=BU0836X Interface
    3.GUID={9F9D1E70-3781-11E3-8002-444553540000}
    A=Saitek Pro Flight Rudder Pedals
    A.GUID={56D2A0C0-3781-11E3-8002-444553540000}
    B=Saitek Pro Flight Yoke
    B.GUID={56D2A0C0-3781-11E3-8003-444553540000}
    C=BU0836X Interface
    C.GUID={8C0259C0-3781-11E3-8001-444553540000}
    D=BU0836X Interface
    D.GUID={9F9D1E70-3781-11E3-8002-444553540000}
     
    I had to change it thus. (Spot the difference.)
    [JoyNames]
    AutoAssignLetters=Yes
    0=Saitek Pro Flight Rudder Pedals
    0.GUID={56D2A0C0-3781-11E3-8002-444553540000}
    1=Saitek Pro Flight Yoke
    1.GUID={56D2A0C0-3781-11E3-8003-444553540000}
    2=BU0836X Interface
    2.GUID={8C0259C0-3781-11E3-8001-444553540000}
    3=BU0836X Interface
    3.GUID={9F9D1E70-3781-11E3-8002-444553540000}
    C=Saitek Pro Flight Rudder Pedals
    C.GUID={56D2A0C0-3781-11E3-8002-444553540000}
    B=Saitek Pro Flight Yoke
    B.GUID={56D2A0C0-3781-11E3-8003-444553540000}
    D=BU0836X Interface
    D.GUID={8C0259C0-3781-11E3-8001-444553540000}
    A=BU0836X Interface
    A.GUID={9F9D1E70-3781-11E3-8002-444553540000}
     
    As you can see, I have four controlers, Saitek Rudders, Saitek Yoke and two BU0836X cards.

    If you look at the [buttons] section,(below), it's not too hard to figure out which controler needs which letter.

    (Make sure you change the letterd for both the name and the GUID together. Don't mix them up, and as usual, make copies of everything before you start so if you do make a mistake you can go back to the begining.)

    As you can see in the sample below...

    30=RB,32,C65734,0 ;    Pan_Up

    The first letter after the '=' sign in this case 'R' tells us 'Repeat'. This could also be: 'P', 'Pulse'; 'H', 'Hold' or 'U' (Un)Pulse'

    The next letter, 'B', refers to device 'B' (B=Saitek Pro Flight Yoke)

    and

    50=PA,0,C66056,0 ;       Pannel Lights On

    Here the 'A' referes to device 'A' (A=BU0836X Interface)


    [buttons]
    .
    .
    .
    !29=;
    !29=;        ---------- POV Hat switch ----------
    !29=;
    30=RB,32,C65734,0 ;    Pan_Up
    31=UB,32,C66416,-1 ;    Pan_View -1
    32=RB,33,C65856,0 ;    Pan_Right_Up
    33=UB,33,C66416,-1 ;    Pan_View -1
    34=RB,34,C65672,0 ;    Pan_Right
    35=UB,34,C66416,0 ;    Pan_View -1
    36=RB,35,C65857,0 ;    Pan_Right_Down
    37=UB,35,C66416,-1 ;    Pan_View -1
    38=RB,36,C65735,0 ;    Pan_DOwn
    39=UB,36,C66416,-1 ;    Pan_View -1
    40=RB,37,C65855,0 ;    Pan_Left_Down
    41=UB,37,C66416,-1 ;    Pan_View -1
    42=RB,38,C65671,0 ;    Pan_Left
    43=UB,38,C66416,-1 ;    Pan_View -1
    44=RB,39,C65854,0 ;    Pan_Left_Up
    45=UB,39,C66416,-1 ;    Pan_View -1
    !46=;
    !47=;        ---------- Electronics Pannel ----------
    !48=;
    50=PA,0,C66056,0 ;       Pannel Lights On
    51=UA,0,C66057,0 ;       Pannel Lights Off
    52=PA,1,C66363,0 ;       Toggle Alternator 1
    53=UA,1,C66363,0 ;       Toggle Alternator 1
    54=PA,2,Cx01003102,x01 ; Battery On  (Offset Byte Set)
    55=UA,2,Cx01003102,x00 ; Battery Off (Offset Byte Set)
    56=PA,3,C66364,0 ;       Toggle Alternator 2
    57=UA,3,C66364,0 ;       Toggle Alternator 2
    58=PA,4,C66340,0 ;       Toggle Elect Fuel Pump 1
    59=UA,4,C66340,0 ;       Toggle Elect Fuel Pump 1
    60=PA,5,C66341,0 ;       Toggle Elect Fuel Pump 2
    61=UA,5,C66341,0 ;       Toggle Elect Fuel Pump 2
    62=PA,6,C66072,0 ;       Pitot Heat On
    63=UA,6,C66073,0 ;       Pitot Heat Off
    64=PA,7,K72,8 ;          'H' Carb Heat On (Toggle)
    65=UA,7,K72,8 ;          'H' Carb Heat Off (Toggle)


    Hope this helps and is not too confusing,
    Chris.

  12. Posted

    I try the macros so many time and i delete the FSUIPC & install it again so many times, but the MACROS which which i name it (FUEL 1 cut) not listed in the list of the control sent when button press, even release, and also even key press (in key assignment tab).

    What happen ? What i do, all the ways is close in my face ?

    Please any any thing that give me the right way to fix my problem ?

    Also what the name u give to the macros which you created (not the name of the macros click) to your PNDG747 ?

     

    If you are having difficulties creating Macros for FSUIPC I will suggest you try using Google to help you search for further assistance.

     

    I did a search for "fsuipc macro" and this came up first on the list.

     

     

    I'm sure there are many more examples like this out there.

     

    Good luck,

    Chris.

  15. Posted

    PMDG 737 ngx, but the essential aircrafts is PMDG MD11, LEVEL D767, AS A320 EX (until the fs labs a320 released), also the PMDG 747 & the amazing PMDG777.

    Of the aircraft you mention here, I only have experience with the PMDG 747 and the PMDG 737 NGX.

     

    I have described how to do what you require using the PMDG 747 and it works for that aircraft. To open the 2D pannel for the throttles to record the Macro, press <shift>8.

     

    For the PMDG 737 NGX, you can assign keystrokes.

     

    Open the FMC window (<shift> 3) and select...

     

    MENU > PMDG SETUP > OPTIONS > KEY COMMANDS > CONTROL STAND (Page 2/2)

     

    There you have ENGINE X IDLE and ENGINE X CUTOFF options. You can assign key strokes to these options and then have FSUIPC assign these keystrkes to buttons/switches.

     

    (Alternativley, the control numbers for these are <70320> and <70321>, using parameters 0 when button pressed & 1 when button released.)

     

    As for the other aircraft you list, I do not have them, therefor I cannot assist you with those.

     

    Chris.

  17. Posted

    The MACRO is a good choice, but i think it will be the fix if i use the keyboarf to assigning, but in my case i use the toggle switch (external device) not keyboard, so i don't think the MACRO will help.

     

    Hello again paul, what is the L VARS and how i can get it ?

    Who mentioned a keyboard? Not I.

     

    If I understand correctly from your original post. You want to control the Fuel Cutoff switches using toggle switches. This is exactly what I am doing.

     

    I use an FSUIPC Mouse Macro file to control the PMDG 747 FUEL CUTOFF switches using toggle switches on a six lever throttle quadrant which I built myself using a BU836x controler.

     

    I take it you have not used Macro with FSUIPC? It's worth having a go.

     

    Create Mouse Macro using FSUIPC.

     

    The Macro will just be a single mouse click on the FuelCutoff switch of your aircraft.

     

    The name you give the Macro will then appear in the list of Button + Switches -> Control sent when button pressed / released.

     

    Chris.

  19. Posted

    And if you left the RAM alone, the OS would not need to generate all of the unnecessary page faults to access redundant RAM masquerading as a dirve. A RAM Drive is a DRIVE, not RAM, just a rather quick one.

     

    All you end up doing is giving the system more work and the only thing you will achieve is to slow the system down.

     

    Chris.

  24. Posted

    It is 1:18 on a Friday Afternoon in New Zealand right now because we get to enjoy Friday before the rest of the world....The sun is shining, not a cloud in the sky, and soon our Pub's and Patio's will be filled with people getting off work for the weekend.....Cheers :drinks:

     

    You're also the first one back to work on Monday morning too. Mind you, I'm only a couple of hours behind you over here in the Western Ilse.

     

    Chris.

×
×
  • Create New...