Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
2021.3.37f1
6000.0.37f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-70588
Regression
No
[iOS] Specular lightning is inconsistent when using iOS
How to reproduce:
1. Download and open the attached project
2. Enter Play mode
3. Observe the brightness of the spheres in the Play view
4. Build and deploy the project for iOS
5. Observe the brightness of the spheres in the device
Expected outcome: The brightness of the spheres do not differ between editor and iOS devices
Actual outcome: The brightness of the spheres differ between editor and iOS devices (slightly darker on iOS devices)
Reproduced with: 2021.3.37f1, 2022.3.25f2, 2023.2.19f1, 2023.3.0b10, 6000.0.0b16
Reproduced with: iPad 6th gen (iOS 17.2)
Could not reproduce with: iPhone 12 Pro (iOS 14.4.1), iPhone 13 Pro (iOS 16.6.1)
On the attached project the main light specular appears darker on my iPad Pro 12.9 2nd gen, while on editor and on my iPhone X appears as expected.
You can see the difference on the images attached (the 4:3 being from the iPad).
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 (6000.5.X):
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.