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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
This is a duplicate of issue #715666