Search Issue Tracker
Fixed
Fixed in 1.0.3
Votes
0
Found in [Package]
1.0.2
Issue ID
BEHAVB-5
Regression
No
NullReference errors appear inside the Console window when deserializing BehaviorGraph after re-creating related GameObjects using the Behavior package
How to reproduce:
1. Open the attached "IN-86387" project
2. Open the "serialization-type-construct-fail-case" Scene and enter Play mode
3. Press the “Save” button on the top left corner of the Game window
4. Press the F5 key to reload the Scene (hotkey configured via the SerializationExampleSceneController.cs Script)
5. Press the “Load” button on the top left corner of the Game window
6. Observe the console
Expected result: Console window does not display any errors
Actual result: NullReferenceException error appears multiple times and an ArgumentException error appears once in the Console window
Reproducible in: 1.0.2 (6000.0.16f1, 6000.0.25f1, 6000.1.0a2) (Unity Behavior package introduced in version 6000.0.16f1)
Fixed in: 1.0.3 (6000.0.14f1, 6000.0.25f1, 6000.1.0a2)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: To re-test with the same Agent and setup in 1.0.3 Runtime Assets have to be deleted and reloaded, as well as Play mode has to be re-entered and “Save” has to be clicked to commit these changes before reproduction steps can be re-taken from 1 to 6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] [GameActivity] UI is unresponsive when Application Entry Point is set to GameActivity
- [Linux] VR template "Tutorial Player" GameObject becomes blank after entering Play mode
- Editor window minimizes when changing the Layout while using the Windows split-screen function
- Object pools do not reset when re-entering the Play Mode with reload domain disabled
- Performance issue when using Shadow-Casting Lights with Batch Renderer Groups
Add comment