Gate-5 Posted April 5, 2014 Posted April 5, 2014 I just had to redo my curve settings for the F15 in 1.2.8 and thought I'd share them. Hope someone can use this. 1
Home Fries Posted April 5, 2014 Posted April 5, 2014 I find that my cougar works with a straight throttle as long as the curve starts at my idle detent. The afterburner turns on and shuts off right when it's supposed to. -Home Fries My DCS Files and Skins My DCS TARGET Profile for Cougar or Warthog and MFDs F-14B LANTIRN Guide
Gate-5 Posted April 5, 2014 Author Posted April 5, 2014 I find that my cougar works with a straight throttle as long as the curve starts at my idle detent. The afterburner turns on and shuts off right when it's supposed to. Apparently different for every stick, I forgot to mention that my curve is for a Warthog.
Pyroflash Posted April 5, 2014 Posted April 5, 2014 My warthog hits 96% right on the detents with no curve. If you aim for the sky, you will never hit the ground.
Gate-5 Posted April 5, 2014 Author Posted April 5, 2014 My warthog hits 96% right on the detents with no curve. Really? Thats strange :unsure:. If I remove my curve from one channel it only gets to around 94.5-95. For my curve I checked the fuel flow, and adjusted it to be just below the point before it starts going up.
69iAFMike Posted April 5, 2014 Posted April 5, 2014 Thanks, I'm using it now :) I did hit 96% at the detent before (no idea why), but then it only got to 93% every flight. So the new curve helps.
Pyroflash Posted April 5, 2014 Posted April 5, 2014 Yeah, I lied, by the way. Turns out my HOTAS profile had curves set that I forgot about. If you aim for the sky, you will never hit the ground.
lxsapper Posted April 5, 2014 Posted April 5, 2014 DCS Needs a way to define your afterburn detent like falcon 4 has, period! A throttle axis has no business having curves whatsever!
PFunk1606688187 Posted April 5, 2014 Posted April 5, 2014 DCS Needs a way to define your afterburn detent like falcon 4 has, period! A throttle axis has no business having curves whatsever! ^ Warning: Nothing I say is automatically correct, even if I think it is.
Pyroflash Posted April 5, 2014 Posted April 5, 2014 DCS Needs a way to define your afterburn detent like falcon 4 has, period! A throttle axis has no business having curves whatsever! Agreed. I think that it is quite weird. If you aim for the sky, you will never hit the ground.
Cali Posted April 6, 2014 Posted April 6, 2014 DCS Needs a way to define your afterburn detent like falcon 4 has, period! A throttle axis has no business having curves whatsever! Can't believe this hasn't been done yet, it's only been about 10 years! i7-4820k @ 3.7, Windows 7 64-bit, 16GB 1866mhz EVGA GTX 970 2GB, 256GB SSD, 500GB WD, TM Warthog, TM Cougar MFD's, Saitek Combat Pedals, TrackIR 5, G15 keyboard, 55" 4K LED
lxsapper Posted April 6, 2014 Posted April 6, 2014 In all fairness I would settle for a simple lua edit for a simple .lua edit where you could define the percent (00.0%) of throttle axis to use as the MIL Power mark. I really doesn't have to be in the UI. Please ED.... Preaty please.....
lxsapper Posted April 18, 2014 Posted April 18, 2014 Ok I came up wtih my own solution for this. It's not the solution I wished for but since I have now converted to using TARGET (trackIR commands related). The TARGET manual states that the warthog throttle afterburner detent's enter afterburner region at 80% physical travel. I found this to be wrong. Although if you use a J Curve as described in the manual 80% physical to 95% directx output it will work because the real values will be roughly the same. The Real values are 66% physical travel from idle to afterburner detent and 78% directx output just short of engaging the afterburner on the F-15C on 1.2.8. I tested the SU-33 and it seems that however close to this values of 78% this plane at least uses a slighlty diferent value to engage the AB. Then I have another problem wich I don't know if it's common to all Warthogs but on mine the Left Throttle actually travels further before hitting the AB detent aprox 69% physical travel (just a couple on mm). My solution to all of this was using a custom curve on the Scripteditor in a way that instead of something looking like a J Curve I have something close to two Straight lines, giving me virtually linear response in the dry power region and then a diferent line with diferent sensibility but still linear for the AB region. I also put a small deadzone in the left throttle from 66 to 69% so that both throttles hit Full Mil when they are aligned but I can also not worry about pushing the left throttle all the way to it's detent. And here is the Script code for this: MapAxis(&Throttle, THR_RIGHT, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetCustomCurve(&Throttle, THR_RIGHT, LIST(0,0, 10,12, 20,24, 30,36, 40,48, 50,59, 60,71, 66,78, 70,81, 80,87, 90,94, 100,100)); MapAxis(&Throttle, THR_LEFT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetCustomCurve(&Throttle, THR_LEFT, LIST(0,0, 10,12, 20,24, 30,36, 40,48, 50,59, 60,71, 66,78, 69,78, 70,81, 80,87, 90,94, 100,100)); Note: That I altered the default TARGET assignment of DX axis names to the physical ones. So adapt to the circustances of your script.
JetBLASTER Posted April 21, 2014 Posted April 21, 2014 I just had to redo my curve settings for the F15 in 1.2.8 and thought I'd share them. Hope someone can use this. Tanks Gate5 I set up my TM Warthog with the curve the same yours and work beautiful . Now pull the throttle just to the end and I have 110 %.:thumbup: [sIGPIC][/sIGPIC] Intel® Core™ i7-6850 CPU@3.60GHz @4.068 Asus ROG STRIX X99 GAMING ATX Motherboard 64 bit operation System- RAM 32.0 GB Gigabyte GeForce GTX 1080 WindForce OC 8GB - Disk Drives KINGSTON SVP200S37A 1tb/WDC WD 10EZEX-00ZF5A0 - Samsung ssd 1tb 840 series. - 3 Samsung 27"SyncMaster 3D Game monitors - Windows 8.1 Pro - TM Hotas Warthog-Trackir5 pro-Saitek Rudder Pedals-Cougar MFD.
mytai01 Posted January 23, 2017 Posted January 23, 2017 Don't the DCS people realize they support Warthog Throttle, but didn't make a setting to define the detent from mil power to AB? They should fix this!!! Or, explain how to make it work... MS Win7 Pro x64, Intel i7-6700K 4.0Ghz, Corsair RAM 16Gb,EVGA GeForce GTX 1080 FTW GAMING ACX 3.0, w/ Adjustable RGB LED Graphics Card 08G-P4-6286-KR, Creative Labs SB X-FI Titanium Fatal1ty Champ PCIe Sound Card, Corsair Neutron XTI 1TB SSD, TM Warthog Throttle & Stick, TM TPR Pedels, Oculus Rift VR Headset CV1, Klipsch Promedia 4.1 Speakers...
Recommended Posts