Accepted: Separate walking controller from RenIK for ManyBoneIK

  • Status: accepted
  • Deciders: V-Sekai,fire,lyuma,
  • Tags: V-Sekai,

Context and Problem Statement

To be able to implement ManyBoneIk we need to extract the walking controller from RenIK.

Describe the proposed option and how it helps to overcome the problem or limitation

Extract the walking controller into like a gdscript.

Describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams

Split the tracker IKPoints from the controller.

Positive Consequences

We can migrate to many bone ik.

Negative Consequences

Conversion to gdscript may be slower.

Option graveyard:

  • Option: The status quo.
  • Rejection Reason: This solves nothing.

If this enhancement will not be used often, can it be worked around with a few lines of script?

It is a few lines of script.

Is there a reason why this should be core and done by us?

We manage the avatar experience.

References

License of the contribution

MIT License

Copyright (c) 2018-2022 SaracenOne
Copyright (c) 2019-2022 K. S. Ernest (iFire) Lee (fire)
Copyright (c) 2020-2022 Lyuma
Copyright (c) 2020-2022 MMMaellon
Copyright (c) 2022 V-Sekai Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.