Shkval absolute axis - Mouse and X52 mouse. Some clues !

[Erforce]

Hello there !

 

it's been some times now, we're still stuck to get an analog skhval controller.

 

SU-25T has this feature, why not our Ka-50 ?

 

Today, I digged up some config files, and i successfully added the mouse control to skhval. The only problem i see is, it just doesn't work yet :) I'm missing something obviously.

 

I'm sure someone, somewhere can make it work !

 

i would like to post in russian forum as ED is very active there, but my russian knowledge is near zero. And google is not my friend too

 

so, get to pictures :

The SU-25 shkval mouse control :

 

Based on its config, i added lua code to Ka-50 :

 

to achieve this :

 

 

But it doesn't work in game :cry:

 

Having an analog skhval control, instead of 4-way digital, would allow us to lock more naturally and easily moving targets, like helicopters or planes, as the speed doesn't resets when you change direction. Without mentioning controlling the slew-speed entirely.

 

So if you have a clue about what other lua file or else we need to modify, share it !

[Erforce]

Oh, nice link, now i know what's behind the mini-stick ;)

 

But i have to respectfully disagree with you.

 

The difference between digital (0+1 state) and analog (0 ≤ state ≤ 1) is the multi-position input.

 

If the stick was a matter of 0 and 1, (OFF or ON) it would act like a standard cross found on every pre-2003 console gamepad, or X52 POV hats.

 

But the ministick is analog. This should be pressure buttons under it.

it act like a mouse, and has different state, like the mouse too.

 

you can see it here :

CENTERED :

 

Moved on grid, relative position between 0 and 1 :

 

moreover, when you release the stick, it act like a mouse : no input, stopping any relative movements from previous location.

 

For the Shkval, the game doesn't need to recenter each time, as this is an absolute grid.

Any movement is possible within -70 and +70 degrees (i don't know the real numbers) of center camera position. When no input are received, the camera just stops. it doesn't not recenter.

 

it's, on the paper, as simple as this.

 

That's why it worked in FC2(can't confirm this myself) and it's working in the SU-25T.

 

I keep believing in it.

 

Edit :

And for those who think i'm crazy to speak to myself, be aware that someone answered in between. How his post has been deleted entirely, i don't know, I've blurred the central text in case of.

Edited October 16, 2013 by Erforce

[fzfq3m]

Yep... I didn't thought about pressure pads that's why I deleted my previous answer in order to make another but you was faster than me :p

 

I can't remember but I think that Saitek's ST software allows to set the mini stick as normal axis instead of emulate a mouse and then you can assign those axis to the shkval axis in DCS... but then Iḿ affraid that the shkval will follow when the mini stick returns to center which will be annoying.

 

BTW I think that in BS we have both digital/analog control... we have four options in the cyclic section (for digital d-pad or hat switch) and the Absolute Horizontal/Vertical in the axis xommand section... but please correct me if I'm worng (again)

 

Regards

 

P.S: I will do some test with my x52 tonight and see if I can assign the mini stick to the shkval axis. I will report the results here

Edited October 16, 2013 by fzfq3m

[Erforce]

no worry. In fact, if you don't know, like me, how this fully works, don't try it.

 

in DCS, the X-52 column has only 7 analog inputs( X,Y,Z, joyX, joyY, JoyZ, Slider)

the mouse is activated only for the "mouselook"

 

TrackIr can control the shkval, but like the main X52 stick, it has another primary function.

 

The ministick, in sst, can act like a mouse (registry matters). that's why it should be codable somewhere.

[Suchacz]

Unfortunately, it looks like the mouse can't be bound to other axis commands than moving your view...

I completely agree with you and have discussed it with the team, but unfortunately it is not currently possible for us to assign axes to the mouse separately from the view control. This is a universal DCS limitation for the moment.

[karambiatos]

But in the Su-27,Su-33, F-15, Mig-29S, Su-25T, Su-25A.

 

i can assign the mouse axis to slew the TDC or shkval, and i do use it.

[Erforce]

Actually, with so many other modules working with the mouse control for TV screens, we can't say it's DCS limitation. I just looked how the SU-25T worked, and copy-pasted the same kind of information for Ka-50. now it's working in the menu, i'm sure i miss some specific scripted lua calls to make it work in game.

 

That's why i restarted a new thread about this. Having the shkval control on the digital POV hats, is un-natural. In the real KA-50, the Shkval slew control is a stick on the cyclic, like on X52.

 

We should not let this wish die slowly. A natural Shkval control is more important than having an electrical system, or even the external temperature.

As for the upcoming FA-18C, the Target Designator should be bounded to the analog ministick. Chosing a slew speed and a direction dynamically is why we'll be able to shoot the S300 command center, before we die.

 

Anyway, right now, i can't let my beloved Ka-50 to his hangar.

[ZaltysZ]

You can try converting Ministick to DX axis, if you can afford loosing some other axis (i.e. twist is good candidate for sacrifice, if you use rudder pedals): http://forums.eagle.ru/showthread.php?t=63794&highlight=x52

[Erforce]

Hmmm.. that's interesting !

 

After a few tries, i succeeded in remapping the ministick to RX and RY rotaries.

 

I can't say it's easy to use, because of curvatures and the design itself, but i'll digg it up later.

rep inbound !

 

- A mouse support for this stick should be created if it's possible, registry tweaking is not recommended :)