-
Bug
-
Resolution: Fixed
-
1.21.20.22 Preview, 1.21.30.22 Preview
-
None
-
Confirmed
-
Multiple
-
1266221
The bug
If you start a camera move with a /camera set followed by a /camera ease, then interrupt it with a second move, the third /camera set gets lost, and an incorrect transition between the current point and the final point occurs, unless there is artificial delay added between the third and fourth commands. Since delay can't be added in functions, this workaround is not acceptable.
How to reproduce
1. Download and open the attached world
2. Click the button on the green blocks next to the command chain
3. Watch as you transition from 1 -> 2, then cut and transition from 3 -> 4
4. Now click the button on the red blocks
Expected behavior
It should play out the same as the first time: a transition from 1 -> 2, then a cut to 3 and transition from 3 -> 4
Observed behavior
The cut is lost. Instead, an incorrect transition from 2 -> 4 plays.
Notes
The two command chains are identical save for a two-tick delay between the set and ease functions. This is evidence that MCPE-181364 was not fixed in its entirety.
- relates to
-
MCPE-181364 /camera set behaves incorrectly when run during an existing camera interpolation
- Resolved