Search Issue Tracker
Fixed in 2022.2.7f1
Fixed in 2023.1.0b4
Votes
0
Found in
2022.2.4f1
2023.1.0b2
Issue ID
UUM-25471
Regression
No
Animation is played on a loop even though "TileAnimationFlags.LoopOnce" is used when selecting the Timemap in Editor
Reproduction steps:
1. Open project “LoopingTest”
2. Open scene “SampleScene”
3. Make sure the Inspector window is open
4. Enter Play mode
5. Wait for the animation to stop playing
6. Select “Grid\Tilemap” GameObject
Expected result: the animation doesn’t start playing again
Actual result: the animation starts playing on a loop
Reproducible with: 2022.2.4f1, 2023.1.0b2
Couldn’t test with: 2020.3.44f1, 2021.3.17f1 (TileAnimationFlags is introduced in the 2022.2 stream)
Notes:
- if the Inspector window isn’t open, the animation will play once after selecting the “Grid\Tilemap” GameObject
- selecting a different object in the scene after selecting the Tilemap, stops the animation loop
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2.7f1):
Fixed by another internal issue: UUM-25434: AnimatedTiles with LoopOnce set loop again in Editor Playmode when the Tilemap Component is selected
Resolution Note (fix version 2023.1.0b4):
Fixed by another internal issue: UUM-25434: AnimatedTiles with LoopOnce set loop again in Editor Playmode when the Tilemap Component is selected