Search Issue Tracker
Active
Under Consideration for 1.0.X
Votes
0
Found in [Package]
1.0.13
Issue ID
BEHAVB-412
Regression
Yes
The Parent Behavior node becomes dirty when a leaf node is edited
How to reproduce:
- Open the “BehavBugRepro.zip“ project
- Connect the project to any or a new Version Control project
- Check in any changes (to hide any changes in the “Pending Changes“ tab)
- Open the “Child“ Behavior Graph
- Move any node inside the “Child“ graph
- Focus on the Unity Version Control window
- Observe the Pending Changes tab
Actual result: “Child“ and “Parent“ assets are dirtied and shown
Expected result: Only the “Child“ asset is dirtied and shown
Reproducible in: 1.0.8, 1.0.13 (6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2)
Not reproducible in: 1.0.7 (6000.0.63f1)
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment