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

the algorithm is diffcult to use #19

Open
lvZic opened this issue Feb 1, 2023 · 1 comment
Open

the algorithm is diffcult to use #19

lvZic opened this issue Feb 1, 2023 · 1 comment

Comments

@lvZic
Copy link

lvZic commented Feb 1, 2023

the doc is poor and hard to understand, and there is little example code.
the code crash after 2 or 3 frames loop.
I wonder how to set each frame input and get each frame output?
what the MyGameNode mean in doc? If i should create another tree named MyGameNode?

@TheComet
Copy link
Owner

MyGameNode is your own code. I'm assuming you have a game engine that has its own node tree. So if this is true, then you have to copy the positions and rotations from your game into an identical structure of ik_node_t, solve, then copy the data back into your game.

If you want to use ik_node_t structures directly for the rest of your application you can do that too. Then you wouldn't need to do any copying, but then you are depending on IK structures, which is probably not a very good idea from a design point of view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants