treasure Posted July 25, 2021 Share Posted July 25, 2021 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. Link to comment Share on other sites More sharing options...
GPatricks Posted July 25, 2021 Share Posted July 25, 2021 (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 July 25, 2021 by GaryR Asus Z790-PLUS D4, Corsair 1000X PS / Intel i9-13900KF @5.8Gz - Corsair H150i Liquid CPU cooler, 64GB Corsair Vengeance DDR4 @3192mhz / 2TB M.2 NvMe Boot Drive (DCS World Beta installed here), 1TB M.2 Data drive, 1TB WD SATA drive, Zotac Gaming GeForce RTX 4090 Trinity 24GB - Nvidia 552.12 driver / 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz / Win11 Pro Ver. 23H2 - Build 22631.3447 TIR 5, TM Warthog HOTAS\VirPil stick base, MFG V3 Crosswind Pedals, TM MFDs on 2 8" Lilliputs/ Simgears ICP / Varjo Aero VR Link to comment Share on other sites More sharing options...
Lange_666 Posted July 25, 2021 Share Posted July 25, 2021 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 combat pedals, TrackIR4, Rift-S. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance! Link to comment Share on other sites More sharing options...
treasure Posted August 15, 2021 Author Share Posted August 15, 2021 nice, i will give it a go Link to comment Share on other sites More sharing options...
Recommended Posts