Search Issue Tracker
Won't Fix
Votes
2
Found in
2021.3.40f1
2022.3.38f1
6000.0.10f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-75634
Regression
No
[macOS][Intel] Red screen appears in Player while resizing from Window to Fullscreen Window when using Screen.fullScreen = true;
Steps to reproduce:
1. Open the "TestProject.zip" on Intel Mac
2. Go to Edit > Project Settings > Player > Resolution and Presentation
3. Set "Fullscreen Mode" to the "Maximized Window"
4. Build and Run to the Mac Platform
5. Minimize Player from Fullscreen Window to Windowed mode
6. Close the app
7. Go to Edit > Project Settings > Player > Resolution and Presentation
8. Set "Fullscreen Mode" to the "Windowed"
9. Build and run to the Mac Platform
Actual results: App loads and when it's resizing from Window to Fullscreen Window red screen appears
Expected results: App loads and automatically resizes from Window to Fullscreen Window successfully
Reproducible with versions: 2021.3.40f1, 2022.3.38f1, 6000.0.10f1
Tested and reproduced on device:
- MacBook Pro, 15-inch, 2017, Radeon Pro 560 4 GB, Intel HD Graphics 630, 1536 MB. macOS: Ventura 13.5.2
Tested and did not reproduced on devices:
- MacBook Pro, 16-inch, 2021, Apple M1 Max, macOS: Ventura 14.5
- Windows 11 Pro, Inte(R) Xeon(R) W-2145 CPU @ 3.70GHZ, version: 23H2
Notes:
- Only reproducible when using Screen.fullScreen = true;
- On Silicon Mac screen also appears, stays for the same amount of time, but it's black
Comments (2)
-
Redrag
Apr 28, 2025 09:35
I'm getting screen tearing on Mac only, fullscreen only. VSync makes no difference or any other settings I have tried. Unity 6000.2.0a9
-
HLRob
Aug 21, 2024 10:09
We're seeing a similar issue as well, using a fresh project on 2021.3.41f1 on our Intel Mac with 100% repro rate. If the project is built with "maximised window" or "fullscreen window" then the game starts in a weird state, either a black screen or a zoomed in pixel (which you would see changing colors if something moves on the screen) but the game's logic and audio still works.
Switching to windowed mode while in this state, fixes the issue until you go back into fullscreen. It was also noticed that having the unity editor open sometimes helps fixing the issue even in fullscreen, so if you don't see it try turning off the editor and running the build then.
MacBook Pro, 16-inch 2019, 2.6GHz 6-core Intel Core i7, AMD Radeon Pro 5300M 4 GB, Intel UHD Graphics 630 1536 MB, 16 GB 2667 MHz DDR4, Sonoma 14.5
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.