Announcement

Collapse
No announcement yet.

Cougar and TSUBA....no movement in DCS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Cougar and TSUBA....no movement in DCS

    Hello folks, I just set up my Cougar throttle using TUSBA and Win10 Pro.

    Windows sees the TUSBA just fine. In windows controls, all the buttons and knobs and axis are recognized just fine.

    I setup and calibrated everything just fine in the TSUBA software suite.

    Now when I go into DCS and fire up the F16, the throttle doesn't work at all. The sim won't even recognize the throttle moving. I have rebooted, tried running f16 again...no go.

    Do I haver to have a profile loaded in order for this to work. I felt that since everything was working in Win10 and TSUBA...I didn't need anything special.

    Also, DCS does recognize I have the TSUBA installed. It also shows the Axis assignments on the TSUBA. am I missing a step somewhere.

    Thanks for any assistance you can offer.
    David
    Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
    NVIDIA Driver:430.64

    OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

    Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

    VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
    SteamVR V1.1.18

    #2
    EDIT Follow-up. The TQS works fine in FS2020 and P3dv5. It jsut won't function in DCS. Again, Am I missing something simple here?

    I also rebooted again, and switched the TSUBA to a different USB port. I know it's working because it worked in the above sims.

    Thanks
    David
    Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
    NVIDIA Driver:430.64

    OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

    Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

    VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
    SteamVR V1.1.18

    Comment


      #3
      Probable what you are missing is assign TQS axes and buttons in DCS controls (for F-16 or a any other plane). The "auto-assignment" is useless.

      Comment


        #4
        Ok Thank You. I'll go ahead and reassign everything again.
        David
        Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
        NVIDIA Driver:430.64

        OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

        Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

        VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
        SteamVR V1.1.18

        Comment


          #5
          Well this is just too weird. i re-assigned all the axis's and buttons on the TSUBA.

          Nothing functions in the sim. The Cougar throttle works on all my other sims just fine.

          Very perplexing for me. Oh well gave it my best shot.

          Thanks for the suggestions. Guess I should have saved my money re TSUBA.

          Seemed like everyone using it was doing OK. Hence my purchase.
          Oh well. Life goes on.
          David
          Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
          NVIDIA Driver:430.64

          OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

          Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

          VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
          SteamVR V1.1.18

          Comment


            #6
            Originally posted by dwbarnett View Post
            Nothing functions in the sim. The Cougar throttle works on all my other sims just fine.
            If it works on the other sims, then we can discard a hardware problem ... must be some config on dcs issue. Can you attach your dcs.log to take a look at it?
            For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra
            For Gaming: 34" Monitor - Ryzen 1500X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Windows 10 Pro - Thrustmaster HOTAS Cougar - Oculus Rift CV1
            Mobile: iPad Pro 12.9" of 256 GB

            Comment


              #7
              Hi Rudel, here is my dcs.log. Thank You for your help.

              dcs.log Hope I did this right. Never attached anything before.

              David
              Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
              NVIDIA Driver:430.64

              OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

              Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

              VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
              SteamVR V1.1.18

              Comment


                #8
                Originally posted by dwbarnett View Post
                Hi Rudel, here is my dcs.log....
                Hi,

                Your log shows that dcs detects correctly your tusba devices:

                INPUT: Device [Keyboard] created deviceId = -1
                INPUT: Device [RS_TUSBA_R2 {EBB23F40-019E-11eb-8002-444553540000}] created deviceId = -1
                INPUT: Joystick created[RS_TUSBA_R2 {EBB23F40-019E-11eb-8002-444553540000}], ForceFeedBack: no
                INPUT: Device [Mouse] created deviceId = -1

                Can you take a screenshot of dcs controls window? It should have 4 columns: keyboard, mouse, and the two tusba devices.
                For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra
                For Gaming: 34" Monitor - Ryzen 1500X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Windows 10 Pro - Thrustmaster HOTAS Cougar - Oculus Rift CV1
                Mobile: iPad Pro 12.9" of 256 GB

                Comment


                  #9
                  Hello Rudel, that is interesting the TUSBA is showing a joystick too. I don't have one connected at all. I just have the throttle connected at this time.

                  I just show one TUSBA_R2 device on my controls page. I have KEYBOARD,TUSBA_R2,MOUSE.
                  That is all on my CONTROLS page.

                  I wonder if the joystick being in there is conflicting somehow? I'll try and delete the joystick out of the profile, see if that works.

                  Were would that file be located? Or can I edit it at all? Is there perhaps something in the RS_HID software, that may be causing the joystick to read? Even though nothing is hooked up.

                  IE after running the software, it created that entry in TSUBA_R2. The other issue I find weird, when setting up my throttle in RS_HID...when I calibrate, the numbers start high at MIN and go to 0 at MAX. I use the INV setting to change that direction.

                  However, I checked my flightsim(P3Dv5) with the inv setting....it is inversed in the sim too.
                  IE when I loaded the plane, the throttle was already MAX with the actual hardware throttle at MIN position.

                  I changed it back by turning off inv for the throttle. When trying flightsim(P3dv5) again, everything moved in the appropriate direction.

                  Finally, I noticed when setting up my axis in DCS, when I moved the throttle from MIN to MAX, I got several different axis readings.

                  IE First I got axis JOY_RY, then as I moved forward, it switched to SLIDER_1, then continuing to move forward it showed SLIDER_2...then finally at MAX it read JOY_RZ.

                  I don't have a clue what is going on with the throttle. I know it works fine on my other sims, but DCS doesn't like it at all. Any thought appreciated.

                  David
                  Last edited by dwbarnett; 09-29-2020, 02:32 PM. Reason: clarify what flightsim referred too
                  Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
                  NVIDIA Driver:430.64

                  OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

                  Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

                  VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
                  SteamVR V1.1.18

                  Comment


                    #10
                    Originally posted by dwbarnett View Post
                    I just show one TUSBA_R2 device on my controls page. I have KEYBOARD,TUSBA_R2,MOUSE.
                    That is all on my CONTROLS page.
                    Yes, I was confused by the log, seems that DCS first detects the usb device and afterwards it identifies it as a joystick.

                    I wonder if the joystick being in there is conflicting somehow?
                    It should not conflict, as DCS can handle several joysticks simultaneously.

                    Finally, I noticed when setting up my axis in DCS, when I moved the throttle from MIN to MAX, I got several different axis readings.

                    IE First I got axis JOY_RY, then as I moved forward, it switched to SLIDER_1, then continuing to move forward it showed SLIDER_2...then finally at MAX it read JOY_RZ.
                    That is really weird, as the Cougar throttle handles the throttle lever with a single potentiometer. The Cougar has 3 axes in total: throttle, range and antenna, perhaps you should call the TUSBA dealer and ask them for support, as it seems to be a bad-wiring issue.

                    Best regards,

                    Eduardo
                    For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra
                    For Gaming: 34" Monitor - Ryzen 1500X - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Windows 10 Pro - Thrustmaster HOTAS Cougar - Oculus Rift CV1
                    Mobile: iPad Pro 12.9" of 256 GB

                    Comment


                      #11
                      Tusba adds many axes to your throttle and they are needed if you want to implement something like idle/cut off and AB detents
                      If I remember it correctly the one you have to select is RY I am not at the computer now.
                      Also make sure when you start your flight your throttle is not in the cutoff position.
                      If your throttle is in the cutoff position and you haven’t set it to come off from that position it will not move.
                      A good way to check that is to start inflight.
                      So select axis axis RY and start inflight and see if it moves

                      Comment


                        #12
                        Hi< I had these issues setting mine up as well. Look in the RS software, the TUSBA adds another axis, which you need to delete. Not at my sim PC for a few days so cant give you exact help, and this was several months back so its not 100% clear in my head....

                        There is a guy on here called Supmua, who really knows the RS software and all this stuff inside out, he may be able to help if you cant find it.....
                        System specs: Scan 3XS i9 9900K @5ghz, 32GB Corsair veng DDR4 2666, EVGA GTX 2080ti Win 10. Reverb G2 on order , 40 inch 4K Phillips monitor. Real simulator FSSB R3 with F-16 SGRH grip and warthog with RS F-18 grip, plus Cubesim TM MFD's, Tir5. Winwing F-18 throttle, Tek creations UFC, panels. Cougar throttle & TUSBA, plus ICP for the Viper. MFG crosswind rudders. Jet seat and butt kicker..

                        Comment


                          #13
                          OK, making progress. I found the manual for the TUSBA...it's a lot more detailed than the vid. I just set up a min and max to experiment.

                          Before I thought I had put an idle detent in the throttle....hence moving it from min to idle..nothing happened.

                          Well, this time....I hit the R-SHIFT HOME key, this moved the throttle out of the cutoff position...I had thought the idel would do the same as the warthog idle...I was mistaken.

                          Once the throttle moved out of cutoff....everything moved just fine!..yay.
                          Throttle works OK/ Don't know about the antenna etc...will find out later as I do tutorials.

                          OK, moving forward. Thanks everyone for your input. Appreciated.
                          David
                          Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz OC 4.5GHz,G.SkillDDR4-3200,X299 AORUS Ultra Gaming-CF,Samsung SSD 860 PRO 512GB,Samsung SSD 850 EVO 1TB,WDC WD1002FAEX-00Z3A0,WDC WD3003FZEX-00Z4SA0,NVIDIA GeForce RTX 2080 Ti(Watercooled AORUS 11GB),H100i Cooler.
                          NVIDIA Driver:430.64

                          OS:Microsoft Windows 10 (10.0) Professional 64-bit (Build 17763)

                          Periphials: TM Warthog A10 HOTAS/Throttle,CH Rudder Pedals.

                          VRimax 5K+,PiTools V1.0.1.129,HMD Firmware V2.1.255.212,
                          SteamVR V1.1.18

                          Comment

                          Working...
                          X