Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.15f1
2022.1.23f1
2022.2.0f1
2023.1.0a21
Issue ID
UUM-22928
Regression
No
"textureSheetAnimation.startFrame" acts differently comparing to Start Frame on the Particle System Component
How to reproduce:
1. Open the user-attached project “textureSheetIssue”
2. Open the “SampleScene” scene
3. Select the “ParticleSystem” GameObject in the Hierarchy
4. Under the “Particle System” Component on the “Texture Sheet Animation” change Start Frame to 5, observe the results and change it back to 0
5. Under the “Texture Sheet Feedback (Script)” Component change Start Frame to 5
6. Compare the results
Expected result: Start Frame set by the Script looks the same as set by “Particle System” Component
Actual result: Start Frame set by the Script is behaving differently
Reproducible with: 2021.3.15f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a21
Couldn’t test with: 2020.3.41f1 (Script and Particle System errors)
Reproducible on: Windows 11 Pro
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
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
Resolution Note:
It's true, but changing it risks affecting existing content. I've logged a documentation bug for us to update the scripting api reference to explain thata the value supplied from script is supposed to be in the 0-1 range.
It's done like this so that adding/removing frames does not necessarily invalidate the existing setting of this value.