Search Issue Tracker

Active

Under Consideration for 1.0.X

Votes

0

Found in [Package]

1.0.3

Issue ID

BEHAVB-4

Regression

No

Existing Custom Action nodes retain Action styling when inheritance is changed to Composite

Package: Unity Behavior

-

How to reproduce:
1. Create and open a new project
2. Install the Behavior package
3. In the Assets folder create a Behavior Graph (Create → Behavior → Behavior Graph)
4. Open the Behavior Graph
5. Right click and create a new Custom Action node named “Test” (Add… → Action → Create new Action…)
6. Inside the newly created “TestAction.cs” script change the “TestAction” class to inherit from Composite instead of Action
7. Inside the Behavior Graph create a new Action node using the created Custom Action “Test” (Add… → Action → Test)
8. Observe the created Action nodes

Expected result: Both of the created nodes display Composite styling
Actual result: The first created Action node retains the Action styling, while the second one displays the Composite styling

Reproducible with: 1.0.0(6000.0.24f1, 6000.1.0a2), 1.0.3(6000.0.24f1, 6000.1.0a2)
Could not test with: 2021.3.45f1, 2022.3.51f1 (Behavior package is not supported in these streams)

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.