Search Issue Tracker
Fixed
Fixed in 6000.0.45f1, 6000.1.0b12, 6000.2.0a8
Votes
1
Found in
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99614
Regression
Yes
Animation Curve edits are not always saved when editing in a Prefab
How to reproduce:
1. Open the attached “IN-96102_animation_curve“ project
2. In the Project window select Assets > curve
3. In the Inspector window select “Curve“ field in the “New Mono Behaviour Script“ component
4. Change the shape of the curve and exit the Curve editor using the exit button (repeat at least 5 times)
5. Observe the results
Expected result: The changed shape of the curve is saved next time the Curve editor is clicked
Actual result: The changed shape of the curve is not saved next time the Curve editor is clicked
Reproducible with: 2023.2.0b14, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Not reproducible with: 2022.3.58f1, 2023.2.0b13
Reproducible on: MacOS 15.3 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested
Note:
- This issue only occurs when editing the curve directly in the Prefab Asset. The issue does not reproduce when editing a Prefab instance in a scene
Workaround:
- After changing the curve, click outside the Curve editor to exit instead of using the exit button, then the issue won’t happen
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
Add comment