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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
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