Hello,
I may have encountered a bug, or I maybe do something wrong...
I have the following bone structure:
UpperArm ==> ForeArm ==> Hand ==> fingers
with an IK chain starting from UpperArm, with Hand as an IK Head.
Hand has an effector bone and IK Controller settings set to Position, with a control parameter:
I use code to change the effector bone's position, and set the IK control parameter (here IK_ArmB) to 1 when I do so. This allows me to move the arm with IK.
After moving the effector bone, I also want to use apPortrait.SetBoneRotation() on the hand or fingers.
However, if the control parameter is anything else than 0, it seems that apPortrait.SetBoneRotation() will not do anything anymore to any bone that is part of the IK chain (which seems normal) or at/beyond its Head (which seems like a bug).
So if I use IK to move the hand position, then I cannot anymore use apPortrait.SetBoneRotation() to set the rotation of the hand or its fingers (even if it the Head of after. The fingers are not part of any IK chain)
Hi!
We attached scripts to fix this issue.
The attached files are based on v1.4.8.
As we said, the files are temporary, so there may be potential issues.
So you don't have to use it unless you urgently need to fix this issue.
If you want to revert after installing, delete the "AnyPortrait" folder and import AnyPortrait again from Package Manager.
If you have any problems in the future, please let us know at any time!
Thank you for reporting the bug!
Hi!
We have checked the issue you reported and confirmed that this is a bug.
We apologize for the inconvenience.
We explored several workarounds but determined that this issue cannot be resolved in the current version (v1.4.8).
Our team has been working on improvements regarding IK recently, and we will include this issue in our work.
We can provide you with temporary script files for this issue, but this work may take some time.
Additionally, the temporary script files we can provide may have potential problems because they contain improvements for other issues and have not been sufficiently tested.
We'll leave a comment again when we're finished working on this issue.
Once again, we apologize for the inconvenience caused to you.