Gliptal Posted April 28, 2016 Posted April 28, 2016 The TDC stops working whenever you set custom curves in the axis keybinds. The only way to make it work again is to clear the binding and rebind the axis.
Maulkin Posted April 28, 2016 Posted April 28, 2016 I have this problem as well. Makes it difficult to 'tone down' the speed of the TDC movement like I do with the F-15C --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
PiedDroit Posted April 28, 2016 Posted April 28, 2016 I think TDC currently only moves if in the upper 50% of the curve, so if you try to tone it down it doesn't move because your values are below the threshold. The bug I'm talking about is already reported. I didn't try in latest update though.
Gliptal Posted April 28, 2016 Author Posted April 28, 2016 I think TDC currently only moves if in the upper 50% of the curve, so if you try to tone it down it doesn't move because your values are below the threshold. The bug I'm talking about is already reported. I didn't try in latest update though.Good catch, I'll see if that does the trick tomorrow.
PiedDroit Posted April 28, 2016 Posted April 28, 2016 (edited) Good catch, I'll see if that does the trick tomorrow. I just checked, looks like it's the same threshold bug, tuning it back to normal curve brings it back. Problem is, when that threshold is passed, it goes very fast, there's no way to make it slower. Try vertical axis with saturation Y = 60, it will start moving only at max value. EDIT actually, it's possible to tune it despite of the threshold, I tried this for vertical: Deadzone 0 Saturation X and Y both 100 Curve 0 Invert User curve 50 to 100 by increments of 5 Edited April 28, 2016 by PiedDroit
BJack Posted September 3, 2016 Posted September 3, 2016 Problem still exists. Is there another solution to solve this problem? The tricks discribed above are not working out for me. Any axis tune in both X and Y saturation on the X axis or Y axis will make the slew getting stuck. The defeault slew is set at 100 saturation which is way to fast, can't lock up any targets with it. Because of this reason I will not fly this beautiful plane in any BVR missions, which is a big disapointment for me.
Azrayen Posted September 3, 2016 Posted September 3, 2016 Razbam said they're aware, but other items have priority in the bug-fix process.
Shadow_1stVFW Posted September 3, 2016 Posted September 3, 2016 From Zeus Folks, we are aware of the problem. We have other stuff with higher priority that must be dealt with first. We will check this issue in due time. In the mean time, you can map the TDC slew to buttons to make it useable. Sent from my SAMSUNG-SM-G900A using Tapatalk Aurora R7 || i7K 8700K || 2TB 7200RPM SATA 6Gb/s || 2TB M.2 PCIe x4 SSD || GTX 1080 Ti with 11GB GDDR5X || Windows 10 Pro || 32GB Dual Channel DDR4 at 2667MHz || Virpil Warbird Base || Virpil T-50 Stick || Virpil MT-50 Throttle || Thrustmaster TPR Pedals || Oculus Rift
PVIBert Posted September 22, 2016 Posted September 22, 2016 From Zeus Folks, we are aware of the problem. We have other stuff with higher priority that must be dealt with first. We will check this issue in due time. In the mean time, you can map the TDC slew to buttons to make it useable. Sent from my SAMSUNG-SM-G900A using Tapatalk Not working at all for me. Ministick by far too fast. Buttons by far too slow. Is there a way to master at least the buttons speed waiting for the Ministick patch? I have the Hotas Warthog. Thanks.
Recommended Posts