Search Issue Tracker
Fixed
Fixed in 1.3.X - Entities, 7000.0.0a1
Votes
0
Found in [Package]
1.3.0-pre.4 - Entities
7000.0.0a1
Issue ID
ECSB-1308
Regression
No
SubScene SceneSection "Scene Bounding Volume" component values appear as "NaN" when observed in the Inspector
How to reproduce:
1. Open the attached “test.zip” project
2. Open the “SampleScene”
3. “SceneSection: test (0)” from the Entities Hierarchy tab
4. Expand the “Scene Bounding Volume” component values
5. Observe the result
Expected result: “Scene Bounding Volume” component values have numerical values
Actual result: “Scene Bounding Volume” component values appear as “NaN”
Reproducible in: 1.2.0 (2022.3.44f1, 6000.0.17f1), 1.3.0-pre.4 (2022.3.44f1, 6000.0.17f1)
Could not test with: 2021.3.43f1 (Entities package not supported)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 7000.0.0a1):
This has been addressed.
Resolution Note (fix version 1.3.X - Entities):
This will be fixed in an upcoming entities version.