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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
This is a duplicate of issue #715666