Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.2.0b3
Issue ID
931488
Regression
Yes
A method with PostProcessSceneAttribute is not called after loading the Scene from Script
How to reproduce:
1. Open the attached "PostProcessScene" project and "Scene_1" scene
2. Observe the Loader.cs and SceneProcessor.cs scripts. Loader script loads the five scenes in the project additively, SceneProcessor has a method with PostProcessScene attribute that logs the scene count of loaded scene
3. Enter playmode, observe the console output
Expected result: A method with PostProcessScene attribute gets called every time the scene is loaded via SceneManager.LoadScene (or any other SceneManager function)
Actual result: A method with PostProcessScene attribute does not get called after the scene is loaded via SceneManager.LoadScene (or any other SceneManager function)
Note: Issue is reproducible when loading a scene additively or in a single mode, so the used scene loading mode does not seem to matter here
Regression introduced in - 2017.2.0b2
Reproducible with - 2017.2.0b3, 2017.2.0b2
Not reproducible with - 2017.2.0b1, 2017.1.0f3, 5.6.2p4
Fixed in - 2017.2.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment