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

Make input schemes game specific, not scene specific #448

Open
twaritwaikar opened this issue Apr 15, 2021 · 1 comment
Open

Make input schemes game specific, not scene specific #448

twaritwaikar opened this issue Apr 15, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@twaritwaikar
Copy link
Member

twaritwaikar commented Apr 15, 2021

We will have LOTS of duplication of effort as well as input binding data if we do store input keybindings per scene. We should store them per app i.e. like we do in the editor, and let us choose which input bindings the level needs at runtime

@twaritwaikar twaritwaikar added the bug Something isn't working label Apr 15, 2021
@twaritwaikar
Copy link
Member Author

twaritwaikar commented Apr 17, 2021

Actually having per-scene input bindings may not be that bad of an idea because we will potentially have a lot of different input configurations in the entire game with a lot of per-scene customization.

It may be feasible to have both kinds of input bindings in the engine. Both in the game and the scene and in case of name collisions, scene binding should be selected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant