Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a10
Issue ID
1103131
Regression
No
[PostProcessing] [Android] [Gles2] Motion Blur effect gives too blurry result on Adreno GPUs
Steps to reproduce:
1) Download attached project and open in Unity
2) Make sure Graphics API is set to Gles2
3) Build and Run project on a device
4) Select effects in that order: MotionBlur, Grain, LensDistortion, Vignette
5) Click on Run! button
Observe: Once the camera reach Motion Blur effect, the scene view will be way too blurry
Expected result: This effect should not be that blurry
Reproduced with:
2018.3.0b12, 2019.1.0a10
Devices under testing:
Reproduced with:
VLNQA00107 Google Nexus 6P*, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 430
VLNQA00216 Razer Phone 2*, OS:8.1.0, CPU:arm64-v8a, GPU:Adreno (TM) 630
Not reproduced with:
VLNQA00013 Samsung Galaxy Edge+, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760
VLNQA00212 iPhone Xs, SoC: A12, iOS: 12.0
VLNQA00175 Samsung Galaxy Note9, OS:8.1.0, CPU:arm64-v8a, GPU: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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Resolution Note (2019.2.X):
This affects only GLES2 on GLES3-capable Adreno devices. Motion blur is too heavy for GLES2 devices anyway.