Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2017.2.0f3
Issue ID
1035848
Regression
No
SceneManager.sceneCountInBuildSettings reports a different numbers of scenes than there actually is is the Build settings
To reproduce:
1. Open the project, attached by the user (Daniel.zip)
2. Open the "pre" scene
3. Put "Debug.Log (SceneManager.sceneCountInBuildSettings);" line into the Start method of ScoreManager script
4. Press Start button
5. Observe that console prints out 3 scenes
6. Open the build settings and see that there are 4 scenes
Expected: SceneManager.sceneCountInBuildSettings reports the correct amount of scenes in the Build Settings
Actual: wrong amount of scenes is reported and due to this SceneManager.LoadScene might load a wrong scene
Reproduced in 2017.1.3p4, 2017.2.0f3, 2018.3.2f1, 2017.4.2f2, 2018.1.0f2, 2018.2.0b3, 2018.2.0b4, 2018.3.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.2):
Fixed in 2022.1.0a3