Search Issue Tracker
Fixed
Fixed in 1.3.X - Entities, 7000.0.0a1
Votes
0
Found in [Package]
1.3.X - Entities
7000.0.0a1
Issue ID
ECSB-1320
Regression
No
Entities Systems and Journaling windows break when opened during Play Mode
Steps to reproduce:
1. Open the “Users attached project”
2. Open the “GameStart” Scene
3. Make sure to keep the Systems window closed or hidden
4. Enter Play Mode
5. Press “Continue” through Game View and wait for the _“_HRK_Main” Scene to fully load
6. Clear the Console window
7. Open the Systems window and observe the Console
8. Open the Journaling window
Expected results: No errors are thrown in the Console and the Systems and Journaling windows *show data*
Actual results: NullReferenceException Error is thrown and the Systems and Journaling windows *show no data*
Reproducible with versions: 1.2.3 (2022.3.46f1)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- The exception always occurs in the same place when populating the world proxy, regardless of where the call is invoked. The NullReferenceException comes from a null system handle to an unmanaged system in the Content world.
-
nowisthetimellc
Sep 17, 2024 18:29
I've noticed that when I open the Entities, Systems, and Journaling windows in Play Mode, they either stop responding or show inaccurate information. This can be annoying since it makes debugging and analysis more difficult when playing. nowisthetimellc.com/
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note (fix version 1.3.X - Entities):
This was fixed in 1.3.2