ramazoti Posted August 9, 2016 Posted August 9, 2016 Hallo Guys, i have the Hotas warthug .. the slew hat i made it with the Throttel mouse hat ,, before it was too slow .. after last update its too fast that i can't lock any targets with it.?? dont under stand what happend?? any help will be appriciated thanx Ram Geforce GTX 970 Inter Core I7 4790 CPU @ 4.00GHz 16.00 GB RAM
Chrinik Posted August 10, 2016 Posted August 10, 2016 Isn´t that an axis? Can´t you play around with the Axis settings to make them less responsive? [sIGPIC][/sIGPIC] GCI: "Control to SEAD: Enemy SAM site 190 for 30, cleared to engage" Striker: "Copy, say Altitude?" GCI: "....Deck....it´s a SAM site..." Striker: "Oh...." Fighter: "Yeah, those pesky russian build, baloon based SAMs." -Red-Lyfe Best way to troll DCS community, make an F-16A, see how dedicated the fans really are :thumbup:
Maulkin Posted August 10, 2016 Posted August 10, 2016 I thought there was a bug where changing the response curve would cause it to stop working completely. Sent from my SM-G935W8 using Tapatalk --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
TheSnark Posted August 10, 2016 Posted August 10, 2016 In the previous patch the TDC pipper worked fine, but in the current 1.5 version it has become insanely quick. Is this a bug or a permanent feature? If so I know if I need to change my curves.
Howler4 Posted August 12, 2016 Posted August 12, 2016 I had an issue with the TDC last night where it wouldn't slew with the axis I had set up (CH Throttle side stick). I checked the axis assignments and they were correct, and my curves are the same as before when the TDC slewing worked. I was able to use " , . / ;" to move the TDC but not my assigned axis. Everything else in the pit seemed to work fine.
TheSnark Posted August 12, 2016 Posted August 12, 2016 I think this is in the bug list isn't it? Something got screwed up in the last update that makes the TDC act almost as if it's a binary input, ignoring the initial range of the axis that is being used.
Wright_GR1 Posted August 12, 2016 Posted August 12, 2016 Seeing as it looks like we wont be getting a patch today a good fix for now is Y saturation at about 70%
Frederf Posted August 12, 2016 Posted August 12, 2016 TDC axes have always been binary input. The OA binaries were mistakenly used instead of the more current Release binaries last Release update along with all the other less-good behaviors. Perhaps the super-fast TDC axis control is groundwork for proportional control.
TheSnark Posted August 12, 2016 Posted August 12, 2016 I do hope so, I've given up on using the Hotas Cougar cursor for it, even with saturation it's impossible to gain a lock. I just use the keyboard.
Recommended Posts