Search Issue Tracker
By Design
By Design in 6000.0.X
Votes
0
Found in
2021.3.38f1
2022.3.29f1
6000.0.2f1
Issue ID
UUM-71879
Regression
No
OnBeginDrag is not called when the OnEndDrag was called in the same frame
How to reproduce:
1. Open the user-attached project “EndDragMissingIssue”
2. Open the “test” scene
3. Enter the Play Mode
4. Drag the white square and observe the green square following your mouse
5. Press and hold the Left Ctrl to slow down the frame rate
6. Release the mouse and quickly start dragging the white square again
7. Observe the results
Expected results: The green square follows the mouse as before
Actual results: The green square doesn’t follow the mouse because “OnBeginDrag” wasn’t called
Reproducible with: 2021.3.38f1, 2022.3.29f1, 6000.0.2f1
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
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:
Unfortunately what is being described as the desired outcome is not how the system works. If you need it to work differently that's a feature request and you can submit your idea on the public roadmap for input: https://unity.com/roadmap/unity-platform/gameplay
I suggest checking if the behavior you desire can be achieved with the Input System package (https://docs.unity3d.com/Packages/com.unity.inputsystem@1.8/manual/index.html) as it's much better than the legacy input system already and actively being worked on.
Resolution Note (6000.0.X):
Unfortunately what is being described as the desired outcome is not how the system works. If you need it to work differently that's a feature request and you can submit your idea on the public roadmap for input: https://unity.com/roadmap/unity-platform/gameplay
I suggest checking if the behavior you desire can be achieved with the Input System package (https://docs.unity3d.com/Packages/com.unity.inputsystem@1.8/manual/index.html) as it's much better than the legacy input system already and actively being worked on.