Search Issue Tracker
Fixed
Fixed in 2022.3.62f1, 6000.0.48f1, 6000.1.0f1, 6000.2.0a10
Votes
0
Found in
2022.3.60f1
6000.0.43f1
6000.1.0b11
6000.2.0a7
Issue ID
UUM-100594
Regression
Yes
Values changed on a prefab are not retained when entering Play Mode
How to reproduce:
1. Open the attached “IN-97074” project
2. In the Project tab navigate to Game/Assets/Villagers and select the “VillagerBase” prefab
3. In the Inspector tab find “Villager Behaviour” Script Component
4. Change any values in the Script Component
5. Click on the Scene view/Game view/Hierarchy tab to unselect prefab
6. Enter Play mode
7. Select the “VillagerBase” prefab again
8. Observe the changed values
Expected result: Values are retained
Actual result: Values revert to old ones
Reproducible with: 2022.3.12f1 (4fe6e059c7ef), 2022.3.60f1, 6000.0.43f1, 6000.1.b11, 6000.2.0a7
Not reproducible with: 2021.3.49f1, 2022.3.11f1
Reproducible on: macOS 15.3 (M2 Ultra)
Not reproducible on: Windows 11
Workaround: Values are retained if the prefab remains selected when entering Play mode
Notes:
- After changing the values, sometimes they are retained, when clicking anywhere on the Inspector tab
- Removing the “DefaultSceneLoader” script fixes the issue (Game/Script)
- When clicking on Scene/Game view to unselect the prefab, behavior is inconsistent
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Render Graph Execution errors when using GPU occlusion culling with 'Opaque Objects' frame setting disabled on a Camera
- Animator window: “Delete” menu item not greyed out for Base Layer context menu
- Resetting “PC_RP Asset (Universal Render Pipeline Asset)” causes Game view to become black and throws Renderer and NullReference errors in the Console window
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
Add comment