Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2.0a20
2020.2.0b2
Issue ID
1276959
Regression
Yes
SceneManager.GetActiveScene().name always returns level0 in Build
How to reproduce:
1. Open the user's attached "SceneManagerTest - Unity 2020.2.0b2.zip" project
2. Open the "SampleScene" Scene
3. Go to File -> Build And Run
4. Observe the text in the application
Expected result: The text in the application is "SampleScene" (SceneManager.GetActiveScene().name)
Actual result: The text in the application is "level0" (SceneManager.GetActiveScene().name)
Reproducible with: 2020.2.0a20, 2020.2.0b2
Not reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.6f1, 2020.2.0a19, 2020.2.0b3
Note:
- The issue is not reproducible in the Editor
- The issue is reproducible with Windows and Mac Build
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b3