I have been working on a very simple looking 2D game for Android, and after loading it on my HTC One M7 I noticed a low frame rate for such a simple looking game?
After opening the console and using profilegpu I have discovered that apparently it is due to post processing, despite the fact that I have disabled the post processing in this level?
After closing and reopening the profilegpu tab it has switched what it taking up so much frame-time (can’t think of another word for it) sometimes it says postprocess, sometimes it says filter translucent volume?
Any light shed on this issue would be appreciated, as I have had sooo many problems with this project already.
Thanks for replying Andrew, but I do already-not have post processing in the scene or on the player enabled, so it seems as though the engine is applying some itself?
Also, I just found the name of the other thing that ends up taking alot, which is ‘filter translucent volume’ and am confused as to what that is?
Thanks.
Thankyou, however this does not stop the post processing from taking making the ticks longer.
Also when I disable translucent lighting, the post process cost, which should be nothing, ramps up to ‘fill in’ for the lack of translucent lighting.
So instead of the tick length being 1 for the translucent + 1 for the post process, it become 0 for the translucent + 2 for the post process? Like it’s trying to make the ticks longer or something?
Sure, however in this particular run, the reflection apply got boosted, despite, again, not having any reflection in my simple 2D android game with no reflection spheres or post process SSR?
Usually it is the post process that gets boosted, but it changes sometimes, as with this time.
“Affect Translucent Lighting” on the light just prevents their injection, there’s still come constant cost from clearing and filtering the volume.
You can disable it with the console command ‘r.TranslucentLightingVolume 0’, or lower the resolution with ‘r.TranslucencyLightingVolumeDim 32’. These can be overridden in your game’s DefaultEngine.ini (SystemSettings section) to apply them on load."
Thank you for providing me with this bit of information.
Have you set up your project for the proper targeted platform and hardware?
From looking at the overall times, your Scene render time is reduced by .03 ms after turning off the Translucent Volume Lighting. Notice also, the location of the small pink bar within your scene and how it has changed its order. That is the SSR Temporal AA.
When you select the correct platform and hardware, your default post process settings should change along with it.
When I created this project I set the target hardware to mobile, so that is not causing this issue.
On the subject of default post process settings I have all of them unchecked, from your images I cannot discern whether this is what you mean to be correct, or if you mean for me to check all of the post process settings?
Uncheck the settings you do not with to be calculated. Also keep in mind when you run the profile gpu command, it profiles the area in which your camera is focused. This is why you have varying outcomes between each profiling case. To increase performance as well, disable the ‘Smooth Framerate’ option, which is found in the ‘General Settings’ of your ‘Project Settings’
Ok, so when I disable post process showflag and also the translucent lighting, the reflectionapply and TXAA (despite the fact that in the settings I have set the antialias method to FXAA) take turns to boost up their tick length?
I know this is very old but I was seeing this recently. The post process had a 23 ms time no matter what I did. If I used the console command to disable post processing (ShowFlag.PostProcessing 0) the time went into translucent lighting, if i disabled that the time went elsewhere.
What was happening was my framerate was being restricted by my display. In this case it was restricted to 30 fps over rdp. It seemed like the profiler didn’t know where to put the extra frame time occurring due to the hardware limiting the rendering speed. The stat gpu even showed several ms in an [unaccounted] bucket.
Once I could render higher fps it was able to render faster and the random super high post process ms no longer appeared.