Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.1.1-preview
Issue ID
1187223
Regression
No
[ECS][DOTS] Entity Conversion interface does not work in Sub-Scenes
Reproduction steps:
1. Open "1187223" project
2. Enter Play mode
3. Notice in the "Entity Debugger" window that there are 3 different Entity Objects
Expected Result: There should be 4 different Entity objects, one created by a Sub-Scene
Actual Result: Entity Conversion interface does not work in Sub-Scenes
Reproduced with: 2020.1.0a12, 2019.3.0b10, 2019.2.12f1, 2018.4.12f1
Did not reproduce on: 2017.4.34f1
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
When a game object is converted inside of a subscene, only entities created with GameObjectConversionSystem.CreateAdditionalEntity(GameObject) will be persisted in the subscene. This specifically means that entities created using calls to dstManager.CreateEntity() will not appear after conversion. More recent versions of entities actually warn if there are any such orphaned entities at the end of conversion.