Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.41f1
2022.3.39f1
6000.0.12f1
6000.1.0a7
Issue ID
UUM-76744
Regression
No
ScrollRect.velocity gets set to 0 when the initial value is set before the first frame in Start()
Reproduction steps:
1. Open the attached “rect.zip” project
2. Open the “SampleScene” Scene (Assets > Scenes)
3. Enter the Play mode
4. Observe the Console and the Game view
Expected result: The “2nd frame velocity” value is around 295-300 and the cyan rectangle moves towards the “Expected Stop Position”
Actual result: The “2nd frame velocity” value is close or equal to 0 and the cyan rectangle barely moves from initial position
Reproducible with: 2021.3.41f1, 2022.3.39f1, 6000.0.12f1
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Clicking “ResetPosition and Velocity” or “Restart Scene” buttons in the Game view, shows the expected result
- Does not reproduce if the velocity is set after the first frame
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:
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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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:
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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.