Search Issue Tracker
Fixed
Fixed in 1.5.0
Votes
0
Found in [Package]
1.1.1
1.2.0
1.3.0
1.4.1
1.4.2
1.4.3
Issue ID
ISXB-336
Regression
No
Input System duplicates input when using separate windows
Reproduction steps:
- Open the user’s attached project
- Open Scenes folder in the Project window
- Select all three scenes in the Project window (“External”, “TOP_Scene”, “MAIN_Scene”)
- Right-click on one of the selected scenes and click “Open scene additive”
- Enter the Play Mode
- Click on the red square in display 1
- Click on the green square in display 2
- Observe the console outputs
Expected result: The output after clicking the red is “Red_Square has been pressed!”, the output after clicking the green is “Green_Square has been pressed!”
Actual result: The output after clicking the red is “Green_Square has been pressed!”, the output after clicking the green is “Green_Square has been pressed!”
Reproducible with: 1.1.1 (2022.1.0a14), 1.2.0 (2022.1.0b5), 1.3.0 (2021.3.7f1, 2022.1.11f1, 2022.2.0b3, 2023.1.0a3), 1.4.1 (2021.3.10f1, 2022.1.19f1, 2022.2.0b7, 2023.1.0a9), 1.4.2 (2021.3.11f1, 2022.1.19f1, 2022.2.0b12, 2023.1.0a16), 1.4.3 (2021.3.12f1, 2022.1.21f1, 2022.2.0b13, 2023.1.0a16)
Reproducible on: MacOS 12.2.1 (Intel), Windows 10
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 1.5.0):
The input system work has been done to pass though the display index.
Whilst this doesn't completely fix the issue, I'm closing it as this following bug covers the follow up UI work to pass the display index though.
https://jira.unity3d.com/browse/UUM-16464