NaOH1 Posted December 14, 2018 Share Posted December 14, 2018 I've been dealing with TM for close to a month with no fix. They keep telling me they're looking into it but can't figure it out. I have a new Warthog HOTAS. I have the AB detent installed. In DCS F-18 I physically touch the AB detent so I've reached 100% travel. In game I'm only reaching 93% power. If I go over the detent, AB works as normal and if I remove the detent it all works as normal. I've calibrated many times with no change. Up to a month ago I've been a CH guy so TM is new to me. Does anybody know what I can do to fix this issue? I'd like to use the detent. Below is the txt scrip that came with the calibration tool I downloaded here. /* Thrustmast A-10 Throttle Calibration Tool - Output/Configuration file. */ FW_Checksum = 0x0091F60E; // 00..02 SerialNum = 0x00303030; // 03..06 TestPrgStatus = 0x00; // 07 TrimCenDZ = 0x8D; // 18 Standard_DZ_SX = 0x10; // 20 Standard_DZ_SY = 0x10; // 21 Standard_DZ_T = 0x09; // 22 Standard_DZ_LT = 0x01; // 23 Standard_DZ_RT = 0x01; // 24 Idle_Btn_Start = 0x8DE2; // 26-27 Idle_Btn_Stop = 0x9BC5; // 28-29 Initial_Min_SX = 0x8000; // 30-31 Initial_Min_SY = 0x8000; // 32-33 Initial_Min_T = 0x5880; // 34-35 Initial_Min_LT = 0x076D; // 36-37 Initial_Min_RT = 0x068B; // 38-39 IdleSize_LT = 0x2A15; // 40-41 IdleSize_RT = 0x296D; // 42-43 MultShifts_SX = 0x07; // 44 MultShifts_SY = 0x07; // 45 MultShifts_T = 0x07; // 46 MultShifts_LT = 0x07; // 47 MultShifts_RT = 0x07; // 48 MultInit_SXP = 0xF3; // 50 MultInit_SXN = 0x90; // 51 MultInit_SYP = 0xBF; // 52 MultInit_SYN = 0xFB; // 53 MultInit_TP = 0x39; // 54 MultInit_TN = 0xDE; // 55 MultInit_LT = 0xB1; // 56 MultInit_RT = 0xB0; // 57 Center_Area = 0x1000; // 58-59 Center_Reduc = 0x04; // 60 Center_Shift = 0x03; // 61 Center_BM = 0x03; // 62 nIdle_Btn_Start_Ratio = 33; nIdle_Btn_Stop_Ratio = 120; Link to comment Share on other sites More sharing options...
Thermal Posted December 14, 2018 Share Posted December 14, 2018 There is no calibration process for the Warthog to match the physical AB detent location to the "logical" AB detent inside a generic game (AFAIK). You can probably apply a transform map to the throttle axis using Target to make that happen (this is the hard way). The easy way is, in DCS, adjust the curve of the throttle axis such that the physical detent matches the logical detent. From memory, with my Warthog it as around +11 (or -11) in DCS. Set and forget. To assist checking you have the right value, you hit CTRL-ENTER in flight and bring up the joystick overlay. This has the Hornet logical AB detent displayed. Tweak as needed. This has the added advantage of being Hornet specific, and would also work for say the Tomcat because the controller curves are aircraft specific, and you can set curve that works for each aircraft - hence no need to run a calibration for each aircraft for every flight. Link to comment Share on other sites More sharing options...
NaOH1 Posted December 14, 2018 Author Share Posted December 14, 2018 Thank you Thermal!!!!! You fixed it for me. Link to comment Share on other sites More sharing options...
Recommended Posts