Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
2
Found in
5.4.0f3
Issue ID
824304
Regression
No
Input.mousePosition returns incorrect value when using locked cursor
Reproduction steps:
1. Open the "bug.zip" project.
2. Open the "test" scene.
3. Play the scene.
4. Notice that the cursor is not centered.
Actual result: Cursor is offset 20 pixels from the center of the screen.
Expected result: Cursors is in the middle of a screen.
Note: Offset is around 12 pixels in the standalone build.
Reproduced on: 5.5.0a6, 5.4.0p2, 5.4.0f3, 5.3.6p3, 5.3.5f1
Comments (1)
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
SkedgyEdgy
Oct 28, 2018 19:50
This issue still occurs. It seems to be locking to the center of the window instead of the center of the viewport. In the editor, the offset is 20 pixels, and the title bar is 40 px tall. In the standalone, the title bar is 24 px tall, and the offset is 12 pixels. In fullscreen, when there is no title bar, there is no offset.