-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
Adding Motion Matching Library #29892
base: master
Are you sure you want to change the base?
Conversation
#include "core/io/resource_loader.h" | ||
|
||
bool AnimationNodeMotionMatchEditor::can_edit( | ||
const Ref<AnimationNode> &p_node) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a note, in the cpp files, we use <tab> instead of <space> for indentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually set up the pre-commit-hook too. Will recheck it..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
Remember that the red crosses are the travis and appveyor ci checks failing. These are test compiles of the project. |
Ohh! I really am not sure why they fail... :( |
|
4ebf094
to
a5155a1
Compare
You can use Rebasing in git allows you to put the branch on top of the current git 3.2 master. It also allows you to squash multiple commits together for clarity. |
Okay thanks! |
@Aa20475 Is this still desired? If so, it needs to be rebased on the latest master branch, and squashed, as per this article. Also, since this PR is a feature proposal, you should consider opening a proposal which explains example use cases and how this approach will solve the problem. Otherwise, abandoned pull requests will be closed in the future as announced here. |
Okay will do it asap. I'd still love to work on this PR. ✌️ |
#32408 is my rebased pr, feel free to take it. |
That's cool! Can you give me a short desc of the changes you made , so that i can catch up? |
Note: Edited |
Ohh okay! That's cool! I've been exploring about it too. We still need to speed up the kdtrees knnsearch in some way. I thought we can implement it to run of GPU. There is a more complex and sophisticated algorithm which adds reinforcement learning to this which is the actual algorithm in the paper that proposed motion fields. But I thought speeding up the KNNsearch takes the first priority. Also, any luck with running it during game preview? |
Can you create a test project? |
…e cost and trajectory predictions..
I thought I had it somewhere on my Hard disk. I'll find it or make a new one asap! |
48b1712
to
4e0a498
Compare
Thanks a lot, @fire for doing the changes. I will make a test project quick and let you know. |
Can you post the design document for the GSOC, so I can make a proposal for this? |
@Aa20475 This PR doesn't build, please fix it and squash the commits. See this article for more information. |
This is an incomplete motion matching implementation. A more recent version is from https://github.com/Remi123/MotionMatching. I would like to archive this pull request. |
We are working on a motion-matching demo here. https://github.com/GuilhermeGSousa/godot-motion-matching/tree/engine-module |
I think this pull request should be closed because the original developer made this for google summer of code many years ago and salvage / replacement is done in a different place. Motion matching needs a proposal (there is one). Also, we should submit a new pr if we want to merge motion matching into Godot Engine. |
Basic Structure of Node and tree made
TODO: Build tree
bugsquad edit fixes: godotengine/godot-proposals#6122