Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.1.0-pre.3 - Entities
1.2.0-pre.6 - Entities
Issue ID
ECSB-957
Regression
No
Entities ArgumentException error is thrown when creating nested Sub Scenes
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/OutdoorsScene“ scene
3. Select the “Cube” and the “Cube (1)“ GameObjects in the Hierarchy window
4. Create a new Sub Scene (Right click one of the selected GameObjects in step 3 > New Sub Scene > From Selection)
5. Save the project (File > Save)
6. Observe the Console window
Expected result: No errors thrown in the Console window
Actual result: “ArgumentException: We are reading a UnityEngine.Object but the deserialized index is out of range for the given object table.“ error is thrown in the Console window
Reproducible with: 1.1.0-pre.3, 1.2.0-pre.6 (2022.3.19f1)
Not reproducible with: 1.1.0-pre.3 (2022.3.20f1, 2023.3.0a19), 1.2.0-pre.6 (2022.3.20f1, 2023.3.0b7)
Fixed in: 1.1.0-pre.3, 1.2.0-pre.6 (2022.3.20f1)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Comments (2)
-
hww
Oct 10, 2024 18:17
The issue still appears in Entities 1.3.2
-
yboumaiza
Aug 31, 2024 02:30
The issue still appears in Entities 1.2.4
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
- Warnings in the Bug Reporter window are cut off and not truncated when the Bug Reporter window is resized to its minimum size
- Color is incorrectly applied to objects when initialized with non-normalized parameters
- SerializationUtility.GetManagedReferencesWithMissingTypes() don't return null when “Prefab has missing SerializeReference Types“ warning banner is present
- Memory leak when VFX Graph is open and Camera has "Target Texture" enabled
- The Canvas component's warning box is missing an apostrophe when Additional Shader Channels is set to "Normal" and "Tangent" with Render Mode set to "Screen Space - Overlay"
Resolution Note:
This bug is fixed in 1.2.0+ we have no plans to fix it in any earlier version. We recommend users upgrade if they encounter this issue.