Search Issue Tracker
Fixed in 5.5.0
Votes
1
Found in
Issue ID
817356
Regression
No
[AW] Remove properties breaks recorded scene value
Steps to reproduce:
1. Create new project and add cube with rotation (0, 0, 330)
2. Open animation window, create animation, move to keyframe at 0:30 and set rotation to (0, 0, 350)
3. Inspect first keyframe and notice that everything is good - rotation is same as in step 1
4. Move back to keyframe at 0:30 and remove all rotation keyframes by clicking "Remove Properties"
5. Again, set rotation to (0, 0, 350) and inspect first keyframe
6. Notice that first keyframe has rotation of (0, 0, 350), not (0, 0, 330)
Basically, rotation messes up if rotation is recorded for after rotation property is removed
This is not a regression and is repro in all versions.
workaround: after removing property, numerically input desired value before re-activating recording. Value will then be added a frame zero as expected.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions appear when clicking to rename and then deleting the only GameObject in a scene
- Crash on "core::base_hash_set" when using nested [SerializeReference] fields in List<T> structures
- A ghost Game Window and multiple errors appear in the Editor when a Render Texture used by a Camera's "Target Texture" property is deleted
- Color Picker feels less smooth when dragging a Variables Color property in UI Builder Inspector
- Crash on xatlas::internal::pack::Atlas::findChartLocation_bruteForce when generating the lighting
Add comment