Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0p3
Issue ID
992200
Regression
No
Prefab instance in the scene is not refreshed after the prefab is changed when Cache Server is in Local mode
To reproduce:
1. Open the user's attached project
2. Open scene "Test"
3. Make sure the Cache Server Mode is set to "Local" in Preferences -> Cache Server
4. Change the Layer of the "Cube" instance in the scene to any other than Default, apply changes to prefab
5. In the Explorer, copy "Assets/cache/Cube.prefab" to "Assets/", overwrite the original Cube.prefab
6. Switch back to Unity and observe that the Cube instance in the scene has not changed its layer, even though the prefab has
Expected result: Prefab instance in the scene has the same properties as the prefab
Actual result: Prefab instance in the scene is not refreshed after prefab is changed
Reproduced with: 5.6.5p1, 2017.1.3p1, 2017.2.1p3, 2017.3.1f1, 2018.1.0b6
Note:
- It may require enabling Custom Cache Location in Preferences -> Cache Server, if the issue does not reproduce after the first few tries
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note (2019.1.X):
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.