Search Issue Tracker

Not Reproducible

Under Consideration for 6000.3.X

Votes

0

Found in

6000.3.0a3

Issue ID

UUM-112329

Regression

Yes

Editor and Build Profiles windows turn black when moved to another monitor

-

Steps to reproduce:

Short version:

  1. Have your monitors set to mirror
  2. Close your Mac (as you would when putting it to sleep); make sure it's plugged in and not set to lock up immediately.
  3. Open Build Profiles
  4. Add a macOS build profile and select it
  5. Click “Cloud Build” and click “Add Settings” (you might get prompted to install the Build Automation package first; do that and click the Cloud Build button again afterwards)
  6. Open your Mac

The same result can be achieved by moving the Unity editor over to the other monitor without closing your laptop. Choose whichever yields the best results.

Long version:

  1. Create a new project
  2. File -> Build Profiles
  3. Click “Add Build Profile”
  4. Select “Meta Quest”, which is not installed
  5. Click “Add Build Profile”
  6. Open/focus "Build Profiles" window (while bug UUM-112120  is not fixed)
  7. Click “Cloud Build” and click “Install”
  8. Open/focus "Build Profiles" window (while bug UUM-112120  is not fixed)
  9. Delete the created build, close the window
  10. File -> Build Profiles
  11. Click “Add Build Profile”
  12. “Meta Quest”  will be presented by default
  13. Click “Add Build Profile”
  14. Open/focus "Build Profiles" window (while bug UUM-112120  is not fixed)
  15. Click “Cloud Build” and click “Add Settings”
  16. Leave the windows open
  17. Move the editor to another monitor
  18. Or move the "Build Profiles" window to another monitor window

Actual results: Windows become black

Expected results: Windows should stay the same as they were

Reproducible with versions:  6000.3.0a3

Not reproducible with versions: 6000.3.0a2

Can’t test with versions:  -

Tested on (OS): M1 Max - Sequoia 15.5

Note: After some time, if you leave the editor or its window, it returns to its original state

  1. Resolution Note:

    The team and I cannot reproduce this error following both long and short repro steps on macOS 15.5 M4. If you can still reproduce this issue on 6000.3.0a5, please reopen this ticket and update the description with more details to help us reproduce this issue. Thanks.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.