Search Issue Tracker
Fixed in 6.9.0
Votes
5
Found in [Package]
5.13.0, 5.10.0
Issue ID
1148817
Regression
No
[LWRP] Render Texture loses transparency values in built game when an Empty Renderer Feature is added
Steps to reproduce:
1. Open user attached project
2. Build & Run
3. Observe that the render texture loses transparency
Expected result:
Reproduced in: 2019.3.0a1, 2019.2.0a14, 2019.1.0f2 on Vulkan and OpenGLES3
Packages reproduced in: 5.13.0, 5.10.0
Reproduced on: Android, iOS, Windows Standalone
Devices under test:
Reproduced:
VLNQA00230, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
iPhone 6 (iOS 11.3.1)
Comments (1)
-
talofen
May 30, 2019 22:03
Same problem in Windows Build. Both LWRP and HDRP. In a new project the problem is not there, but after some works, it comes out. I still have not found the combination of settings that triggers it...Does anyone have any workaround?
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 6.9.0):
Fixed from LWRP 6.9.0+