Outerra forum
Anteworld - Outerra Game => Tech demo, support, updates => Topic started by: Elecman on June 27, 2014, 09:13:49 pm
-
Can you decrease the sensitivity of the automatic joystick axis detection (for axis assignment)? One of the axis on my joystick is a bit jittery and constantly interferes with the assignment selection.
-
The threshold for detection is half the axis range, would it jitter as much?
Some joysticks & their firmware versions send data in invalid format, I think the throttle in Warthog is one of them, sending data in big-endian format. But when we patched it, other Warthog owners complained that it broke for them. It looks like there are two versions, but we do not have enough info to discern them and work around it.
-
have you tried
https://www.flickr.com/photos/awac9/14339116947/ (https://www.flickr.com/photos/awac9/14339116947/)
-
My joystick is indeed the Thrustmaster HOTAS Warthog with throttle and stick. I didn't try the deadzone setting yet, will give that a go.
If you want, I can do some debugging for you.
Edit:
The problem is caused by the gray slider wheel right of the throttle. Setting it out of the middle kind of solves the problem but changing the dead zone does not. I checked the output again and in fact it is not jittery at all. So presumably the problem is caused by the slider being in the middle position, right on the edge of the detection threshold. Maybe detecting a change of motion instead of a hard coded location is a better idea?
-
The detection is based on the change of motion. If the HOTAS sends big-endian data, even small jitter makes large jumps in output. Btw have you the latest drivers & firmware installed for it?
-
No, I didn't install any drivers. Let me try that.
Edit:
I installed the driver and updated the firmware. Problem still persists.
-
Ok, can you do the following? Set enable_hid_logging=true in eng.cfg, and send us the eng.log file from a short session where you test t in that problematic way.
-
Ok, here is the log
https://drive.google.com/file/d/0Bwk4bDWv3jAcckxsaDV6Zy1TQWs/edit?usp=sharing (https://drive.google.com/file/d/0Bwk4bDWv3jAcckxsaDV6Zy1TQWs/edit?usp=sharing)
By the way, you have elevator up and down reversed. If the elevator goes up, the aircraft should go up as well.
-
Yea, Axis 7 comes in big-endian format, causing all the problems. But I found the workaround for HOTAS wasn't activating, and there was a bug in the detection of the joystick.
-
Ok, thanks for clearing this up.
-
Please check with the latest version, eng.log should contain a line about detecting HOTAS.
-
Ok, it works now, but the tiny joystick on the throttle
(middle one here:)
http://www.gamingnexus.com/images/Article/ggqbqj3077/3.jpg (http://www.gamingnexus.com/images/Article/ggqbqj3077/3.jpg)
and the main joystick bare both mapped to axis 0 and 1.
-
Ok, it works now, but the tiny joystick on the throttle
(middle one here:)
http://www.gamingnexus.com/images/Article/ggqbqj3077/3.jpg (http://www.gamingnexus.com/images/Article/ggqbqj3077/3.jpg)
and the main joystick bare both mapped to axis 0 and 1.
It should be OK because axis number is relative to device and there are two devices in your setup "Joystick - HOTAS Warthog" and "Throttle - HOTAS Warthog". There should be number before colon identifying device like "1:Axis0" or "1:Btn0".
-
Ok, good :-)