What's happened to the 'normal' files in joystick folder?

[imacken]

As with almost all modules, I find the senstivity on the TDC control on my HOTAS too high on the Harrier, so I usually edit the joystick lua files more to my liking. These files are always stored in the 'joystick' folders, e.g. C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-5E\Input\F-5E\joystick\Joystick - HOTAS Warthog.lua', etc.

There are none of these in the Harrier folder. Why is that?

[schurem]

They are in c:\users\you\saved games\DCS\config\input\

 

The ones you are looking at are the default settings. Any (file) edits you make there will get reverted on every patch for maximum annoyance. If you make the edits with the in-game UI, they will get saved in the above path and are immune from patch shenanigans.

[imacken]

Thanks but that is not what I mean. The files in your Saved Games folder are just the diff lua files where you have rebound. I am talking about the default files like the one I mentioned in the first post.

They are missing in the Harrier. However, they must be somewhere!

Normally, I make changes to the sensitivity of the TDC in the default files and then run it as mod in OvGME to avoid patch changes.

[imacken]

Actually, I can see that not all modules have got these default files, e.g. Viggen, so this is not unique to the Harrier.

I wonder where the default bindings are stored for the Warthog HOTAS then. I know there are some in the default.lua file, but all modules have that as well.

I'm a little confused by this.

[LeCuvier]

I have not seen default values for sensitivity in files like "Throttle - HOTAS Warthog.lua", except in the A-10C. That module has these code lines:

{combos = {{key = 'JOY_X',filter = {saturationY = 0.15,saturationX = 1.0,curvature = {0}, deadzone = 0.3, invert = false, slider = false,}}},action = iCommandPlaneSelecterHorizontalAbs, name = _('HOTAS Slew Horizontal')},
{combos = {{key = 'JOY_Y',filter = {saturationY = 0.15,saturationX = 1.0,curvature = {0}, deadzone = 0.3, invert = false, slider = false,}}},action = iCommandPlaneSelecterVerticalAbs  , name = _('HOTAS Slew Vertical')},

These lines define default bindings plus sensitivity and deadzone for the slew control. I didn't know the A-10C had these until I read your post and investigated. They make sense because the file "Throttle - HOTAS Warthog.lua" applies for the throttle only and does not create unwanted default bindings in joystick, pedals etc.

Many modules don't have .lua files for specific game controllers; they only have a generic "default.lua". They typically have default axis bindings (without sensitity adjustments) in that file. The AV8B is one of those. It has these lines of code:

{combos = defaultDeviceAssignmentFor("roll")  ,  action = iCommandPlaneRoll           , name = _('Roll')},
{combos = defaultDeviceAssignmentFor("pitch") ,  action = iCommandPlanePitch       , name = _('Pitch')},
{combos = defaultDeviceAssignmentFor("rudder"),  action = iCommandPlaneRudder       , name = _('Rudder')},
{combos = defaultDeviceAssignmentFor("thrust"),  action = iCommandPlaneThrustCommon, name = _('Thrust')},

Unfortunately, that creates the same axis bindings for every game controller which is a nuisance. As the unwanted bindings tend to come back with updates, I have taken the "combos" bit out. The first of these lines then reads:

{action = iCommandPlaneRoll           , name = _('Roll')},

I'm not sure this is of any help, especially as you didn't show an example of how you set default sensitivity for the slew control in the F-5E; so I might be way off.

[LeCuvier]

I tried to replicate the default sensitivity values of the A-10C in the AV8B:

1. created a copy of the "default.lua" and named it "Throttle - HOTAS Warthog.lua".

2. added a command definition for the LIDS (for use with a single maintained ON/OFF switch) for testing. I found that the module recognized the new file.

3. deleted the lines for the TDC slew from the "default.lua" and modified the ones in the "Throttle - HOTAS Warthog.lua" to read:

{combos = {{key = 'JOY_X',filter = {saturationY = 0.15,saturationX = 1.0,curvature = {0}, deadzone = 0.3, invert = false, slider = false,}}},action = iCommandPlaneSelecterHorizontalAbs, name = _('TDC Slew Horizontal')},
{combos = {{key = 'JOY_Y',filter = {saturationY = 0.15,saturationX = 1.0,curvature = {0}, deadzone = 0.3, invert = false, slider = false,}}},action = iCommandPlaneSelecterVerticalAbs    , name = _('TDC Slew Vertical')},

I could bind the 2 axes, but the sensitivity defaults had no effect.

It was an interesting experiment, and good to know that the module is actually capable of recognizing controller-specific .lua files; but unfortunately I could not produce sensitivity default behaviour.

[imacken]

There are default files in most of my modules for each device, e.g. for the Warthog HOTAS joystick and a separate one for throttle. It is because I have seen this that I asked the original question.

See attached images to show the 'joystick' folder contents for the F-5E, as an example, also the lines in the lua file that I change to reduce the TDC sensitivity - the default values are 'value_down=1.0' changed to 0.2. It should be noted that the default.lua has to be changed also with the same edit.

I can't see anything equivalent in the Harrier.

[LeCuvier]

The files ending with just .lua define the commands available for binding. Yes, in some cases you can change the value to something less than 1.0 in order to reduce the response. But that is not true in every case.

The files ending with .diff.lua are default profiles that have the same structure as the .diff.lua files under "saved games", and yes, you can change those although they are not meant to be.

The modules made by ED tend to have the full complement of files. Those made by 3rd parties mostly have just the "default.lua", and frankly I'm happy with that as these other files just make the whole thing more complex.

[imacken]

Yes, I understand all that. So, are we saying that in the case of the Harrier, there is no way to adjust the sensitivity of the TDC which I have bound to the Coolie Switch?

[LeCuvier]

Yes, I understand all that. So, are we saying that in the case of the Harrier, there is no way to adjust the sensitivity of the TDC which I have bound to the Coolie Switch?

You can change the sensitivity only if you bind the TDC control to the slew control X and Y axes, like you do for the A-10C.

 

For the TDC key commands there is no way to adjust sensitivity in the Harrier. For some modules I have been able to modify the gain values in the "clickabledata.lua"; but the Harrier's one doesn't even have an entry for the TDC. It's all "hermetic".

[imacken]

That is very frustrating, as almost all the modules have too much movement for the TDC on the Coolie Hat or the TMS. Makes fine adjustments difficult.

[Supmua]

TDC axis slew is actually doable with the Harrier (I use TMW throttle with slew mod) with some hick ups compared to the Hog or Hornet.

 

The only issue I found is spotty output via X axis, sometimes I have to slew a few times before it would register. But once it gets going then it is pretty smooth. I have zero issue with Y axis slew, not sure why.

[imacken]

TDC axis slew is actually doable with the Harrier (I use TMW throttle with slew mod) with some hick ups compared to the Hog or Hornet.

 

The only issue I found is spotty output via X axis, sometimes I have to slew a few times before it would register. But once it gets going then it is pretty smooth. I have zero issue with Y axis slew, not sure why.

 

I don’t use the slew axis as I find it very difficult to use and even less accurate than the controls I’m talking about, i.e. the coolie hat and TMS.

[Supmua]

Another option that I tried was mapping axis to buttons with Target. This way you can still make use of the TDC stick without wasting it. It works as well as the coolie hat mapping and can slew diagonally.

 

For example, split the X axis range (AxMap2 in Target GUI) so that from 0-30% input would slew left (y key) and 70-100% input would slew right (u key).

[imacken]

You’re talking a foreign language to me! I know nothing about TARGET.