Search Issue Tracker
By Design
Votes
5
Found in
2019.3
2019.3.1f1
2020.1
Issue ID
1219452
Regression
No
Scene.IsSubScene returns a different result when called in the Build
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Inspect the Console Window's message
4. Go to Build settings (File->Build Settings)
5. Enable the Development Build option
6. Click "Build And Run"
7. Inspect the Console Window in the Build
Expected result: Scene.IsSubScene returns the same value in the Editor and Build
Actual result: Scene.IsSubScene returns a different result
Reproducible with: 2019.3.2f1, 2020.1.0a23
Couldn't test with: 2017.4.37f1, 2018.4.17f1 (Scene doesn't contain a definition for isSubScene)
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
Resolution Note:
The 'isSubScene' property has a public setter as it is up the client to set this property when needed. The entities package controls this property in the Editor via the SubScene component. Unity uses this property only in the Editor for controlling how the Hierarchy should render a subscene.
This property is intentionally undocumented as it might be refactored in the future.