Skip to content
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

Gamepad support #81

Closed
cochrane opened this issue Jun 18, 2017 · 1 comment · Fixed by #126
Closed

Gamepad support #81

cochrane opened this issue Jun 18, 2017 · 1 comment · Fixed by #126

Comments

@cochrane
Copy link
Owner

Could this work? Might be worth a try.

Rough idea for how the UI works:

  • Two modes, camera and bone/posing
  • Camera mode: Right analog turns camera, direction pad and/or left analog stick moves it.
  • Bone posing mode:
    • Direction pad selects bone: "Up" goes to parent, "down" goes to first child, "left"/"right" go to next/previous sibling. Only single selection for now (but multiple would be easy).
    • Analog sticks and/or triggers control rotation. Precise mapping to be determined experimentally.
    • For analog sticks, may make sense to use X,Y,A,B buttons to restrict axis to rotate around.
    • Analog stick/triggers do not set position/rotation directly. Rather, they change it slightly, depending on the degree to which they're pressed down.

Camera mode is arguably optional; I think most work will be done in bone posing mode. But it is what people are used to.

Have to investigate whether to start with the apple game controller framework (easy to use!) or good old HID Manager (controllers that are reasonably priced and easy to find in stores, but have to define own mapping!). In the long run it may be necessary to support both.

@sethk
Copy link
Contributor

sethk commented Feb 13, 2018

This is such an awesome idea! It makes so much more sense than inputting values or using the mouse.

cochrane added a commit that referenced this issue Apr 29, 2018
This starts support for #81, adding back-end support: A low-level class
that corresponds to one input element and knows how to interpret its
values. Which is harder than it looks with HID.
@cochrane cochrane linked a pull request Aug 2, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants