Search Issue Tracker

Won't Fix

Won't Fix in 1.12.X

Votes

0

Found in [Package]

1.12.0

Issue ID

ISXB-1400

Regression

No

Portion of the Game view Window stops registering mouse events when switching between touch and mouse input

Package: Input System

-

Reproduction steps:
1. Make sure a display with touch screen is available for testing
2. Open the attached “IN-93467.zip” project
3. Open the “SampleScene”
4. Enter the Play mode
5. Move the mouse cursor around in the Game view
6. Observe input logs in the Console
7. Press '1' on the keyboard to switch input
8. Move the finger around in the Game view
9. Observe input logs in the Console
10. Press '1' on the keyboard to switch input back
11. Move the mouse cursor over the Game view
12. Observe input logs in the Console

Expected result: The whole Game view Window triggers mouse events
Actual result: Left side of the Game view does not trigger any mouse events

Reproducible with: 1.7.0 (2021.3.48f1, 2022.3.57f1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2), 1.12.0 (2021.3.48f1, 2022.3.57f1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2)

Reproducible on: Windows 11
Not reproducible on: No other environment tested

Note:
- Removing focus from the Game view Window and then switching back to Game view fixes the issue

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (1.12.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.