Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.15f1
2018.2.16f1
2018.3.0b5
2018.3.0b10
2019.1.0a9
Issue ID
1090068
Regression
No
[macOS][Metal] A blue shadow appears under the cursor when playing Standalone Fullscreen Metal build on MacBook Air
Steps:
1. Open attached project ("macbookair-small.zip")
2. Make sure Metal API is set as Graphics API for build
3. Build for macOS Standalone
4. Open build in MacBook Air
Expected: no shadow under the cursor.
Actual: there is a blue shadow under the cursor.
Reproduced with: 2017.4.15f1, 2018.2.16f1, 2018.3.0b10, 2019.1.0a9.
Tested with: MacBook Air (mid 2012)
Note:
-not tested with the new MacBook Air 2018 which probably isn't affected as it has Retina display
-not reproducible on MacBook Pro, iMac 5K, Mac mini.
-not reproducible if Graphics API is OpenGL
-not reproducible if a build is started in a non-fullscreen mode
-
nickrobin7278
Mar 06, 2019 04:10
I use MacBook Pro and I have faced the same issue on my MacBook Pro. I have recently updated the system and after the update, my MacBook Pro turned into a black screen. I have searched a lot to fix the error on the internet and found https://applesupportnumber.net/blog/macbook-pro-wont-turn-on/. It really provides the entire solutions regarding this.
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2019.2.X):
This is clearly the OS/driver issue. Unity is not responsible for drawing system cursors so we cannot do much about it.