A NodePath in a Node cannot cope if the destination node moves in the node heirarchy - if the destination moves to a new path then the NodePath does adjust accordingly.
A NodePath cannot reference a unique item from a branch that has identical twin children.
To Reproduce
Steps to reproduce the behavior:
Load a Limb.
Add a pose Path and a pose target under Path.
Copy target and paste it to Path a few times.
Prepare a LimbSolver for Limb.
Pin the LimbSolver.
Drag any of the target nodes to the LimbSolver Detail target.
Regardless of which one is selected, PathNode can only find the first child. The symptom is that LimbSolver only moves to the first child's Pose.
Expected behaviorNodePath remembers the correct unique item. LimbSolver correctly moves the the appropriate target.
Screenshots
Platform (please complete the following information):
v2.105.*
Additional context
NodePath was introduced to fix #212. Which it did! ... but not well.
Describe the bug
To Reproduce Steps to reproduce the behavior:
Limb.Pathand a posetargetunderPath.targetand paste it toPatha few times.LimbSolverforLimb.LimbSolver.targetnodes to theLimbSolverDetailtarget.PathNodecan only find the first child. The symptom is thatLimbSolveronly moves to the first child's Pose.Expected behavior
NodePathremembers the correct unique item.LimbSolvercorrectly moves the the appropriatetarget.Screenshots
Platform (please complete the following information):
Additional context NodePath was introduced to fix #212. Which it did! ... but not well.