Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.1.0f1
Issue ID
696817
Regression
Yes
AW can no longer move the current time before the first key
AW can no longer move the current time before the first key
1. What happened
When I try and move the current time (red line) before the first key, the red line snaps back to the first key.
This did not happen in 5.0
2. How we can reproduce it using the example you attached
Create a Cube
Open the AW
Click create to create a clip
Click Add Property and add the Cube : Translation
(you should now have two keys, one at frame 0, and the other at frame 60)
Move the second/last key to frame 120, and move the first key to frame 60
BUG: Try to move the current time (red line) before the first key... it snaps back to frame 60 :(
If you enter frame 0 in the current time field (top left corner of AW) the current time becomes 0, but then snaps back to 60 as soon as you click the UI again :(
You are able to set the current time past the last key (expected), but are not able to do the same thing before the first key (not expected).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Add comment