Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.41f1
2022.3.39f1
6000.0.12f1
6000.1.0a7
7000.0.0a1
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
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.