Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2017.2.0f3
Issue ID
977745
Regression
No
Scene.buildIndex returned after building project ignores inactive Scenes in build list
Steps to reproduce:
1. Open attached project
2. Load Scene "B"
3. Make sure Scene "A" is unticked in File>Build Settings
4. Enter Play mode
5. Check console - "0 Assets/B.unity" is logged
6. Build project (for Windows)
7. Check console - "1 Assets/B.unity" is logged
Expected result: the index of Scene B is always logged as 0 if it is the first active scene in the list
Actual result: the index of Scene B is logged as 1 after building a project
Reproducible with: 5.6.0f3, 2017.2.0f3, 2018.1.0a6
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
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Resolution Note (fix version 2019.1):
Verified fixed on 2019.3.0a4