Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.1.6f1
2019.2.0a1
2019.3.0a1
Issue ID
1162614
Regression
Yes
[WebGL] RenderTextures color is not updated based on depth in WebGL builds when using WebGL 2.0 graphics API
How to reproduce:
1. Open the attached project ("case_1162614-TestDepth2017.zip")
2. Open the repro scene ("SampleScene")
3. Enter the play mode
4. Move the camera up and down using W/S keys and notice the texture changing from black to red
5. Make and run a WebGL build using WebGL 2.0 graphics API
6. Move the camera again
Expected results: RenderTexture's color changes based on depth
Actual results: RenderTexture's color remains black and does not change based on depth
Reproducible with: 2018.4.2f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
Not reproducible with: 2017.4.29f1
Notes:
1. The issue does not reproduce when WebGL 1.0 graphics API is used instead of WebGL 2.0
2. Tested with Google Chrome (75.0.3770.90 (Official Build) (64-bit)), Firefox (67.0.2 (64-bit)
3. Couldn't test with 2018.3.0a1 because of project crashing while opening the scene
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a4