Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1f1
Issue ID
916927
Regression
Yes
Button hitbox transfers through game window when using two canvases on two separate displays
To reproduce:
1. Open attached project "New Unity Project.zip"
2. Open "buttons.unity" scene
3. Enter play mode
4. Click on the button in game window Display 1 observe as the buttons presses
5. Click on the same spot where button is on game window Display 1, in game window Display 2
Expected result: button on game window Display 1 is not pressed
Actual result: button on game window Display 1 is pressed
Reproduced on: 5.6.1f1 5.6.1p2 2017.1.0b8
Not reproduced on: 5.5.0f3 5.5.4f1
Regression introduced on: 5.6.0a1 (you still can not press the button on the game window Display 2)
Notes: on 5.5.x you can not click the button on game window Display 2. Using canvas render mode Screen Space - Camera, getting same results.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Add comment