Search Issue Tracker
Fixed in 5.2.0
Votes
36
Found in
5.1.2f1
Issue ID
715666
Regression
No
[Full-Screen] Input.mousePosition output does not match the displayed view on the screen
To reproduce the bug follow the steps
1. Open "InputMousePosition" project
2. Open "Test" scene
3. Build & Run
4. Select resolution that is different from Home Resolution of your computer screen
5. Press Play
Unity 5.1.X:
Input.mousePosition will return values that are out of the screen coordinates. User used workaround to get correct position of the mouse.
Unity 5.2.X (black boarders):
Input.mousePosition zero coordinates starts from bottom of black boarders, also input ratio does not fit the graphical view ratio.
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
- Resizing Profiler Module Details panel and releasing mouse button outside Unity doesn't cancel resize
- "Auto-hide gizmos" preference is not saved when reopening the project
- Sampling a custom depth texture on a machine with a GTX 1080 makes object's textures display the wrong color when in Play mode or Player
- Terrain is missing the Hidden/TerrainEngine/Details/WavingDoublePass shader when AssetBundles are built in older Unity Versions
- [Android] URP Project crashes when built on a device with PowerVR Rogue GE8320 GPU
mayasarii876
Mar 09, 2022 03:20
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
Fattie
Jul 13, 2020 01:25
This is STILL not fixed in 2020. What the heck ?
d0p3fish
Oct 24, 2016 22:24
Same Problem on Unity 5.4.2f2 Fullscreen Mode at Mac
hitmax87
May 27, 2016 18:46
Bug steel here, in new version!
Jill Chang
May 23, 2016 09:30
Same problem here!!!
Djamahl
May 11, 2016 18:17
BTW, we were able to repro in a standalone deployment, but our primary concern is Android/iOS where tap precision is less precise.
Djamahl
May 10, 2016 18:49
We're experiencing this issue on 5.3.1p3. Initially we thought some of our custom code was causing this, but we've constantly been able to reproduce this in a blank project with buttons with offset. We've used precision styluses to ensure the expected input locations are accurate and see that the issue is definitely not fixed.
I have a test project I can provide to show this problem clearly with debug visualization added.
https://www.dropbox.com/s/0k03ub4hl4j476r/ButtonUI.unitypackage?dl=0
Hodgson_SDAS
Apr 12, 2016 14:27
This bug did not get rolled into 4.x?
winterkewl
Mar 31, 2016 17:15
This issue is marked fixed, but it's still happening to me in 5.3.2.f1
SujitKadam
Mar 04, 2016 06:38
same problem with Unity 5.3