Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X
Votes
1
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b16
2022.1
Issue ID
1373996
Regression
No
Particles are played at the wrong FPS when the particle's texture sheet animation is set to "Single Row"
How to reproduce:
1. Open project "ParticleBug.zip"
2. Enter "SampleScene" Scene (Assets>Scenes>SampleScene)
3. In the Hierarchy window select "Particle System"
4. Look at the Scene or Game window and observe the speed of the particles
5. In the Inspector window scroll down to the "Texture Sheet Animation" tab and expand it
6. Change Animation to "Whole Sheet"
7. Look at the Scene or Game window and observe the speed of the particles
Expected result: Speed of animation should be the same in both animations
Actual result: With animation "Single Row" the speed is slower
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.25f1, 2021.2.0b16, 2022.1.0a12
Notes:
- If the Animation is "Single Row" you need to multiply the FPS by the number of rows (20x8=160) to see the animations play at the correct speed
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b5
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.15f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.33f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.39f1