New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement joystick input #2346

Merged
merged 4 commits into from May 12, 2018

Conversation

3 participants
@smoogipoo
Contributor

smoogipoo commented Apr 3, 2018

Prereqs:

(Just adds support for keybindings).

Eventually we're gonna need the bindings to support multiple buttons for axispositive/axisnegative inputs, but this is fine for now.

@smoogipoo smoogipoo added the input label Apr 3, 2018

@smoogipoo smoogipoo added this to the April 2018 milestone Apr 3, 2018

@Numailia

This comment has been minimized.

Numailia commented Apr 5, 2018

is this gonna make possible for absolute positioning based on how far which direction you're tilting the joystick? ofcourse this would need a very accurate (and large) linear joystick, idk if whether or not those exist... but it would be cool if osu! can support another form of absolute input with this :o

@smoogipoo

This comment has been minimized.

Contributor

smoogipoo commented Apr 5, 2018

Yes. For that you'd query the axes from the joystick input state on Update().

@Numailia

This comment has been minimized.

Numailia commented Apr 5, 2018

wowie!! i dunno how practical this is, but it sure is cool :D

@peppy peppy modified the milestones: April 2018, May 2018 May 2, 2018

peppy added some commits May 12, 2018

Merge remote-tracking branch 'upstream/master' into joystick
# Conflicts:
#	osu-framework
#	osu.Game/Overlays/KeyBinding/KeyBindingRow.cs
@peppy

peppy approved these changes May 12, 2018

@peppy peppy merged commit 9515eb4 into ppy:master May 12, 2018

1 check passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details

@smoogipoo smoogipoo deleted the smoogipoo:joystick branch Jun 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment