Pygame: Analog trigger initial value is not the neutral trigger position
up vote
2
down vote
favorite
I'm developing an application that uses pygame to read analog trigger values from an XBox 360-Style gamepad.
This application relies on the triggers being initialized to the neutral position, or else it results in undefined behaviour.
The problem: analog triggers are interpreted as axes in pygame and those get initialized to 0 until they receive the first user input. But the neutral position (triggers are not pressed) of the triggers is mapped to -1.0.
So, until I somehow press both triggers, the signal I receive is “half-pressed” for both triggers, although I'm not pressing anything.
Is there a way to specify the initial state of the Joystick object? I already tried to define a custom JOYAXISMOTION event which didn't help.
Minimal code example:
import pygame
import time
pygame.joystick.init()
if pygame.joystick.get_count() <= 0:
print("No joystick or gamepad found")
exit()
device = pygame.joystick.Joystick(0)
device.init()
print(device.get_numaxes())
while True:
pygame.event.get()
# here, it prints 0.0, 0.0 when not touching the triggers,
# until I press them
print("Left trigger: {}t Right trigger: {}".format(device.get_axis(2), # left trigger
device.get_axis(5))) # right trigger
time.sleep(0.1)
pygame gamepad xinput
asked Nov 12 at 17:33
Prunebutt
111
add a comment |
up vote
2
down vote
favorite
I'm developing an application that uses pygame to read analog trigger values from an XBox 360-Style gamepad.
This application relies on the triggers being initialized to the neutral position, or else it results in undefined behaviour.
The problem: analog triggers are interpreted as axes in pygame and those get initialized to 0 until they receive the first user input. But the neutral position (triggers are not pressed) of the triggers is mapped to -1.0.
So, until I somehow press both triggers, the signal I receive is “half-pressed” for both triggers, although I'm not pressing anything.
Is there a way to specify the initial state of the Joystick object? I already tried to define a custom JOYAXISMOTION event which didn't help.
Minimal code example:
import pygame
import time
pygame.joystick.init()
if pygame.joystick.get_count() <= 0:
print("No joystick or gamepad found")
exit()
device = pygame.joystick.Joystick(0)
device.init()
print(device.get_numaxes())
while True:
pygame.event.get()
# here, it prints 0.0, 0.0 when not touching the triggers,
# until I press them
print("Left trigger: {}t Right trigger: {}".format(device.get_axis(2), # left trigger
device.get_axis(5))) # right trigger
time.sleep(0.1)
pygame gamepad xinput
asked Nov 12 at 17:33
Prunebutt
111
Do you intend to use only one of the triggers or both? Pygame treats them as one axis, so I'm not sure if there's a solution if you need both triggers.
– skrx
Nov 13 at 22:23
Huh? Weird, that's not what I experienced. In my application, both were recognized as their own axis (2 and 5, as seen in my snippet)
– Prunebutt
Nov 14 at 15:12
Hmm, maybe it depends on the gamepad. Both triggers control the value of axis 2 for me. When I hold the left one the value is 1 and when I hold the right one it's -1. There's no axis 5, so your code (device.get_axis(5)) raises apygame.error: Invalid joystick axishere. Which pygame version do you use? I have 1.9.4.
– skrx
Nov 14 at 15:19
I'm also using version 1.9.4. I guess it depends on the gamepad, then. I'm using the Logitech F710 in Xinput mode.
– Prunebutt
Nov 15 at 10:23
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm developing an application that uses pygame to read analog trigger values from an XBox 360-Style gamepad.
This application relies on the triggers being initialized to the neutral position, or else it results in undefined behaviour.
The problem: analog triggers are interpreted as axes in pygame and those get initialized to 0 until they receive the first user input. But the neutral position (triggers are not pressed) of the triggers is mapped to -1.0.
So, until I somehow press both triggers, the signal I receive is “half-pressed” for both triggers, although I'm not pressing anything.
Is there a way to specify the initial state of the Joystick object? I already tried to define a custom JOYAXISMOTION event which didn't help.
Minimal code example:
import pygame
import time
pygame.joystick.init()
if pygame.joystick.get_count() <= 0:
print("No joystick or gamepad found")
exit()
device = pygame.joystick.Joystick(0)
device.init()
print(device.get_numaxes())
while True:
pygame.event.get()
# here, it prints 0.0, 0.0 when not touching the triggers,
# until I press them
print("Left trigger: {}t Right trigger: {}".format(device.get_axis(2), # left trigger
device.get_axis(5))) # right trigger
time.sleep(0.1)
pygame gamepad xinput
asked Nov 12 at 17:33
Prunebutt
111
I'm developing an application that uses pygame to read analog trigger values from an XBox 360-Style gamepad.
This application relies on the triggers being initialized to the neutral position, or else it results in undefined behaviour.
The problem: analog triggers are interpreted as axes in pygame and those get initialized to 0 until they receive the first user input. But the neutral position (triggers are not pressed) of the triggers is mapped to -1.0.
So, until I somehow press both triggers, the signal I receive is “half-pressed” for both triggers, although I'm not pressing anything.
Is there a way to specify the initial state of the Joystick object? I already tried to define a custom JOYAXISMOTION event which didn't help.
Minimal code example:
import pygame
import time
pygame.joystick.init()
if pygame.joystick.get_count() <= 0:
print("No joystick or gamepad found")
exit()
device = pygame.joystick.Joystick(0)
device.init()
print(device.get_numaxes())
while True:
pygame.event.get()
# here, it prints 0.0, 0.0 when not touching the triggers,
# until I press them
print("Left trigger: {}t Right trigger: {}".format(device.get_axis(2), # left trigger
device.get_axis(5))) # right trigger
time.sleep(0.1)
pygame gamepad xinput
pygame gamepad xinput
asked Nov 12 at 17:33
Prunebutt
111
asked Nov 12 at 17:33
Prunebutt
111
asked Nov 12 at 17:33
Prunebutt
111
asked Nov 12 at 17:33
Prunebutt
111
asked Nov 12 at 17:33
Prunebutt
111
111
Do you intend to use only one of the triggers or both? Pygame treats them as one axis, so I'm not sure if there's a solution if you need both triggers.
– skrx
Nov 13 at 22:23
Huh? Weird, that's not what I experienced. In my application, both were recognized as their own axis (2 and 5, as seen in my snippet)
– Prunebutt
Nov 14 at 15:12
Hmm, maybe it depends on the gamepad. Both triggers control the value of axis 2 for me. When I hold the left one the value is 1 and when I hold the right one it's -1. There's no axis 5, so your code (device.get_axis(5)) raises apygame.error: Invalid joystick axishere. Which pygame version do you use? I have 1.9.4.
– skrx
Nov 14 at 15:19
I'm also using version 1.9.4. I guess it depends on the gamepad, then. I'm using the Logitech F710 in Xinput mode.
– Prunebutt
Nov 15 at 10:23
add a comment |
Do you intend to use only one of the triggers or both? Pygame treats them as one axis, so I'm not sure if there's a solution if you need both triggers.
– skrx
Nov 13 at 22:23
Huh? Weird, that's not what I experienced. In my application, both were recognized as their own axis (2 and 5, as seen in my snippet)
– Prunebutt
Nov 14 at 15:12
Hmm, maybe it depends on the gamepad. Both triggers control the value of axis 2 for me. When I hold the left one the value is 1 and when I hold the right one it's -1. There's no axis 5, so your code (device.get_axis(5)) raises apygame.error: Invalid joystick axishere. Which pygame version do you use? I have 1.9.4.
– skrx
Nov 14 at 15:19
I'm also using version 1.9.4. I guess it depends on the gamepad, then. I'm using the Logitech F710 in Xinput mode.
– Prunebutt
Nov 15 at 10:23
Do you intend to use only one of the triggers or both? Pygame treats them as one axis, so I'm not sure if there's a solution if you need both triggers.
– skrx
Nov 13 at 22:23
Do you intend to use only one of the triggers or both? Pygame treats them as one axis, so I'm not sure if there's a solution if you need both triggers.
– skrx
Nov 13 at 22:23
Huh? Weird, that's not what I experienced. In my application, both were recognized as their own axis (2 and 5, as seen in my snippet)
– Prunebutt
Nov 14 at 15:12
Huh? Weird, that's not what I experienced. In my application, both were recognized as their own axis (2 and 5, as seen in my snippet)
– Prunebutt
Nov 14 at 15:12
Hmm, maybe it depends on the gamepad. Both triggers control the value of axis 2 for me. When I hold the left one the value is 1 and when I hold the right one it's -1. There's no axis 5, so your code (
device.get_axis(5)) raises a pygame.error: Invalid joystick axis here. Which pygame version do you use? I have 1.9.4.– skrx
Nov 14 at 15:19
Hmm, maybe it depends on the gamepad. Both triggers control the value of axis 2 for me. When I hold the left one the value is 1 and when I hold the right one it's -1. There's no axis 5, so your code (
device.get_axis(5)) raises a pygame.error: Invalid joystick axis here. Which pygame version do you use? I have 1.9.4.– skrx
Nov 14 at 15:19
I'm also using version 1.9.4. I guess it depends on the gamepad, then. I'm using the Logitech F710 in Xinput mode.
– Prunebutt
Nov 15 at 10:23
I'm also using version 1.9.4. I guess it depends on the gamepad, then. I'm using the Logitech F710 in Xinput mode.
– Prunebutt
Nov 15 at 10:23
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267296%2fpygame-analog-trigger-initial-value-is-not-the-neutral-trigger-position%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267296%2fpygame-analog-trigger-initial-value-is-not-the-neutral-trigger-position%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you intend to use only one of the triggers or both? Pygame treats them as one axis, so I'm not sure if there's a solution if you need both triggers.
– skrx
Nov 13 at 22:23
Huh? Weird, that's not what I experienced. In my application, both were recognized as their own axis (2 and 5, as seen in my snippet)
– Prunebutt
Nov 14 at 15:12
Hmm, maybe it depends on the gamepad. Both triggers control the value of axis 2 for me. When I hold the left one the value is 1 and when I hold the right one it's -1. There's no axis 5, so your code (
device.get_axis(5)) raises apygame.error: Invalid joystick axishere. Which pygame version do you use? I have 1.9.4.– skrx
Nov 14 at 15:19
I'm also using version 1.9.4. I guess it depends on the gamepad, then. I'm using the Logitech F710 in Xinput mode.
– Prunebutt
Nov 15 at 10:23