Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
Issue ID
696614
Regression
Yes
BlendTree in graph view doesn't get updated when a controller's parameter get deleted
repro1:
Create a New Animator Controller
Create a new Blend Tree
Go into the Blend Tree
(make sure you have no parameters)
Right-click the Blend Tree and select "Add Blend Tree"
(you should now have two chained Blend Trees, that both use Blend parameter)
Create a new Float parameter and name it "A"
Select first Blend Tree and set "A" as it's Parameter.
Deleting the only existing parameter "A" does not reset the Blend Tree parameter to "Blend". It still has an "A" slider that is no longer connected to a parameter. Deleting a parameter that is being used by a Blend Tree, should reset the slider to Blend.
Also notice that "A" no longer exist in the Blend Tree parameter pull-down list, but is assigned as a slider, that does nothing.
In 4.6 blend tree was updated correctly.
repro2:
Create Animator Controller
Create a Blend Tree
Create a second Blend Tree from the first one
Create a parameter
Select the SECOND Blend Tree and assign the parameter
Error: "parameter name does not exist."
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment