Joystick Sensitivity Adjusments in v1.02 Patch

[Paco454 0]

As mentioned in the 1.02 patch,

joystickSensitivity[]={0.500000,0.500000,0.500000,0.500000,0.500000,0.500000,1.000000,1.000000,0.500000,0.500000

,0.500000,0.5000

00,0.500000,0.500000,1.000000,1.000000};

version=1;

I'm glad this has been added to address sensitivity issues, however, which one of these numbers, controls rudder, pitch, yaw ect..?

Providing these settings is a good thing, a bad thing is not to explain what each number represents. With out this information, it's not helping to solve a sensitivity issue because I'm shooting blanks with out it. Could you please, in a manner which explains each number and what axis it controls, what each number represents. I would be greatful if you could take the time to sort this out.

Please provide an example of an increased sensitivity settings as a template to use as guide.

Many thanks in advance.

PACO454

[LT.INSTG8R 0]

+1

I would also like some sorta of description/template on how use these settings.

I would really like to increase the sensetivity,its currently like stirring puddding on my X-52

[DaSquade 0]

Sorry to highjack your topic, but didn't want to take the risk of making a new one and have it move or worst: Locked.

I'm aware of the settings (sensitivity), but somehow i feel it has nothing to do with it. Anyway, my problem:

I have the microsoft precision 2

Worked great (compair price etc..) on OFP/VBS/LockOn.

Since patch 1.02 i decided to give the helis/planes a go again (used to love them ), but somehow i still don't have full access of my trust (decrease and increase). Bit hard to explain but apperently i only have 1/5 controle lenght on my axes for up and down:

----++/++---- visual layout of what my trust axes does. Where - is no controle and + the part where i have controle, / zone between up and down. No need to say it is extreme hard to controle the height if you only have 1/5 access of the full trust axes .

My joystick is configured correctly outgame and ingame (afaik).

Maybe it is possible to tweak the values of the joystcik sensitivity, but since i don't have an idea where to start...

Anyhelp is welcome, really would love to handle the heli/planes again like in the 'old' days .

[Hudson 0]

...but somehow i still don't have full access of my trust (decrease and increase). Bit hard to explain but apperently i only have 1/5 controle lenght on my axes for up and down:

----++/++---- visual layout of what my trust axes does. Where - is no controle and + the part where i have controle, / zone between up and down. No need to say it is extreme hard to controle the height if you only have 1/5 access of the full trust axes...

I am having the same problem. I use a saitek X-52 and there are percentage markers on the throttle, the thrust only kicks in after I have applied 80% of my throttle. This dosent leave alot of room for fine control ingame. Its like having 2 speeds "no go" or "go fast" Why cant we get a simple description in the readme on what each of these sensitivity settings are for?

Quote[/b] ]1.02 - New: Joystick sensitivity configurable in ArmAProfile file.

Configuration is done per positive/negative part of each axis.

Default is:

joystickSensitivity[]={

0.500000,0.500000,0.500000,0.500000,0.500000,0.500000,1.000000,1.000000,

0.500000,0.500000,0.500000,0.500000,0.500000,0.500000,1.000000,1.000000};

Dosent give a good idea of what this does unless your the person(s) that added this setting to the game.

[LT.INSTG8R 0]

Exactly what Hudson said. Its all well and good we have a joystick adjustment now, but could you plz tell us how to use it? What numbers represent, which axis etc.

Thanks

[Paco454 0]

Seems if you increase the values it increases sensitivity. I just replaced the first number to for each one and that seemed increase the sensitivity.

Still require a description for the values.

Example: 0.500000 to 1.500000

I use the x-52 Saitek

Paco454

[DaSquade 0]

Did some testing myself with the values. It is seams (of what i found out so far) it has to do what the axes and the deadzone and senitivity. O'really, you would say , but i wish it was that simple.

Indeed increasing the values makes it more sensitive. Since we don't know (yet) what value is what, it is guess/trial and error atm.

Something i did found out is if you decrease them all (test here was: 0.25000 for all) you alter the deadzone. Like in my problem (and others) now i have ++---/---++ as trust. Still not what it used to be but it is a change. Playing with the setting atm but i think it comes in groups of 4 (so 4x4). So left/right (rudder), noise and increase/decrease trothle. Please report your findings, as there are funnier things to do then edit/test/ .

[LT.INSTG8R 0]

Yeah I mean we can all sit there all night and change the numbers(I changed them all to 1.0's) but I hope tomorrow someone from BIS will poke his head in and explain the axis these numbers control.I would like a little less roll sens. but the 1.0s clearly made it more sensitive and responsive.

Just give us some more rudder authority at some speed or at least loss of energy when using it at speed(as it should be anyway) and I can live with the FM with a bit more tweaking.

[Hudson 0]

Those of you blowing out brain cells figuring these things out should get autographed copies of your localized special edition armed assault for all the free bug testing and quality assurance work. Looks to me like BIS has alot of thank yous to hand out for the thousands of dollars of free QA work being done by the community. Reports to the wiki alone should cost them $1 :-) Well they just deleted about 80% of the wiki bug list so that wouldnt get you much. Gotta quote DaSquade again...

Quote[/b] ]...there are funnier things to do then edit/test/

Isnt this the truth. Hard to find real play time with all the workarounds and testing being done.

[DaSquade 0]

Well, let me put it this way. I DON'T hate testing out what is what, but it is just the frustration it brings. Sofar i noticed it does change things (stick controle) but even dough i change one value a time, it just seams to have a live of its own. Meaning, it isn't doing what i think it should do .

I just mean, it would be a good time saver for us and less frustrating if BI simply had added a small discription what value means what.

[twisted 128]

i set the 0.5's to 0.7s and found a much improved less of control. i tried 0.3's but then it was quite sluggish.

be good to get official BIS (or a knowledagable users) feedback here.

[maxqubit 1]

I use a 360 controller (which has 2 analogue sticks and a pair of analogue triggers) which works now fine under the default settings, but i too am interested in knowing what value does what.

To 'trial and error' 16 variables is out of my league. A BIS dev should drop a line.

[Rg 0]

I'm guessing the values are doubled (look at the numbers in groups of 4 (Square shape, I'm guessing)) for pitch,yaw,roll (not necessarily in that order) and throttle (guessing, I couldn't figure those last 4 out).

After some testing, I prefer setting everything to 1.0 (for now anyways). This gives you a good balance between the sensitivity of v1.00 and v1.02, because the default values of .50000 seem to be set with keyboard flying in mind. So, for us joystick users, you might want to up the sensitivity.

Thank you BIS!

Right now I would say I'm satisfied with the flight model. Sure, there may be room for minor tweaks, but the general feel is great. I'll never fly a real helicopter, but at least the FM now "feels" good/accurate (*NOTE - I have not flown any real chopper sim).

I can't tell you how much fun I'm having just joyriding around in the MH-6, flying as fast and low as possible while using TrackIR. God damn, what a rush.

Happy Flying

[DaSquade 0]

I have been trail and erroring all day (yesterday), but somehow i didn't managed to find the exect explaination of the values.

For the moment i'm happy with these settings:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">joystickSensitivity[]={0.100000,0.500000,0.500000,0.500000,0.500000,0.500000,1.000000,1.000000,0.500000,0.500000

,0.500000,0.500000,0.500000,0.500000,1.000000,1.000000};

Still need to adjust is (once i really know what is what) but for the moment, after a day of practice, i can say the new flight system is very nice. It is just very different with the old behavior, mostly because of the banking. But again after some practice it can be a very presently suprise (banking + rudder).

A happy pilot again.

But the documentation of the values would still be appreciated .

[armored_sheep 56]

Number are sensitivity for each of the folowing inputs:

AXIS_X AXIS_Y AXIS_Z ROT_X ROT_Y ROT_Z SLIDER_1 SLIDER_2

First eight values are for positive part of axis, last eigtht for the negative one:

AXIS_X_POS AXIS_Y_POS AXIS_Z_POS ROT_X_POS ROT_Y_POS ROT_Z_POS SLIDER_1_POS SLIDER_2_POS

AXIS_X_NEG AXIS_Y_NEG AXIS_Z_NEG ROT_X_NEG ROT_Y_NEG ROT_Z_NEG SLIDER_1_NEG SLIDER_2_NEG

Value is transformed as:

value = pow(raw_value,1/sensitivity).

[DaSquade 0]

Thanks in name of all joystick users (that wanted this info).

Kind regards (off testing with the values again).

EDIT (after adjusting settings and do some ingame practice):

These values i use:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">joystickSensitivity[]={0.800000,0.800000,0.800000,0.030000,0.030000,0.030000,1.000000,1.000000,0.800000,0.800000

,0.800000,0.030000,0.030000,0.030000,1.000000,1.000000};

It is still a bit 'too' stable (using the UH60), but it is a good setting for me atm.

Didn't knew i would say this, but . Again not sure if it is realistic flight behavior but boy i love it !

Still doing normal things (drops/pickups, especially on rooftops ), so no fighting (FFARs etc).

[Hudson 0]

Thank you for the detailed explanation Armored_Sheep.

[Serclaes 0]

Thank you armored sheep.

Could somebody check if i made this right?

[Rg 0]

Number are sensitivity for each of the folowing inputs:

AXIS_X AXIS_Y AXIS_Z ROT_X ROT_Y ROT_Z SLIDER_1 SLIDER_2

First eight values are for positive part of axis, last eigtht for the negative one:

AXIS_X_POS AXIS_Y_POS AXIS_Z_POS ROT_X_POS ROT_Y_POS ROT_Z_POS SLIDER_1_POS SLIDER_2_POS

AXIS_X_NEG AXIS_Y_NEG AXIS_Z_NEG ROT_X_NEG ROT_Y_NEG ROT_Z_NEG SLIDER_1_NEG SLIDER_2_NEG

Value is transformed as:

value = pow(raw_value,1/sensitivity).

Armored_Sheep,

If you have the time, can you post what settings you and/or others at BIS use in house for flying with a joystick? I'm sure you have spent more time with this then we have

[LT.INSTG8R 0]

Thanks for the details Armored Sheep, Now I have something I can work with.

[DaSquade 0]

Can somebody explain me the difference between AXIS and ROT? Might sound stupid and silly, but somehow i can make it out .

Been spending half day trying to configuer my Z axis and i don't get any difference at all! By the way, i suppose i can edit my profile while i have left a mission (back in editor), save it and try mission again, without the need of full reboot of ArmA?

[Richklink 0]

But it's still confusing, and a biatch to tweak..Couldn't you include a setting within the game to do it in the controls section..with explanations??

Lock On had a nice tweaking screen (those who used it will agree). Can you not implement a similar concept?

[Serclaes 0]

[...]

Armored_Sheep,

If you have the time, can you post what settings you and/or others at BIS use in house for flying with a joystick? I'm sure you have spent more time with this then we have

I guess we have more time to test this out as they do  

And i'ld say the calibration of a joystick is something rather personal, not?  

[Paco454 0]

Thank you.

PACO454

[LT.INSTG8R 0]

But it's still confusing, and a biatch to tweak..Couldn't you include a setting within the game to do it in the controls section..with explanations??

Lock On had a nice tweaking screen (those who used it will agree). Can you not implement a similar concept?

I agree another set of sliders for the Axis(Pitch Roll and Yaw) would help simplify it.