Better performance on stock rendering pipe then LWRP? Android

I switched to using LWRP a few days ago, and game is now running at 60FPS for about 1-2mins and then it starts dropping the frame rate cause of thermal throttling. I had this problem before but i used Beautify bloom PP so when i turned it off i stop getting this overheat but with LWRP without any PP i am getting worse performance than before... How is that possible =.=. Testing on my Galaxy 8+ SM-G955F and these settings for LWRP with 2 Pixel lights and HDR enabled other things r disabled, rendering is set to 1 cause i am already scaling it down via script in the beginning to max res 1080p. I am using 1 directional light, Lightweight PBR shader and no shadows. Should i tweak something else and is there anyone with the same problem?

EDIT: I have V-Sync set to every v blank cause without it fps is blocked on 30, i thought to overcome this thermal throttling by limiting fps to 30 but still i am better going with standard pipeline and beautify over LWRP and new processing stack where i get max 50 FPS using bloom only with Fast enabled it says that it is optimized for mobile

 

I have the same experience on 2018.1.6, the default is 5x faster on a low end device.

 

W

Will default pbr shader work well on newer Android device like 4gb ram + adreno 506?

 

Is beautify works great for mobile ?

 

I noticed something similar and decided to upload an example project with apks:
https://1drv.ms/u/s!Ajlnu9a5i2Xz3SXMNlD-ryZLLVm5

I get 60 FPS on old default rendering ( no SRP asset set in graphics settings. All materials in the scene set to "Standard").
With the LQLWRP asset and the materials set to LWRP shaders its at about 34 FPS.
No posteffects.
Currently, I'm testing on a Xiaomi Mi A2 lite - Similar behavior on a Doogee Mix 2.
Did I miss some essential step when enabling LWRP?

 

Getting same result on Galaxy Note 5: 29-32fps vs 60fps.

 

In my case, the FPS is almost 50% compared with Mobile shaders right after converted. But we go to far and we cannot convert back.
Now we need to wait for the LWRP to be more stable and has better performance.

 

In my case, the game look significantly worse with almost no Post process,
and I lose about 20-30% of FPS on PC/Consoles

 

For us:

EditorVersion: 2018.3.0b12,
render-pipelines.core: 4.3.0-preview,
render-pipelines.lightweight: 4.3.0-preview,

Tested on PC/Switch/PS4, all of these platforms show significant drop in performances and graphics

 

- BuiltIn Deferred > LWRP 4.3.
- we use the Unity Post processing 2

we have lots of lights.

 

Probably because you have a lot of lights you will need to wait for deferred LWRP in 2019 to get better results

 

Yeah but light is supposed to be capped to 1 directional +4 others in LWRP no?

 

You mean LWRP performing worse than Built-in, right?

 

yes for inside, it's mainly AO and most of the time shadows are disabled

Shadows where disabled, cause with shadows it's -5fps

yeah that's why I'm really surprised!
It will be very hard to extract a small scene, project is 30gigs

Maybe one of the reason could come from the shaders, in Build-in we have custom shaders handwritten, with LWRP we ported our shaders to Amplify Shaders Editor




Completely unrelated, but I've done that tool to quickly change all materials

 

Right now I can't, as our tests where very inconclusive we decided to put that in pause and move it in a separate branch.
Once I've finish my current task, I can go back to it.

 

I have just upgraded my project to 2018.3.0f2 and LWRP 4.6.0
Currently building for Android.
I made my own light weight Glass Shader in Shader Graph using a simple Opaque Texture process.

I'll go through the process of reverting to standard shaders again to test this as I think LWRP is hurting my FPS as well.
Day Scene has 1 Pixel light with shadows.
Night scene has no Pixel Lights but 6 Vector lights with no shadows.

Unfortunately I suck at traditional Shader Programming so not sure how best to convert my Glass over. I might try using MK Glass Free.

I'll post some mobile results soon.

Here's how my current test scenes look in the editor using LWRP (Obviously FPS on mobile are much worse ) ...

 

Hi @phil_lira,

I just filed a bug report for a very similar problem with the LWRP on Android involving shadows. I created a very simple scene: an object using the simple lit shader (alpha clipping activated) casts a shadow on a single plane using a single directional light with soft shadows (shadow resolution: 1024). On a Galaxy S6 (SM-G920F) this scene leads to significant device heating and battery drainage. The same scene using the legacy renderer and legacy (cutout) shaders leads to less heating (with 'very high' shadow resolution). By comparison, on a Pixel XL (1st gen) I don't get significant heating using the LWRP.

Will post #issue id once it's sent to me. Cheers /Wendi

 

Bug report is here.

 

My guess is that you are using higher quality shadows with LWRP vs the default pipeline.

 

Sorry, but the only way I can make sense of your remark is by assuming you didn't read my post. As I said, the problem is specific to a certain device (S6) using a LWRP build vs default. Performance is not selectively impacted on another device (Pixel).

 

It could be that the impact of the soft shadows is insignificant on the pixel or that the pixel has a better GPU architecture for the task than the S6 (i.e. maybe tiled vs non-tiled), so it may only be measurable on the S6.
What sort of frame rates are you getting? Is VSync enabled?

 

yes ! much slower !

on an android mid-end device, the stardard runs at 24fps and the LX runs at 17fps.

It's and fps walk in Carcassonne. if you wanna see the difference in real with your devices, i'll post both
standard and LW APKs. just lemme know

Therefore, for me the LW is a no-go for android.

Happy Unitying !

 

Hi @grobonom, Unity say they treat all such cases (with less performance on LWRP) as bugs, so could you file a bug report instead of posting your APKs here?

 

hi @WendelinReich

I'll try to file a bug but i know U3D devs will need my project and it's getting quite huge :/
more than 2GB....

I thought that as a first step i could send the 2 apk to give an idea of the differences.

It will take ages to upload for my internet connection.

But if it might help unity team, i will report my issue.

Happy Unitying !

 

Yup LWRP sucks. Don't think it was tested.

 

Be less internet.

 

Hi folks,
after updating my 2d platformer to unity 2019.1 and LightweightRP 5.7.2 i have performance issue only on an android devices. Final Blit Pass take around 80% all rendering time, so rendering performance is terrible.

Submitted the bug report (Case 1151611)

 

i suppose you disabled the 'wait vsync' option ?

sometimes, udev team make weird choices :/ like dropping their awesome webplayer, for a useless 3D web api... quite strange but i guess it's a matter of market parts.....

LWRP is amazing for windows and really runs faster !
On android it appears there are still some issues.... just a matter of time IMHO )

Happy unitying !

 

Meizu Pro 7 Plus and Nexus 7 2013. Mono and IL2CPP builds.

 

I'm having the same FPS issues on my low end Android device using a MEIZU_M5 model M611H.

The demo scene in the LWRP project template is running at 5~6fps on my device with post process and around 30 fps without post process..

Switching back to default rendering until it's usable on low end devices. I'll stay around.

 

Unity 2019.1.4f1

LG K8 (2017)

One mesh with ~65500 vertices

mobile diffuse: 60fps+
lwrp simple lit: 45fps
standard shader: 30fps
lwrp lit: 30fps

I will file a bug report tomorrow...

 

Unity 2019.1.0 lwrp has a very bad visual quality and is running very slowly...

 

1. Are we getting the improvement updates soon ? Im using LWRP 5.7 on Unity 2019.1
2 . Is there a way to currently disable some of these features like cascaded shadows manually ?
3 . noice

 

You can set shadow cascades to disabled. That saves a fair bit. It also means that you do not have to do a z prepass which isn't that useful on mobile unless you need Z for another effect.
Without cascades, you will probably need to use a very limited shadow range.
Soft shadows have a cost as well.

 

I am having issues with the unnecessary FinalBlitPass too. This happens on mobile devices because

Code (CSharp):

1. bool platformNeedsToKillAlpha = Application.platform == RuntimePlatform.IPhonePlayer ||
2.                 Application.platform == RuntimePlatform.Android ||
3.                 Application.platform == RuntimePlatform.tvOS;
4.             renderingData.killAlphaInFinalBlit = !Graphics.preserveFramebufferAlpha && platformNeedsToKillAlpha;

killAlphaInFinalBlit is true on those devices by this part of code in LightweightRenderPipeline.cs, which leads to

Code (CSharp):

1. RequiresIntermediateColorTexture

returning true in ForwardRenderer.cs, which leads to

Code (CSharp):

1. bool createColorTexture = RequiresIntermediateColorTexture(ref renderingData, cameraTargetDescriptor) || rendererFeatures.Count != 0;

getting true, which leads to the FinalBlitPass. Also attaching any RendererFeature has the same effect.
This is unfortunate, as its absolutely not necessary, and takes a huge amount of frameTime especially on older devices. The only way for me to prevent this is to force createColorTexture to false, but I can only achieve this by editing the package source code, which is no feasible solution (just for testing I did this, and everything runs fine and smooth, same performance as without LWRP).

So please fix this (LWRP 6.9.1)!!

 

Unfortunately, we've had to modify the source code as well for the same reasons.
Maintaining it will be a pain, but we hope that someone fixes it soon.
There must be a better way to deal with RendererFeatures and the final blit that is more performant, even if that means less abstract.

 

The LWRP's PixelPerfectCamera makes it so my UI elements such as buttons aren't clickable. If I disable the PixelPerfectCamera, I can click them (so I can confirm that it's this causing it). Using the previous PixelPerfectCamera from the Pixel Perfect package did NOT cause this problem.

Any ideas?

EDIT: It's an issue only when crop frame X or Y is set! It's very weird. It's like I have to click and take into account the position of the offset from X and Y. How to fix?

 

Im trying to use LWRP for an Android game but i cant get more than 25 fps on a medium performance device ( Asus Zenfone 4 Max). I lowered everything i could regarding performance for testing. Even a blank new scene dont pass 20 FPS with LWRP default settings.
Using stock rendering on my game i get 60 FPS.
Should i forget about LWRP for a while and go back to stock?
I would like to use a neon texture in some parts, which is easier to acquire with LWRP, but i cant get it on stock rendering without buying it on asset store ( unless im missing something or I coudnt find a good tutorial).

 

You are using LWRP for a neon texture?
I am guessing that the shader is the missing part as textures are interchangeable.
Chances are, you can modify the neon shader to work with the stock RP, copy the neon texture and create an appropriate material.
Still, I wonder why your fps with LWP is so different. Are you using shadows? Do you have cascades on? In the stock RP cascades silently fail, in LWP they work but they are slow.