Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.5f1
2023.1.5f1
2023.2.0b2
2023.3.0a1
6000.0.0b11
Issue ID
UUM-45004
Regression
No
Incorrect colors are rendered when using GUI.DrawTexture on macOS with Metal
Reproduction steps:
1. Open the attached project "IMGUITest"
2. Change Graphics API to Metal in the Player Settings
3. Build and Run the project
Expected result: the colors are dark-ish
Actual result: the colors are pale
Reproducible with: 2021.3.29f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0b2
Reproducible on: macOS 13.4.1 (Intel), Xbox One (user reported)
Not reproducible on: Windows 10, macOS 13.4.1 (Intel) (OpenGLCore, user reported)
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
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
- Meshes created via InstantiateAsync render at the spawn position when GPU Resident Drawer is enabled
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.