Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
10.1.0
Issue ID
1284683
Regression
No
[Mobile] Colours do not match on one of the Universal Rendering Examples projects
How to reproduce:
1. Clone project: "https://github.com/Unity-Technologies/UniversalRenderingExamples"
2. Open a project, and open a scene called "3DSkybox"
3. Switch target to Android
3. build and run the project on a device
Happens on Vulkan And GLES3
Expected Result: Colours do match the scene in the editor
Actual Result: Colours are way too different.
Reproducible with: Sony Xperia Z1 (Adreno 330) (probably older devices).
Not reproducible with :Samsung Galaxy Note10 USA, Android 9, [Adreno (TM) 640], Meizu Pro 6, Android 7 [Mali-T880], Huawei P20, Android 8, [Mali-G72].
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
I cannot reproduce this on Nexus 4 on Android 5.1 (newer driver than Zperia X1) or Android 4.4 (older driver).
I'm closing this as "Won't Fix". Most likely a driver bug.
It's unlikely that anyone is really going to ship HDR content with all the postprocessing of the test project in a new game that is supposed to run properly on the affected device.