Page MenuHomeFeedback Tracker

Mathematical average for PITCH axis when using TWO controllers.
Closed, ResolvedPublic

Description

Hello,

I have configured a joypad AND a joystick for Arma3.

For helicopter analog pitch axis input I have set up both ontollers.
One analog axis from the joypad for pitch input.
Second analog axis from the joystick (throttle) for the pitch input.
Both axis go from -100 to +100 in the controler settings. All fine.
So that I can use what I want. With cyclic controls this is no problem.

However, for the pitch axis, the engine calculates the arithmetic AVERAGE of both input axis. At least for the pitch. When sitting in a helicopter one can see this by observing the pitch gauge.

The analog axis on the joypad is normally at 50% (center) when not used.
In this state my joxstick throttle can only manage to create 25-75% heli pitch.
When pushing joystick throttle to 100% AND joypad axis to 100% at the same time, I can get 100% heli pitch.

On the other hand, another example, when setting joystick throtte to 0%, I can only create a pitch from 0-50% with the joypad.

So the problem seems to be, that the game engine is calculating the arithmetic AVERAGE of both analog axes that are used for the pitch.

Can this be fixed/improved somehow? I don't know, that is the most elegant way to solve this problem... maybe ignore inputs from a controller that is idle for a amount of seconds.

A joypad pitch axis should be at center when you put it away, a joystick throttle can be anywhere between 0 and 100%.

However, the game engine should detect, which controller is used and which is put away and ignore the input from the controller that is put away and do not calculate and use the average for both axis inputs.

BR
Rob

Details

Legacy ID
1303389405
Severity
None
Resolution
Not Fixable
Reproducibility
Always
Category
Controls
Steps To Reproduce

Configure two controllers in parallel which each one have a analog axis for analog pitch.

Event Timeline

Rob2 edited Steps To Reproduce. (Show Details)May 12 2015, 10:59 PM
Rob2 set Category to Controls.
Rob2 set Reproducibility to Always.
Rob2 set Severity to None.
Rob2 set Resolution to Not Fixable.
Rob2 set Legacy ID to 1303389405.May 8 2016, 12:05 PM
Adam added a comment.May 13 2015, 10:40 AM

Hello,

We are aware of this issue, unfortunately we cannot address it right now due to the limitation of the engine.

Thank you for your feedback.