Minimal Shkval curve setting at 6

[Nobody96]

Hi

 

I just played around with some custom curves to allow lighter inputs from my ministick. The problem I encountered is, that if you choose a value below 6 for your custom curve, the shkval is not moving at all. And 6 is still a bit to fast to precisely aim at 7km+.

 

I don't know if a track would help but I could provide one where I set all custom curve values to 5. The only thing you would see is that I am unable to move my shkval though.

 

Binding a cooliehat as shkval controller also isn't an option, because even with a deadzone set at 100%, the (very very small) jitter from the ministick is blocking these input.

 

EDIT: The same is true for the A-10. If you choose a custom curve thats all set to 5, no sensor movement of the tgt-pod or the mavericks is possible

 

so long

Mathias

Edited November 19, 2011 by Nobody96

[Nobody96]

Can anyone confirm this finding? Are there any suggestions?

 

so long

Mathias

[159th_Viper]

Do not set the curve - set the saturation:

 

In-Sim via the SP GUI/Controls screen, Axis-Tune the HOTAS Slew Horizontal and Vertical Axis to the following values -

 

Joy_X:

 

Deadzone = 5

Saturation_Y = 80 (or less if too zippy)

 

 

Joy_Y:

 

Deadzone = 5

Saturation_Y = 80 (or less if too zippy)

 

See if that helps.

[sLYFa]

I also found using a ministick as skhval slewing control to be not precise enough.

Playing around with sensitivity /saturation settings didnt help very much.

The solution for me was having two controls for the skhval: The ministick for quick slewing to the general direction of the target and a POV switch to precisely aim on the target.

I do not have the problem with ministick "jitter", even at very small deadzones.

Maybe this is due to different hardware we use, I use TM HOTAS Warthog

[jib]

I have the G940 which has a three way mode switch, I have now mapped the mini hat joystick as analog control on mode 1 and have left it mapped to ,.;/ buttons on mode 2.

 

This works very well for fast scanning then switch to mode 2 for very fine locking.

 

I have also played around with curves, saturation and deadzones but haven't had much luck with making an accurate analog shkval setting :(

[Nobody96]

Do not set the curve - set the saturation:

 

In-Sim via the SP GUI/Controls screen, Axis-Tune the HOTAS Slew Horizontal and Vertical Axis to the following values -

 

Joy_X:

 

Deadzone = 5

Saturation_Y = 80 (or less if too zippy)

 

 

Joy_Y:

 

Deadzone = 5

Saturation_Y = 80 (or less if too zippy)

 

See if that helps.

 

So curvature or custom curves below 6 don't work for the cougar ministick. Pretty disappointing... I will keep it at 6 and continue swearing than.

 

so long

Mathias

[159th_Viper]

So curvature or custom curves below 6 don't work for the cougar ministick. Pretty disappointing... I will keep it at 6 and continue swearing than.

 

I did not say that :)

 

Set your curvature back to default and only adjust values as stated (saturation and dead-zone) and see if that helps.

[Nobody96]

I did not say that :)

 

Set your curvature back to default and only adjust values as stated (saturation and dead-zone) and see if that helps.

 

I will do that. By the way: the issue is not that it is to fast overall, but that there is a minimal speed for the tgt-pod and the shkval which you don't seem to suffer from when you are using digital inputs to slew them. Sadly though I ran out of colie hats, because I use a cougar throttle in combination with a g940 stick and use the cougars comm switch as modifier.

 

so long

Mathias

[Nobody96]

Joy_X:

 

Deadzone = 5

Saturation_Y = 80 (or less if too zippy)

 

Joy_Y:

 

Deadzone = 5

Saturation_Y = 80 (or less if too zippy)

 

Tested it with 80, 60 and 40 as saturation, but it was even worse. It is simply to fast for minor corrections at heigh range. I am currently using: "0 5 6 6 6 9 15 21 28 45 100" for the horizontal and vertical slew axis'. I would prefer to use something like 0 2 4 6.

 

I will keep hoping that someone takes a look at this someday or, if it is a needed game-mechanic, doesn't but tells us so :)

 

so long

Mathias