Search Issue Tracker
Fixed
Fixed in 2022.3.16f1, 2023.2.1f1, 2023.3.0a15
Votes
3
Found in
2022.3.13f1
2023.1.0a25
2023.2.0a16
2023.3.0a8
Issue ID
UUM-36255
Regression
Yes
Button triggers another Button when multiple Canvases are used in multiple windows
How to reproduce:
1. Open the “Multi_Canvas_Game_View_Bug“ project
2. Open the “SampleScene”
3. Make sure to have 2 Game views open for “Display 1” and “Display 2”
4. Enter Play Mode
5. Click on the Button GameObject in “Display 1”, then do the same for “Display 2”
Expected result: both Button GameObject events are independent of each other
Actual result: the Button GameObject from “Display 2” triggers the Button GameObject from “Display 1”
Reproduced with: 2023.1.0a25, 2023.1.0b18, 2023.2.0a16
Not reproduced with: 2020.3.48f1, 2021.3.26f1, 2022.2.21f1, 2023.1.0a24
Reproduced on: Windows 10 (by reporter), Windows 11
Notes:
1. In Player, in all tested versions, the Button GameObject on “Display 2” does not do anything
2. To open a second Game view window navigate to Window > General > Game, then on the newly opened Game view window right-click on the “Game” label > Add Tab > Game
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Pitou22
Oct 25, 2023 18:15
Please also see https://issuetracker.unity3d.com/issues/button-only-responds-to-interactions-on-main-display-when-using-a-multiple-display-environment
It was reported 3 month before this issue, and then closed as a duplicates of this one 🤦
march_YY
May 20, 2023 06:10
我又看了下问题出在触控的时候无法正确的得到触控点的坐标。修改下Input中gettouch这个返回的position内容,哦对了确切的说应该是position.x的计算结果,应该是当前屏幕X位置 + 累加前面几个屏幕的X坐标值