Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.36f1
Issue ID
UUM-66007
Regression
No
Button triggers another Button when multiple displays are used
How to reproduce:
1. Open the “bug-uitoolkit-multidisplay“ project
2. Make sure you have at least an additional display connected
3. Build And Run
4. In the secondary display’s Player select one of the buttons
5. Observe the primary display’s Player
Expected result: Both button events are independent of each other
Actual result: The buttons from “Display 2” trigger the buttons from “Display 1”
Reproduced with: 2021.3.36f1, 2022.3.20f1
Not reproduced with: 2023.2.14f1, 2023.3.0b10
Fixed in: 2022.3.21f1
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Running a 3-display setup, the tertiary display’s Player buttons don’t respond at all
2. Could not test in the Editor → Could not find a way to display multiple scenes on different displays
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2021.3.X):
Porting this fix to 2021.3 requires porting more important changes that go with it, which are too risky to include in 2021.3, given the value of keeping this release as stable as possible.