Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.2.0a2
Issue ID
918394
Regression
No
Applying a change to the Muscle Settings in the Configuration modifies other muscle settings
When I modify the "Arm Down-Up" muscle range, the "Arm Front-Back" get locked with a range of 0. (see attached gif)
This also happens on other limbs like the Upper Leg.
repro:
- open project
- select Winston and open the Inspector
- In Rig, enter Configuration...
- Go to the Muscles & Settings tab
- Expand range options for "Arm Down-Up" & "Arm Front-Back"
(notice that the range values for the "Left Arm > Arm Front-Back" are -100 to 100)
- Modify the minimum value for the "Left Arm > Arm Down-Up" range
- click Apply...
bug: "Left Arm > Arm Front-Back" values are now 0 to 0
expected: "Left Arm > Arm Front-Back" values should not be affected and should still be -100 to 100
this is not a regression. repro since at least 5.6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment