Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2018.4.26f1
2020.2
Issue ID
1271765
Regression
No
[Android] The Grabpass does not work when the Blit Type is set to Auto
Reproduction steps:
1. Open the user attached project "TestGrabPass.zip"
2. Switch platform to Android
3. In the Project window under "Assets/Resources/Scenes" open "SampleScene.unity"
4. Make sure that in the Player Settings under Resolution and Presentation Blit Type is set to Auto
5. Build for Android
Expected result: The Grabpass works when the Blit type is set to auto (See notes)
Actual result: The Grabpass does not work when the Blit type is set to auto
Reproduces on: 2018.4.26f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a21
Reproduced with these devices:
OpenGLES 2 and OpenGLES 3:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
Does not reproduce with these devices:
Vulkan:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Notes:
-Issue does not reproduce if Blit Type is set to Always
-Enter Play Mode in the Editor to see the expected results
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b2, backported to 2018.4, 2019.4, 2020.1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.29f1