Search Issue Tracker
Duplicate
Votes
1
Found in
5.1.1f1
Issue ID
708407
Regression
No
[Input] When a fullscreen non-native resolution is used for a standalone player Input.mousePosition produces wrong results
To reproduce:
1.Create new project, import attached "repro" package.
2.Open and play "test" scene.
3.Notice in left-top corner - 3 GUI labels, click in the middle of pink sphere, ScreenToWorldPoint label will show 0,0,-10.
4.Build this scene for standalone, launch it in non-native resolution in fullscreen, try to repeat step 3.
5.Notice that ScreenToWorldPoint label will show wrong results.
Additional notes:
Going from fullscreen to windowed and back with alt+enter, causes strange behaviors to occur, like fullscreen clipping and selected resolution change.
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
This is a duplicate of issue #715666