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

No Default ImputMap actions for character controller #348

Closed
DeficientNull opened this issue Dec 16, 2024 · 5 comments
Closed

No Default ImputMap actions for character controller #348

DeficientNull opened this issue Dec 16, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@DeficientNull
Copy link

Cogito and Godot Engine Version:

Latest for both

Description:
I expect to run the example scenes with existing Input Actions since the docs imply that. This doesn't happen though and the docs don't go into detail about how to set that up.

Reproduction steps:
Run the latest version of the project and attempt to walk or assign your own controls for movement.

@DeficientNull DeficientNull added the bug Something isn't working label Dec 16, 2024
@Phazorknight
Copy link
Owner

Hey, sorry about this.

Unfortunately, the way Godot stores the InputMap inside the project settings, there's no super-easy way to include them when grabbing Cogito from the AssetLibrary.

I recommend using the whole Cogito project from this GitHub repo. That way, the input map is preconfigured and you should be good to go. We'll also update the documentation to be clearer about this.

We were experimenting with adding a button that would "reset" the project input map configuration to provide this, but the implementation was a bit questionable, will look into improving this in future updates though.

@DeficientNull
Copy link
Author

Right, yes i eventually found that out. One temporary fix is to just have the input map names in the documentation. Simply to make sure people know how to set them up manually if they didn't realize they needed project.godot like me.

Regardless, thank you for the speedy reply. Loving the template so far.

On another note, it seems part of the weapon material is broken and does not display properly. This time i'm not sure it's an issue with missing files. Something to do with a global shader parameter viewmodel_fov being missing.

@Phazorknight
Copy link
Owner

@DeficientNull
Yeah, I'll update the documentation soon to make this clearer and include a list of input map actions, now that I'm back from my winter break.

Re weapon material: Would you be able to open a new issue with this with a few more details? (which mesh/material, how it's broken?)

@Phazorknight
Copy link
Owner

@DeficientNull
I've added a function to reset your projects input map settings (which will also add any needed input map settings on a blank project) in this commit: 0fd1fa3

Give it a spin when you have a second, should help getting projects off the ground more easily.

@Phazorknight
Copy link
Owner

Closing this as this has been changed/updated. Please reopen if there's still issues with this.

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

2 participants