STORM-1899: Avatar hand poses randomly get stuck in spread position
Review Request #592 - Created July 19, 2012 and submitted
Ansariel Hiller | Reviewers | ||
viewer | |||
STORM-1899 | |||
None | viewer-release |
A proposed solution for STORM-1899 and the issue, where the handpose of avatars randomly get stuck in the spread hand position. In the current implementation, this case might happen under the following circumstances: * Avatar uses an animation with hand pose A * A request is issued to change hand pose to B * Before the viewer has blended pose A over to pose B, the original pose A is requested again * In this case, the hand pose will not be properly (re)set and because mNewPose == mCurrentPose, there will be no further blending, leaving the hand in it's current pose The patch will properly reset the hand pose in this case and update the visual parameters of the avatar.
Review request changed
Updated (July 19, 2012, 2:11 p.m.)
- changed from Fix VWR-1793: Avatar hand poses randomly get stuck in spread position to STORM-1899: Avatar hand poses randomly get stuck in spread position
Changed summary to reflect correct JIRA issue.
Posted (July 19, 2012, 4:55 p.m.)
-
indra/llcharacter/llhandmotion.cpp (Diff revision 1) -
you probably don't want to write to this memory if you are getting bad values. Best to warn and then do nothing.
Review request changed
Updated (July 25, 2012, 3:12 p.m.)
-
- added Diff r2
Updated the diff based on Richard's comment. The new hand pose is only set if the requested pose is valid (*requestedHandPose => 0 && *requestedHandPose < NUM_HAND_POSES). If it's invalid, it is only logged and the hand motion update continues with the current pose.
Ship It!
Posted (July 28, 2012, 2:15 a.m.)
I think the warning message should either go, or be modified to warn only once, or be changed to lldebug... the way it is now it floods the logfiles... i have 1900 repeats of that warning line in my log file, after being logged in for less than 5 minutes!
Ship It!
Review request changed
Updated (Aug. 16, 2012, 7:33 a.m.)
- changed from pending to submitted
Other reviews