Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1128653
Regression
No
Same Build Indices are returned with Scene.buildIndex when Scenes have the same name
How to reproduce:
1. Open the attached "ReproProject1128653.zip" project
2. Open Build Settings
3. Note that "Testing" Scenes have different Build Indices and their paths are different
4. Enter Play Mode
5. Observe the Console
Expected Behavior: The Scene Build Indices are printed according to the Build Settings
Actual Behavior: "Testing" Scenes have the same Build Indices printed in the Console even though they are different in Build Settings
Reproducible with: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Resolution Note (fix version 2021.2):
The Scene path is now used instead of Scene name to ensure the correct Scene build index is returned in play mode instead of the index associated with the first Scene found by a 'name only' search.