Bug Very high contrast and saturation on android build (LWRP)

Our team recently discovered that whenever we build our game for android, we get a really high saturation and contrast that looks really really bad. The first time I noticed it I thought it was only something odd in one particular test scene, because our main test device is an iPad and the game looked right whenever we build for ios.

We changed to 2019.1 a few weeks ago, but I'm not sure if we had the problem before that or if that's when it started. All android builds worked fine like a month ago at least.

When we build the entire game to android, every scene but one had the issue, and that scene did not have any post process in it, so we tried removing the post process on the cameras in all the scenes, but that actually just made the problem appear in all the scenes, including the one that looked fine before.We use the standard post process for unity.

We tried comparing our build settings to the LWRP example project and found nothing obvious, and we've tried googling but this does not seem to be a common issue because I found nothing.

Any takers on how to solve this?

 

Update with screenshots of the issue and settings.

This is part of a scene what it looks like in the editor (and it looks the same in an ios-build):



This is what it looks like in the android build:



Player settings:





LWRP settings:

 

It seems as though lighting has been omitted from the shaders compiled for Android. Or perhaps that the shader is not supported for that particular GPU and is reverting to an unlit fallback

 

Hm, not sure what you mean. Like the standard unlit shader in LWRP? Because the contrast and saturation effect is on everything in the game, even UI and terrain, trees etc, and even if everything would have unlit shaders it would just look flat and not that dark and saturated. However, the shader compilation takes like and hour so maybe that's an indicator of something, but it's been like that for a while before this problem occured.

I did just notice though that there's no saturation and contrast issue when building in gamma, so it's got to have something to do with linear color space.

 

Thanks, but we tried to build in 2019.1.4f1 as well and still had the issue. The 2019.2b seems to work however, so we're gonna wait for that to come out of beta instead.

 

I still got that issue in 2019.2b. On all devices using Vulkan, everything looks as it should, just with OpenGL3 things get that too high contrast.

 

@aleksandrk Yes it is! The normal postprocessing stack. It doesn some stuff though when i enter different PP-volumes, the effects just dont get displayed properly.

 

@aleksandrk Nice Devices were: LG Nexus 5 and Nexus 6 (all running OpenGL due to their old Android Version). Every device that supports Vulkan didnt show the issue (Nokia 5, Galaxy Tab 2016, Pixel 1st Gen).

 

Are there any plans to back port the fix to other versions of 2019?

 

@aleksandrk my project is locked to 2019.1 for some time, so I'm trying to patch this asap.

I pulled these changes into my local embedded lwrp package v5.16.1
https://github.com/Unity-Technologi...mits/30f5ed8a99c36bd3f46637445ff37e9cc71b3584
FinalBlitPass.cs is now in universal pipeline, but in 5.16.1 I found it in lwrp.

Those changes fixed the darkness of everything but the screen overlay UI. I can't find any other related issues. Is this known? Is FinalBlitPass happening after UI in the newer versions?

Thanks for the help!

 

So in the future we would likely be able to work around this by disabling post processing for those devices?

 

Hi @aleksandrk

I am seeing this in 2018.3, is this the same issue or something else?

 

@aleksandrk I upgraded my project from LWRP to Universal now to see if the fix worked. Everything seems fine, but now I dont get any PP-effects shown at all anymore, but I noticed that the camera itself has some PostProcess-Options now (Volume Mask and a Trigger to render PP-Effects), that were not there before. (Post Processing stack is up to date according to the Package Manager).

 

This darkening affect all SRP with Android-Linear-OpenglES3-pre Android 9. Even simplistic pipe like https://github.com/phi-lira/HelloSRP
This bug block android release of my game, hope unity fix this bug as fast as possible.

 

I figured out what was happened. In unity 2019, when using custom render pipeline, the AndroidBlitType parameter forced to Newer Blit and hided from settings. This cause darkening on Android-Linear-OpenglES3. If i manually edit ProjectSettings.asset and set BlitType to Always(0) all looks fine.
Don't know why unity hide this parameter, don't know why they force it ti Newer. And very angry on unity testing team. They don't find that critical bug, that basically do not allow you to release on android.

 

Yes, i can do sRGB<->Linear conversion for framebufffer by myself. But problem is that uGUI became darker too, and i have no access to uGUI rendering at all.

 

Where is clear documentation for this new PP stack? Can you explain the differences between all versions of PP stack and their compatibility.

 

4 month old critical bug.. Nice.

 

Uhm … on my ProjectSettings.asset androidBlitType is already set to 0, nevertheless, the editor always shows "Never", and of course, everything is ugly dark. @BattleAngelAlita did you do anything else to set "Always"?

 

After saving project unity automatically set this parameter to BlitType Newer. So i asked my programmers to put this lie in build script

Code (CSharp):

1. PlayerSettings.Android.blitType = AndroidBlitType.Always;

 

Thank you, I will test it out.

 

How can i Upgrade to the URP 7.1.1 version ? im stuck in 7.0.1 version (using Unity 2019.3.0b4)

 

download these packages and extract into your packages folder of your peoject :]
each package must be extracted as separate folder ...

com.unity.render-pipelines.universal
com.unity.render-pipelines.core
com.unity.shadergraph

 

Thank you!
Why they are not automatically listed in the PackageManager ?
Are they unstable ?

 

this is latest stable version ...
also i tried these (7.1.2) on 2020.1.0a5 ...
but got same problem [linear - glES 3.1] on android 5.1 and 6.0 and 8.1 [phones and emulators] :[

the Memu emulator is really good choice to testing your games

 

i tested on 3 samsung devices and in all of them it works without bugs but with Very Bad Performance, between 17~60fps in the same map area. but without the URP it's always stable never goes down the 55fps even on old devices. (android 6 )
but when testing on Oneplus2 it's a total different Game, Dark Colors and anything blue, red or yellow become emissive. looks like a Sci-fi Version of it XD. (i think the LWRP/URP is declared stable and ready for release too fast)

anyway i know Unity it's taking too much time to do some essential fixes, time that some studios dont have and cant publish their games just for that.
but from my experience it's the best Game Engine you can found!! it's not yet perfect but it's not sooo far from it.
if we guys look at the new features like : ECS and it's performance by default, the Jobs (Parallelism), Burst, new Renderer Pipeplines and much more. it's going so fast and they cant fix everything in few weeks or months.

i hope Unity Teams will fix them as fast as possible.

I Love Unity and i dont see my future without it!!!

 

i think that Samsung phones have Vulkan and Oneplus 2 doesn't have it , and just used glES 3.x ...
this problem is exists on Open glES 3.x only on android 8.1 and below ... not sure about that :[

 

does it fix method for URP?
and can you give me some info to how to implement this code on project to run it on building?
thanks.

 

Yep in my Case i dont have high contrasts anymore but still having other problems related to the subscene.

@BattleAngelAlita are you having the same high contrasts problems with the new URP version 7.1.2 ?

 

@Opeth001
I write my own pipeline.
Unfortunately this darkening is not problem of SRP. Darkening affect UGUI, and from SRP there is no access to UGUI at all.

 

same problem on URP:
https://forum.unity.com/threads/universal-rp-darker-linear-colorspace-on-android.753944/

 

Same problem on 2018.4 latest LTS. Does anyone have a work around?

 

yes ... rollback to built-in and save your life :|

 

I am on built in, the issue isn't present when building with Vulkan.

My setup is the following:

Built in pipeline
2018.4 LTS
Linear Rendering
Built in Post, only color grading.
Android Platform
Samsung Galaxy S8
Open GLES 3.0
Blit Type "Always"

Upgrading Unity to 2019 is not an option, doesn't seem to fix the issue anyways.

 

i mean rollback to Standard RP ... don't waste your time on LWRP or URP ...

 

Just test 2019.3. And it seems like unity has remove this AndroidBlitType workaround.

 

On 2019.2.3f1 everything seems fine for phones with android version 9.0, but not for those with 8.1. Alltough the first two scenes in our game looked right on my motorola g5(8.1), but all other scenes still have the bug. One of the scenes that looked right this time used to have the contrast-bug, and both of them have post process activated.

Do the SRP Batcher option have anything to do with anything? We disabled that because of other light bugs, and that's the first time that my phone have had any scene working correctly in regards to this thing.

 

All bugs im having (different on each device) are related to SRP Batcher.
Case : 1172922

More Infos here: https://forum.unity.com/threads/are-unity-subscenes-and-lwrp-compatible.717422

 

unity 2019 3.0b8 and urp 7.1.2
still have this bug

when do you fix this bug???

this bug is very critical
linear space render output and gamma space render output have big different
i don't want use gamma space render