Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
Issue ID
1166847
Regression
No
[Android][LWRP] Lightmaps don't render properly on LWRP with "SRP Batcher" enabled
Reproduction steps:
1. Open "lightmapError.rar" project and "stage01-00-night" scene
2. Build & Run for Android
3. Notice how the scene is rendered (bad.png)
4. "LWRP-HighQuality" -> "Advanced" -> "SRP Batcher" -> Off
5. Build & Run for Android
6. Notice how the scene is rendered (good.png)
Expected Result: SRP Batcher doesn't distort the rendering
Actual Result: SRP Batcher distorts the rendering
Reproduced with: 2019.3.0a8, 2019.2.0b8, 2019.1.9f1
Did not reproduce on: 2018.4.3f1 (No SRP Batcher), 2017.4.29f1 (no Packman)
Note:
Mono and IL2CPP reproduce the issue
OpenGLES3 and Vulkan reproduce the issue
OpenGLES2 does not reproduce the issue
Repro Devices:
VLNQA00216, Razer Phone 2 (Phone 2), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00218, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00124, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00263, Google Pixel 3 (Pixel 3), Android 9, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00149, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00005, Samsung Galaxy S7 (SM-G930V), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00271, Samsung - (SM-F900F), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00270, Samsung Galaxy S10e (SM-G970F), Android 9, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00217, Razer Phone 2 (Phone 2), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00230, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00017, Huawei Nexus 6P (Nexus 6P), Android 8.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00138, Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00093, Samsung Galaxy S6 edge (SM-G925F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00176, Xiaomi Redmi 4 (Redmi 4), Android 6.0.1, CPU: Snapdragon 430 MSM8937, GPU: Adreno (TM) 505
VLNQA00109, Xiaomi MI NOTE Pro (MI NOTE Pro), Android 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue GT7400 Plus
VLNQA00266, Xiaomi Mi A2 (Mi A2), Android 9, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00273, Vivo V1821BA (V1821A), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
No Repro Devices:
VLNQA00111, Samsung Galaxy J5(2016) (SM-J510FN), Android 7.1.1, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
This is a duplicate of issue #1104468