-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add Gamepad Support via GLFW #986
base: master
Are you sure you want to change the base?
Conversation
So the idea is that controller input does not use the same call-based propagation as mouse and keyboard with callback functions (OnMouseButtonCallback etc.)? |
I guess the current Regarding actually using the controller inputs as envisoined, I think it would require to pull the camera controller out of the view into the frontend in some form. Seemed too much work for the gamepad inputs prototype. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
…pads) into graph modules (e.g. View 3D)
allows to overwrite either data field for view cameras without touching the other
Publishes Gamepads provided by GLFW as frontend resource. This opens up the possibility to control parts of MegaMol via controller (e.g. View3D, Clipping Plane, etc). The new
Exotic Inputs Service
is supposed to grow up to feed Gamepad Inputs into MegaMol Graph Modules, e.g. for View3D Camera control.Summary of Changes
References and Context
Gamepad controlls are an approach to make manipulation of the Clipping Plane Pose suck less. Also may be cool in general, e.g. on Powerwall or other MegaMol PR stunts/demos.
TODOs
Test Instructions
Start MegaMol and connect your controller. Look at controller state in
GLFW Gamepads
window.