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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment