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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Add comment