Search Issue Tracker
Fixed in 1.5.5
Votes
2
Found in [Package]
1.1.7
Issue ID
1198198
Regression
Yes
[Addressables] Changes made to an Addressables Scene do not carry over when Addressable content is built.
Steps to reproduce:
1. Open the provided project "AddressablesSceneUpdate.zip"
2. In the Addressables Groups window select Build > New Build > Default Build Script
3. Enter Play Mode, Press "Load Next Scene" and "Spawn object" buttons
4. Exit Play Mode and make changes to the "NextScene" Scene (e.g disable "Text" GameObject)
5. In the Project window open "Cube" Prefab and make changes to it (e.g increase the scale of the x-axis)
6. Open "SampleScene" Scene, select Build > New Build > Default Build Script
7. Enter Play Mode -> Press "Load Next Scene" and "Spawn object" buttons
Expected results: Scene changes can be seen in Play Mode when Addressable content is built
Actual results: only Prefab changes can be seen in Play Mode when Addressable content is built
Reproducible with: Addresssables 1.1.7 (2019.3.0a5), Addressables 1.1.7 (2019.3.0b11), Addressables 1.1.7 (2020.1.0a13)
Not reproducible with: Addressables 1.1.5 (2019.2.13f1), Addressables 1.1.5 (2019.3.0a5), Addressables 1.1.5 (2019.3.0b11), Addressables 1.1.5 (2020.1.0a13)
Could not test with 2018.4.13f1 and below 2019.3.0a5 due to package related errors
Note: Scene changes can be seen but only if Build -> Clean Build -> All is used in the Addressables Groups window
Comments (3)
-
abhi_nb
Nov 24, 2020 14:03
Still broken on 1.8.5 with Unity 2020.1.13f1
-
invk
Dec 27, 2019 09:56
Addressable version 1.50 not fixed this issue
-
invk
Dec 27, 2019 09:56
Encounter the same bug.
It seems like Addressable can't successfully build new scene bundle after scene changes.
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
Resolution Note (fix version 1.5.5):
Fixed in Scriptable Build Pipeline 1.5.5 and above, should be used by Addressables 1.6.0 and above