Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.9f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1184385
Regression
No
[WebGL] Multiple Camera Viewports in fullscreen mode are rendered differently in WebGL builds than in the Editor
How to reproduce:
1. Open the attached project ("case_1184385-WebGlViewportsBug.zip")
2. Switch the targeted platform to WebGL
3. Open the repro scene ("SampleScene")
4. Enter Play mode and notice how viewports are displayed
5. Move the mouse to any of the viewports and press "Space" to focus that viewport
6. Exit Play Mode
7. Make a WebGL build and run it
8. Enter fullscreen mode
Expected results: Viewports are rendered the same as in the Editor
Actual results: Viewports are rendered differently, and some of them aren't visible
Reproducible with: 2017.4 32f1, 2018.4.10f1, 2019.2.7f2, 2019.3.0b4, 2020.1.0a3
Couldn't test with 2020.1.0a4, 2020.1.0a5 because of WebGL errors in the build
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2021.1):
Overlay cameras (UI Camera) will no longer cause the fullscreen display to sometimes be incorrect
Fixed in 2021.1.0a3