Ant0ine

Welcome. Similar post here. My response is the #4.

We can indeed go from GUI to SE. Clic on VIEW SCRIPT then copy past the whole in a new Target Script Editor - script.

Ooh I didn't know/remember about that one.:thumbup:

https://www.digitalcombatsimulator.com/en/downloads/documentation/controller_walk_through/ I consider curvature to be like a bandage.. They hide the problem without fixing it. But to really fix the Warthog problem (Shorter throw than IRL + huge neutral point bump and combined axes + .. :joystick:) you would need an extension and a modded centering system.. I had a 15cm extension on mine and I did the "stiction fix", using Nyogel 767A. Problem is that I had to do it regularily and it didn't removed the center bump at all. To workaround that I used to trim nose down a little so that I had to pull on the stick to fly straight and be away of the neutral point bump. Aerobatic/formation pilot does the same IRL. For plane with auto 1G trim like the F18 I would have had to use Target Script Editor to "off-trim" it.

For your Tartarus : The one I have to turn off is named 'USB Input Device'. I use Tartarus V2. To blacklist controller (Joystick, throttle.. All direct input device I think), or rather to whitelist them in fact, I use HID Guardian via WhiteKnight. No idea how to hide the Xbox Controller.

What do you think about the SCG PRO (Kosmosima)? It have similar (and more) button layout than the A10 grip. So I guess no problem to map the Hornet on it. And it have twist. Edit to add : The MCG PRO have even more, but no twist option yet. There is a twist adapter in the work.. No idea when when it will be available. Edit to add : Also if Hornet and Viper are your things.. Keep an eyes on WinWing Hotas (Twist module in option). Today they ship tester units. And they've said they'll work on a F16 hotas IIRC.

What is your budget?

Target need to be running, it will create a virtual controller with set parameters, and hide device included in the script. So in this case it would hide the Warthog stick.

Clic on the little arrow next to the axis name to expend its options.

https://srv0files.eagle.ru/dcs/manuals/DCS_World_Input_Controller_Walk_Through_EN.pdf

Cancel any calibration you've done with windows if possible. Then use the TM Warthog Throttle calibration tool below : https://www.dropbox.com/s/ca4sgzfrprayh42/Throttle%20Warthog%20Calibration%20%28V1.07%29.exe?dl=0

http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_User_Manual_ENG.pdf http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf

I don't like deadzone. Plus it reduce the usable throw which is already much shorter than IRL. And doing so make us less accurate.

+1. Must be activable/tunable independently on each axes.

Unlimited free.

I don't have the X56 nor any other Saitek/Logitech hotas so can't really help further. If I had one I would UnProgram as much button as possible. Edit to add : And look for a way to load that "UnProgrammed" profile by default/on StartUp. Then I would use Joystick Gremlin to do all kind advanced programmation. Including "mode/layer" and shift of course.

TL;DR Recently I wrote a guide explaining how to match our physical throttle detent(s) with virtual throttle detent(s). (To keep linearity and also to band-aid inaccuracy in throttle detent(s) and/or dual throttle mechanical linkage). I did that with my Warthog throttle and tried to make it match with the Hornet. No problem to match physical AB detent with virtual AB detent. However I learned about "InFlight Idle Stop" and so.. I had to do create two different curves. One with ground idle and the other with InFlight Idle. The game indeed replicate what's happening in the real Hornet. More info here. The problem is our physical throttle can't replicate that. At least not the "gaming" peripheral that most people use. So we end up with a pretty large deadzone when airborne. On my Warthog throttle it is about 17% of the Idle to Max AB range. (The whole axis range if calibrated normally). Could you please make that optional? A little option similar to the one we have to choose how to deal with AB detent would be awesome. I do not have much experience with jet myself but I've been told it is very common. I guess Hornet pilots wouldn't be the only one to benefit from this option. Thanks :)

Ok then if you do everything via the Logitech software I think you should solve your problem by turning OFF, or ON the latched option on your "mod selector". https://www.saitek.com/manuals/SST_Manual_En.pdf

I imagine the X56 selector switch is ON-OFF-ON and by default send continuous button press on ON Position. So in DCS you want to use "Modifiers" instead of "Switches". Modifier release when virtual button is released.

Virpil Warbrd or VKB Gunfighter for desktop usage. Virpil MongoosT-50CM2 or VKB Gunfighter if you plan to center mount it with extension. Note that to use the Gunfighter with your a Warthog grip you would need a Warthog adapter Rev.B which I think isn't available yet.

https://www.digitalcombatsimulator.com/en/downloads/documentation/controller_walk_through/ With gimbal as accurate as the one offered by Virpil or VKB, deadzone and curve shouldn't be needed. :unsure:

I would probably try to get throttle only. And save enough money for a VKB or Virpil base. My Warthog Hotas review here :

I edited the open post to add a fix to the "weight on the wheel = ON" mode deadzone.

I see a lot of people are having troubles to make their physical throttle detent(s) match with the virtual detent(s) of the machine(s) they are using. DCS do not give us an option to set our detent(s) point so.. Using DCS curve tool we’re limited.. Best we can do is stuff like this : Not only it isn’t accurate, but it also make the response non linear. With the help of Joystick Gremlin and its developer I found a way to make things cleaner. I’ll use my Warthog throttle with the default detent for this exemple. The detent is at about 66% of the Idle to max range according to DIVIEW. And I’ll try to make my throttle match with the DCS F18 throttle. First thing I notice is that I reach idle virtual throttle before reaching idle physical limit. Seems to be due to the fact the game automatically put the idle detent at ~17% of our throttle range. That reduce my usable throttle range and so my accuracy so let’s solve that. I reach minimal virtual when my physical is at ~83%. Edit : Seems to be normal. To solve that using Joystick Gremlin we have to reduce the Y saturation. Using the Input Viewer I note that 83% from DIVIEW reading is equal to 66% in Gremlin reading (Which goes from -100% to +100%). So I put the control point at 0.660 on Y. Note that we have to use Cubic Bezier Spline. Not needed to change saturation but will be needed later for the AB detent part. This problem is solved. We can do the same directly via DCS. By decreasing Y saturation to 83% : Let’s see how to match physical detent with virtual detent of the F18 now. To do that we need to determine the position of the virtual detent, so I turned on “AfterBurner detent” in game option so that my throttle is locked at MIL power. And here are the result (We must check Vjoy value because our saturation have been modified to solve the idle problem) : Result is 54%. And here are my physical detent position (This time we check the physical throttle value) : 29 and 34%. Difference is important by the way.. The detent (physically) isn’t accurate at all I can feel my left throttle detent being further.. So, now I can place the detent point on the curve : Then to make the curve linear we take the detent point bezier point and place them above minimum and max point, result is as below : I do the same for the other throttle : Good now we return to the option to turn off “AfterBurner Detent”. We’re done. If desired or needed (due to throttle linkage and/or detent inaccuracy as on my throttle) we could add a small deadzone just after the physical detent to ensure we do not active AfterBurner when we hit MIL quickly/hard. To do so we have to add a second point and place it a little bit to the left of our detent point, then we use the Bezier Point to make the curve linear before and after the two point, and also to make the curve between the two point flat, which is what make the deadzone. The detent point is at X-0.300 and the second point is at X-0.320. We don’t see it well cause deadzone is small so here is the idea : I hope this will help some people. And that ED will allow us to do that via their interface someday. Edit : Okay so I learned a bit more about Weight on wheel system of the Hornet thanks to this post, and realized there was more job to do! The curve done earlier is perfect for the "AIR Idle" and AB detent, while in the AIR. However when on the ground I noted the idle detent was wrong, and also a deadzone. To solve that I created two mode in Gremlin, one for WOW ON (weight on the wheel, so on ground or carrier..), the other for WOW OFF (airborne). Then on the WOW OFF mode I remapped my two throttle axes and made the response curve as explained earlier. On the WOW ON however, I had to modify the curve a little to cancel the deadzone.. Which is about 10% My "ground idle" match perfectly with my physical warthog idle detent. Now we have to find a convenient way to swap curve OnTheFly.. I'll use L_Alt+G until I start flying the Hornet seriously again and find a better way. WOW ON to WOW OFF WOW OFF to WOW ON

I would try to remap the jittering axis to a Vjoy thanks to Joystick Curve which have a noise filtering (Hysteresis?) feature. https://xedocproject.com/joystickcurves.html