Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2022.3.59f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99175
Regression
No
Gradient Editor always opens on the main display when a multi-monitor setup is used and the Editor Window is on a secondary display
Reproduction steps:
1. Have at least a two monitor/display setup
2. Open the attached “IN-96214.zip” project
3. Drag the Editor Window to a secondary display
4. Open the “SampleScene”
5. Click on the “GradientObject” GameObject in the Hierarchy
6. In the Inspector, click on the Gradient bar to open the Gradient Editor
7. Observe both displays
Expected result: The Gradient Editor opens on the display where the Editor was
Actual result: The Gradient Editor opens on the main display
Reproducible with: 2022.3.59f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Reproducible on: Windows 11
Not reproducible on: macOS 15.3.1 (M4 Max)
Note:
- Also reproduces with other Gradient Editors, for example, the “Color over Lifetime” in the Particle System
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unable to switch to either Facebook Instant Games/Meta Quest in the Build Profile
- Error "IndexOutOfRangeException: Index was outside the bounds of the array" logged when selecting an Element in UI Builder with a specific setup
- "native code called abort()" is thrown in WebGL player when loading first scene
- Gradient Editor always opens on the main display when a multi-monitor setup is used and the Editor Window is on a secondary display
- Crash on core::base_hash_set when importing a specific package
Add comment