Jump to content

fixing sticktion problem has created another issue - TN Warthog Hotas


Recommended Posts

Posted

hi guys, after stripping the joystick base down, sanding, greasing and all that stuff, i began reassembling it.  when i just put the spring over the gimble and pushed it down to simulate the top plate holding the spring down, the gimble became very stiff to move, way way more stiff than when i started.  its so stiff that its virtually unusable.  i fully reassembled it, problem persisted.  i ended up getting a virpil base as i could not fix it, i have decided to have another go at fixing it, as hardware in the same device from different manufacturers makes the device unrecognisable to the auto button allocations functionality.  hope someone can help, i have poured hours of my life into this black hole with no solution in sight.

Posted (edited)
6 hours ago, treasure said:

hi guys, after stripping the joystick base down, sanding, greasing and all that stuff, i began reassembling it.  when i just put the spring over the gimble and pushed it down to simulate the top plate holding the spring down, the gimble became very stiff to move, way way more stiff than when i started.  its so stiff that its virtually unusable.  i fully reassembled it, problem persisted.  i ended up getting a virpil base as i could not fix it, i have decided to have another go at fixing it, as hardware in the same device from different manufacturers makes the device unrecognisable to the auto button allocations functionality.  hope someone can help, i have poured hours of my life into this black hole with no solution in sight.

 

If you have the Virpil WarBrd Base it's quite simple to have Win10 recognize it as a TM HOTAS WARTHOG Joystick and even TARGET will not know the difference. You use the VirPil Config Tool to load the stick, change the Virpil PID\VID's to be what the TM stick was, rename it, save and done - TM Stick is VID - 0x044F, PID - 0x0402.  I have that setup and use the TARGET software to run a DX128 script which then assigns a DX# to every switch\hat\button on the |Warthog Throttle. Then simply assign the key bindings in the sim. 

Edited by GaryR

GIGABYTE X870E AORUS Elite WIFI7, Thermaltake 1200w PS \AMD Ryzen 7 9800X3D - Corsair iCue Titan Liquid CPU cooler \ 64GB G.Skill Z5 DDR5 \ SBlasterX G6 \ 4TB NvMe M.2 Boot Drive \ Zotac GeForce RTX 4090 Trinity 24GB - Nvidia 576.88 drivers \ 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz Gsync \ Win11 Pro Ver. 24H2 - Build 26100.4652 \ TIR 5 \ Warthog HOTAS  with VirPil stick base \ MFG V3 Pedals \ TM MFDs  on 2 8" Lilliputs \ Simgears ICP \ Varjo XR-3 VR

Posted
8 hours ago, GaryR said:

 

If you have the Virpil WarBrd Base it's quite simple to have Win10 recognize it as a TM HOTAS WARTHOG Joystick and even TARGET will not know the difference. You use the VirPil Config Tool to load the stick, change the Virpil PID\VID's to be what the TM stick was, rename it, save and done - TM Stick is VID - 0x044F, PID - 0x0402.  I have that setup and use the TARGET software to run a DX128 script.

 

Same here, works nice.

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

  • 3 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...