Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.28f1
2022.3.5f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-44740
Regression
No
[ParticleSystem] Texture Sheet Animation's cycleCount data types are different in the inspector and script
Reproduction steps:
1. Open the attached project “ParticleTest”
2. Open the Scene “SampleScene”
3. In the Hierarchy select the “Particle System” GameObject
4. In the Inspector go to Particle System > Texture Sheet Animation and change the “Cycles” number to a random float (e.g. 1.5)
5. Enter Play Mode and check the Console output
Expected result: Output is a float value (e.g. 1.5)
Actual result: Output is an integer (e.g. 1)
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproducible on: MacOS 13.3.1 (Intel)
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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.