Search Issue Tracker
Fixed
Fixed in 1.18.1
Votes
2
Found in [Package]
1.11.1
Issue ID
ISXB-1119
Regression
No
UI element hitboxes misaligned for "Virtual Cursor" when resolution is not FullHD (1920x1080)
Reproduction steps:
1. Open the attached project “IN-85914.zip“
2. Open the scene “GamepadMouseCursorSample“
3. Connect a gamepad
4. In the Game View, change the resolution to any other (for example, “3840x2160“)
5. Enter Play Mode
6. Try to click on buttons and scroll the text using the gamepad
Expected result: UI Elements can be clicked at all times regardless the resolution
Actual result: Hitboxes of the UI elements are offset from their corresponding button
Reproducible in: 1.7.0 (2021.3.44f1, 2022.3.50f1), 1.11.1 (2021.3.44f1, 2022.3.50f1, 6000.0.23f1)
Reproducible on: MacOS 14.6.1 (M1 Pro), Windows 11 (user)
Not reproducible on: No other environments tested
Notes:
- This is only reproducible with Virtual Cursor input, could not reproduce with mouse
- The hitboxes are also offset if the resolution is changed in Play Mode
- Also reproducible in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment