Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X
Votes
0
Found in
2017.3.0b10
Issue ID
978564
Regression
No
BuildPipelineInterrfaces.InitializeBuildCallbacks() is called on every scene load when loading the same scenes multiple times
To reproduce:
1. Open project
2. Open profiler
3. Open and play 'main' scene
4. Observe that BuildPipelineInterrfaces.InitializeBuildCallbacks() is called on every scene load
Expected: BuildPipelineInterrfaces.InitializeBuildCallbacks() should be called only once after the first time scene is loaded and initialised.
Actual: it is called after every scene load
Reproduced: 5.6.4p4, 2017.1.2p4, 2017.2.1p1, 2017.3.0f3, 2018.1.0b1
Comments (1)
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
- 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
rachidDev
Mar 15, 2018 18:37
I have problem In the last patch released on 13 March, I notice the prefab has changed in his value y in the first load of scene, and that happen in the version beta..
this patch is goog Unity 2017.2.2p1 , but the only issue I'm facing it now is I can't get success when I use handle resolve to fix conflit between google SDK.