Search Issue Tracker
Fixed
Fixed in 1.0.10
Votes
0
Found in [Package]
1.0.9
Issue ID
BEHAVB-310
Regression
Yes
Behavior Graph is not updated after exiting Play Mode
How to reproduce:
1. Open the “BehaviorPlayModeBug.zip“ project
2. Open the “SampleScene“
3. In Project tab open the “Behavior Graph“
4. Enter Play Mode
5. Observe the Console (“String1“ is logged every frame)
6. Delete the “Log String1 to the console“ node
7. Exit and enter Play Mode
8. Observe the Console
Expected result: Nothing is logged in the Console
Actual result: “String1“ is logged in the Console
Reproducible in: 1.0.7, 1.0.9 (6000.0.49f1, 6000.1.4f1, 6000.2.0b1)
Not reproducible in: 1.0.6 (6000.0.49f1, 6000.1.4f1, 6000.2.0b1)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Changes done to Behavior Graph should be saved regardless if the user is in Play Mode or not, as it is an asset that is being edited and not a Scene object
- This bug can cause a lot of confusion for users, so the severity is quite big
- Neither reimporting the asset nor restarting the project fix the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Compiler IPC Exception and Editor Crash on AMD 9000-X3D CPU series
- Editor crashes in TextLib::FindIntersectingLink when hovering UITK Labels with <link> tags rendered via ATG
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
Add comment