Jump to content
The simFlight Network Forums

target11

Members
  • Posts

    95
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by target11

  1. I do not understand how you configure your button I assume a push button
    for me when i press the button i have
    5=RC,14,K113,8 -{Key press: F2}-
    when I release it I have
    6=UC,14,K112,8 -{Key press: F1}-
    the line numbers follow line 5 and 6

    YOU
    you press the button you have
    3=RA,4,K121,8 -{Key press: F10}-
    this line should start with 0 and not 3
    when you release the button you have
    16=UA,4,K120,8 -{Key press: F9}-
    this line should normally start with 1 and not 16
    so I don't know how to configure the button and where lines 0 1 and 2 have gone I understand that you can put any line number provided that it follows but that's weird

  2. I also had to configure the axes on efb and then press default to reset what I had done on the efb, I was sure that all had been set to zero in the efb, and then I configured the axes and button in fsuipc and nothing worked, well simply the configurations in the efb were not reset, so I put the ATR_Calib.cfg file in ATR_Calib_back.cfg , deleted my atr profile file, and I reconfigured my axes and buttons in fsuipc, I say in fsuipc, nothing in the efb and nothing in msfs2020

    • Like 1
  3. Good evening
    yes I understood the principle, you configure axes 1 and 2 on msfs2020, and the notches on the efb, so in this configuration you don't need fsuipc, and moreover you can configure the return axes on the same principle, so you do not need to reconfigure the axes on fsuipc, otherwise you will have a conflict or will not obtain the desired result, after if you use fsuipc for the buttons without configuring the axes there should be no problems . on the other hand if you have no notches and you want to configure the axes on idle a maximum like me then using fsuipc will be less complicated.

  4. Good morning
    however, setting the axes on fsuipc is very easy and user friendly, I'm far from an expert, but setting the axes with the ATR efb is anything but user friendly and setting the axes with msfs and the efb is an achievement

    but if you have a notch throttle like the Thrustmaster Airbus Throttle or other I understand the principle of configuring with msfs2020 and the efb of the atr

     

  5. Good evening
    in your fsuipc.ini in general at the line UseProfiles=Yes you must change the Yes to files and the profile folder will create this look at the beginning of my video, look carefully at the steps I do in the video, at some point I create a new ATR profile. the profiles you have in your fsuipc.ini file are automatically created. I prefer to create a separate file for each aircraft, maybe also make a video with all the steps you do on fsuipc.
    and i don't understand why you did this.

    ALSO to mention I removed the FSUIPC.key files so I basically run the FSUIPC as in unregistered and that allowed me to actually use both MSFS and FSUIPC for other stuff, where FSUIPC was not messing with my throttle axis, NOT an ideal solution, but will do for now, hopefully will get it worked out.

  6. Good morning
    I don't want to talk nonsense, but it seems to me that you don't have throttle axes set in the fsuipc.ini file at least not as I had mentioned
    3=FWD,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-
    4=AS,256,D,9,0,0,0 -{ DIRECT: Throttle1 }-

    [Axis]
    PollInterval=10
    RangeRepeatRate=10
    0=AR,256,D,23,0,0,0 -{ DIRECT: Flaps }-
    1=AU,256,D,22,0,0,0 -{ DIRECT: Spoilers }-
    2=AU,B,-8128,-6554,66066,0,66067,0 -{ DIRECT: SpoilersEntering=SPOILERS_ARM_ON, Leaving=SPOILERS_ARM_OFF }-
    3=FWD,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-
    4=AS,256,D,9,0,0,0 -{ DIRECT: Throttle1 }-
    the axes should not be set on the EFB but in fsuipc, let's say that's what I did otherwise john will have to look at this for more help

  7. Good evening

    for information on *1,+8192 see FSUIPC7 for Advanced Users page 41 here Additional parameters to scale input axis values

    for this
    3=AV,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
    4=AS,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-
    to try
    3=AV,256,F,67110,0,0,0,*1,+8192 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
    4=AS,256,F,67103,0,0,0,*1,+8192 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-

    ,*1,+8192 must be added manually
    if not working correctly instead of *1,+8192 try *0.9,+8192 or 0.8 or 0.7 until working correctly

  8. Good morning
    for a hotas warthog, when the hotas throttle is on idle, the throttles on the atr are on reverse to counter this, i.e. when the throttle is on idle and also on the atr, this is what I did.
    2=CZ,256,F,67110,0,0,0,*1,+8192 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
    3=CR,256,F,67103,0,0,0,*1,+8192 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-

    and for the reverse I have them configured on a button
    0=RC,6,K113,8 -{Key press: F2}-
    1=RC,7,K112,8 -{Key press: F1}-

    • Like 1
  9. Good morning,
    I wanted to know after installing GSX PRO, in exe.xml
    I had to manually add
      <Launch.Addon>
         <Disabled>False</Disabled>
         <ManualLoad>False</ManualLoad>
         <Name>FSUIPC7</Name>
         <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
         <CommandLine>-auto</CommandLine>
         <NewConsole>False</NewConsole>
       </Launch.Addon>
    these lines of code appear in "exe_backup_fsdt.xml" but disappeared in "exe.xml"
    in the fsuipc7 installation log there is the line
    C:\Users\Target\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml has been updated.
    so I assume that the lines are added but deleted when installing GSX PRO. Or it's me doing something wrong, which I often do.
    Sincerely

  10. Hello
    so on fsuipc 7.3.10 in fsuipc.ini the joystick assignments were
    [JoyNames]
    0=Flight Rudder Pedals
    0.GUID={13FDBA90-34E6-11EB-8005-444553540000}
    1=Joystick - HOTAS Warthog
    1.GUID={13FDBA90-34E6-11EB-8006-444553540000}
    2=Throttle - HOTAS Warthog
    2.GUID={13FDBA90-34E6-11EB-800A-444553540000}
    A=Flight Rudder Pedals
    A.GUID={13FDBA90-34E6-11EB-8005-444553540000}
    B=Joystick - HOTAS Warthog
    B.GUID={13FDBA90-34E6-11EB-8006-444553540000}
    C=Throttle - HOTAS Warthog
    C.GUID={13FDBA90-34E6-11EB-800A-444553540000}
    D=Logitech G13 Joystick
    D.GUID={96C6A660-4B9A-11EB-8003-444553540000}

    in version 7.3.16 they are
    [JoyNames]
    0=Flight Rudder Pedals
    0.GUID={3AE44B50-8D55-11ED-8001-444553540000}
    1=Logitech G13 Joystick
    1.GUID={3AE69540-8D55-11ED-8007-444553540000}
    2=Joystick - HOTAS Warthog
    2.GUID={3AE69540-8D55-11ED-8009-444553540000}
    3=Throttle - HOTAS Warthog
    3.GUID={3AE90640-8D55-11ED-800E-444553540000}
    A=Flight Rudder Pedals
    A.GUID={3AE44B50-8D55-11ED-8001-444553540000}
    B=Logitech G13 Joystick
    B.GUID={3AE69540-8D55-11ED-8007-444553540000}
    C=Joystick - HOTAS Warthog
    C.GUID={3AE69540-8D55-11ED-8009-444553540000}
    D=Throttle - HOTAS Warthog
    D.GUID={3AE90640-8D55-11ED-800E-444553540000}
    I had removed the G13 between the two versions, then I put it back
    why such a change I do not know.

    when I spoke of key in version 7.3.10 it was defined as such
    2=PB,8,K118,8 -{Key press: F7}-

    in version 7.3.16 they are defined as such
    2=PC,8,K118,8 -{Key press: F7}-
    so I just wanted to change 2=PB to 2=PC
    I just had to click on a button on the joystick to know the letter to change, it was simple

    same thing for axes in version 7.3.10
    0=BX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }-
    in version 7.3.16
    0=CX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }-
    I just had to move an axis to know which letter to change
    0=BX through 0=CX
    again I do not understand why these letters have changed.
    I wanted to keep it simple, but it became complicated.
    Again when I said close the program I did exit program so it was no longer in function, but when restarting FSUIPC it resumed the old assignment, I agree with you that makes no sense.
    I gave up, I'll watch it with my head rested.
    Have a good day

  11. Hello
    it does not matter I will manage to find a solution, it is very possible that I explain my problem badly, it's just that I added a peripheral, so fsuipc took care of it, so the axes (for the example for the keys it was the same thing) were for example before I added the peripheral
    [Axis]
    RangeRepeatRate=10
    0=BX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }-
    1=BY,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-
    2=CZ,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
    3=CR,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-
    4=CS,256,F,66382,0,0,0 -{ TO SIM: AXIS_SPOILER_SET }-
    after adding the device
    [Axis]
    RangeRepeatRate=10
    0=CX,256,F,65695,0,0,0 -{ TO SIM: AILERON_SET }-
    1=CY,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-
    2=DZ,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
    3=DR,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-
    4=DS,256,F,66382,0,0,0 -{ TO SIM: AXIS_SPOILER_SET }-
    so I manually changed BX to CX, BY to CY .....
    and I wanted to do the same thing with the keys, but the file is overwritten each time, so you told me to change the assignments then to open buttons&switch assignments to do reload all buttons to take into account the new assignments but the file crashes then I tried to press a button perform a keyboard key done ok and it works. But then I wondered why we couldn't change the key assignments manually, I tried I close fsuipc to open it again but it takes the same old assignments, and the file is overwritten again and saves the old assignments, but you tell me that it is impossible, which is logical, but which I do not understand, so I'll see if I find a solution, by the way it's a clean install of win 11 msfs2020 and fsuipc 7.3.16.
    Good day

  12. Hello, I understood, but I wonder why it is not enough to make the changes in the file, which is very simple, takes very little time, rather than assigning each key and key combination again, as much as deleting the file and redo it, so I don't understand this way of doing duplicate work when there is a simpler way. But it is obvious that I would not redo all my profile files too much work for nothing. Just put a question it resumes it's information or, if we can get around it it will be simpler
    Have a good day

  13. Hello because the definition of the keys have also changed because I added a device, for example the line on the old file was
    3=HB,6,K117,8 -{Key press: F6}-
    and I manually transform it into
    3=PC,6,K117,8 -{Key press: F6}-
    but as the file is overwritten each time, I will have to press each key and redefine the key combination.
    whereas if I could change directly in the file, save it, and do reload all buttons by taking the file without overwriting it would be easier.

  14. Hello
    I always do my aircraft profiles on a separate file. as I added a device, my key assignments changed. So I changed the key assignments manually in the file, and when I reload all buttons, the old assignments rewrite themselves in the file. For example the original line in the file is
    0=HC,6,K113,8 -{Key press: F2}-
    I change it in the file to
    0=HC,6,K113,8 -{Key press: F6}-
    I do reload all button, I open the profile file and I find the line in the file
    0=HC,6,K113,8 -{Key press: F2}-
    hence my question he will look for this information or, to change this on his own
    thank you for your reply

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