Search Issue Tracker
Fixed in 7.0.0
Votes
0
Found in [Package]
6.9.1
Issue ID
1187003
Regression
Yes
[LWRP] Transparent Render Textures are Rendered as solid colors when using CustomForwardRendererData with a Renderer Feature
Steps to reproduce:
1. Open user's attached project "LWRPRenderTextureTransparencyBug.zip"
2. Build and Run the project
3. Notice RenderTexture is Rendered as solid black color
Expected results: RenderTexture renders 0 alpha camera background color as completely transparent.
Actual results: RenderTexture renders 0 alpha camera background color as a solid color
LWRP RenderTexture transparency issue
Reproducible with: 2019.2.6f1(6.9.1)
VLNQA00115, Sony Xperia Z3 (D6603), Android 6.0.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Not Reproducible with: all versions with LWRP 6.9.0
Notes: CustomForwardRendererData is not available for LWRP 4.10.0 in 2018.4.9f1. In LWRP 6.5.3 and lower, there is an unexpected behavior where clicking "add Renderer Feature" doesn't do anything
Fixed in: LWRP/URP 7.0.0
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
Add comment