Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.13f1
2023.1.0b11
2023.2.0a9
Issue ID
UUM-33753
Regression
No
The default value for a property is saved as an override when ApplyModifiedProperties is called after changing a value on a property of a variant in the Hierarchy
How to reproduce:
1. Open the attached project “PrefabVariantDefaultValue.zip“
2. Open Scene “SampleScene”
3. Select “TestPrefab0” in the Hierarchy
4. Press “Modify Original” button in the Inspector
5. Select “VariantChild” (child GameObject of TestPrefabVariant0) in the Hierarchy
6. Press “Modify Original” button in the Inspector
7. Save the Scene
8. Open "TestPrefab Variant.prefab" in the Assets folder
9. Observe the “Test Value 0” property
Expected result: The “Test Value 0” property is not marked as an override in the Inspector
Actual result: The “Test Value 0” property is marked as an override in the Inspector
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b11, 2023.2.0a9
Reproduced on: macOS 13.0.1 (Intel), macOS 13.2.1 (Silicon) (by reporter)
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.